From: balbi@kernel•org (Felipe Balbi)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 3/3] USB3/DWC3: Enable undefined length INCR burst type
Date: Fri, 10 Feb 2017 10:44:58 +0200 [thread overview]
Message-ID: <87y3xeqvsl.fsf@linux.intel.com> (raw)
In-Reply-To: <DB5PR0401MB1813965DDC8CC6CD0BD85980FE440@DB5PR0401MB1813.eurprd04.prod.outlook.com>
Hi,
Jerry Huang <jerry.huang@nxp•com> writes:
>> @@ struct dwc3 {
>> enum usb_phy_interface hsphy_mode;
>>
>> u32 fladj;
>> + /*
>> + * For INCR burst type.
>> + * First field: for undefined length INCR burst type enable.
>> + * Second field: for INCRx burst type enable
>> + */
>> + u32 incrx_type[2];
>> u32 irq_gadget;
>> u32 nr_scratch;
>> u32 u1u2;
>> --
>> 1.7.9.5
> Hi, Balbi and all guys,
> Any comment for these patches? Can they be accepted?
Rob had comments which you didn't reply yet. I cannot take this patchset
yet ;-)
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170210/8416f400/attachment.sig>
next prev parent reply other threads:[~2017-02-10 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 8:12 [PATCH v4 1/3] USB3/DWC3: Add definition for global soc bus configuration register Changming Huang
2017-01-18 8:12 ` [PATCH v4 2/3] USB3/DWC3: Add property "snps, incr-burst-type-adjustment" for INCR burst type Changming Huang
2017-01-18 8:12 ` [PATCH v4 3/3] USB3/DWC3: Enable undefined length " Changming Huang
2017-02-10 7:45 ` Jerry Huang
2017-02-10 8:44 ` Felipe Balbi [this message]
2017-02-10 15:30 ` Jerry Huang
2017-03-10 11:26 ` Felipe Balbi
2017-05-02 6:13 ` Jerry Huang
2017-06-02 10:07 ` Felipe Balbi
2017-02-20 8:39 ` Jerry Huang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3xeqvsl.fsf@linux.intel.com \
--to=balbi@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox