[PATCH v2 5/7] usb: mtu3: make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3

In fact the driver depends on EXTCON only when it's configed as USB_MTU3_DUAL_ROLE, so make USB_MTU3_DUAL_ROLE depend on EXTCON but not USB_MTU3. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/Kconfig | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[PATCH v2 1/7] usb: mtu3: avoid TX data length truncated in SS/SSP mode

The variable of 'count' is declared as u8, this will cause an issue due to value truncated when works in SS or SSP mode and data length is greater than 255, so change it as u32. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget_ep0.c | 2 +- 1 file changed,

[PATCH v2 4/7] usb: mtu3: fix operation failure when test TEST_J/K

There is an error dialog popped up in PC when test TEST_J/K by EHSETT tool, due to not waiting for the completion of control transfer. Here fix it by entering test mode after Status Stage finish. Signed-off-by: Chunfeng Yun --- v2: 1. reset test_mode as default

[PATCH v2 7/7] usb: mtu3: fix uncontinuous SeqN issue after disable EP

Reset EP when disable it to reset data toggle for U2 EP, and SeqN, flow control status etc for U3 EP, this can avoid issue of uncontinuous SeqN Signed-off-by: Chunfeng Yun --- v2: add this patch --- drivers/usb/mtu3/mtu3_core.c | 4 1 file changed, 4

[PATCH v2 2/7] usb: mtu3: remove repeated setting of gadget state

The usb_add_gadget_udc() will set the gadget state as USB_STATE_NOTATTACHED, so we needn't set it again. Signed-off-by: Chunfeng Yun --- drivers/usb/mtu3/mtu3_gadget.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git

[PATCH v2 3/7] usb: mtu3: fix an unrecognized issue when connected with PC

When boot on the platform with the USB cable connected to Win7, the Win7 will pop up an error dialog: "USB Device not recognized", but finally the Win7 can enumerate it successfully. The root cause is as the following: When the xHCI driver set PORT_POWER of the OTG port, and if both IDPIN and

[PATCH v2 6/7] usb: mtu3: re-enable controller to accept LPM request after LPM resume

After the controller receives a LPM request, it will reject the LPM request, and need software to re-enable it after LPM resume if the controller doesn't remote wakeup from L1 automatically Signed-off-by: Chunfeng Yun --- v2: add this patch ---

Re: [RESEND PATCH 1/5] usb: mtu3: avoid TX data length truncated in SS/SSP mode

Hi, Greg On Thu, 2018-05-10 at 10:16 +0800, Chunfeng Yun wrote: > Hi, Greg > >Could you please pick up the series of patches, thanks a lot Please ignore it, I find a problem in [RESEND PATCH 4/5], and need send a new version. Very sorry > > On Sat, 2018-05-05 at 10:21 +0800, Chunfeng Yun

Re: [RESEND PATCH 1/5] usb: mtu3: avoid TX data length truncated in SS/SSP mode

Hi, Greg Could you please pick up the series of patches, thanks a lot On Sat, 2018-05-05 at 10:21 +0800, Chunfeng Yun wrote: > The variable of 'count' is declared as u8, this will cause an issue > due to value truncated when works in SS or SSP mode and data length > is greater than 255, so

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 08, 2018 at 08:36:25AM -0700, James Bottomley wrote: > Early boot means userspace. for a hot pluggable device, this would > probably be something in udev if you follow the no-daemon model and the > daemon could do it if you do follow the daemon model. > > James Could this be

Re: [PATCH] usb: gadget: composite: fill bcdUSB as 0x0320 for SuperSpeed or higher speeds

Hi, On Wed, 2018-05-09 at 14:33 +0300, Felipe Balbi wrote: > Hi, > > Chunfeng Yun writes: > > The USB3CV version 2.1.80 (March 26, 2018) requires all devices > > ( gen1, gen2, single lane, dual lane) to return the value of 0x0320 > > in the bcdUSB field > > this

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 08, 2018 at 10:29:41AM -0500, David R. Bild wrote: > On Tue, May 8, 2018 at 10:25 AM, James Bottomley > wrote: > > > > > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote: > > [...] > > > > In particular, it sets the credentials for

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Tue, May 08, 2018 at 08:25:48AM -0700, James Bottomley wrote: > On Tue, 2018-05-08 at 13:55 +0300, Jarkko Sakkinen wrote: > > On Fri, May 04, 2018 at 02:56:25PM -0500, David R. Bild wrote: > [...] > > > In particular, it sets the credentials for the platform hierarchy. > > > The platform

Re: [PATCH v3 2/2] usb: misc: xapea00x: perform platform initialization of TPM

On Sun, May 06, 2018 at 09:02:29AM -0600, Jason Gunthorpe wrote: > On Fri, May 04, 2018 at 03:19:21PM -0500, David R. Bild wrote: > > Setting the platform hierarchy password to a random discarded value > > (and the dictionary lockout reset) is really the only special work > > done here. The other

RE: [PATCH v5 01/14] dt-bindings: connector: add properties for typec

Hi > -Original Message- > From: Oliver Neukum [mailto:oneu...@suse.com] > Sent: 2018年5月8日 18:03 > To: Jun Li ; robh...@kernel.org; > heikki.kroge...@linux.intel.com; gre...@linuxfoundation.org; > li...@roeck-us.net > Cc: gso...@gmail.com; dl-linux-imx ;

Re: [PATCH v2 11/11] docs: fix broken references with multiple hints

On Wed, 9 May 2018, Mauro Carvalho Chehab wrote: > The script: > ./scripts/documentation-file-ref-check --fix-rst > > Gives multiple hints for broken references on some files. > Manually use the one that applies for some files. > > Signed-off-by: Mauro Carvalho Chehab

[PATCH v4 1/3] dt-bindings: usb: Update documentation for Qualcomm DWC3 driver

Existing documentation has lot of incorrect information as it was originally added for a driver that no longer exists. Signed-off-by: Manu Gautam Reviewed-by: Rob Herring --- .../devicetree/bindings/usb/qcom,dwc3.txt | 85 --

[PATCH v4 3/3] usb: dwc3: core: Suspend PHYs on runtime suspend in host mode

Some PHY drivers (e.g. for Qualcomm QUSB2 and QMP PHYs) support runtime PM to reduce PHY power consumption during bus_suspend. Add changes to let core auto-suspend PHYs on host bus-suspend using GUSB2PHYCFG register if needed for a platform. Also perform PHYs runtime suspend/resume and let

[PATCH v4 2/3] usb: dwc3: Add Qualcomm DWC3 glue driver

DWC3 controller on Qualcomm SOCs has a Qscratch wrapper. Some of its uses are described below resulting in need to have a separate glue driver instead of using dwc3-of-simple: - It exposes register interface to override vbus-override and lane0-pwr-present signals going to hardware. These

[PATCH v2 11/11] docs: fix broken references with multiple hints

The script: ./scripts/documentation-file-ref-check --fix-rst Gives multiple hints for broken references on some files. Manually use the one that applies for some files. Signed-off-by: Mauro Carvalho Chehab --- Documentation/ABI/obsolete/sysfs-gpio

Re: [RFC PATCH 1/7] usb: typec: Generalize mux mode names

On Tue, May 08, 2018 at 09:10:13PM +0200, Mats Karrman wrote: > Hi, > > On 05/08/2018 04:25 PM, Heikki Krogerus wrote: > > > Hi, > > > > On Mon, May 07, 2018 at 11:19:40PM +0200, Mats Karrman wrote: > Even so, when the mux driver "set" function is called, it will just get > the >

[PATCH] usb: gadget: composite: fill bcdUSB as 0x0320 for SuperSpeed or higher speeds

The USB3CV version 2.1.80 (March 26, 2018) requires all devices ( gen1, gen2, single lane, dual lane) to return the value of 0x0320 in the bcdUSB field Signed-off-by: Chunfeng Yun --- drivers/usb/gadget/composite.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] usb: gadget: composite: fill bcdUSB as 0x0320 for SuperSpeed or higher speeds

Hi, Chunfeng Yun writes: > The USB3CV version 2.1.80 (March 26, 2018) requires all devices > ( gen1, gen2, single lane, dual lane) to return the value of 0x0320 > in the bcdUSB field this sounds really odd. What happens when I get a USB 3.1 compliant device

[PATCH v4 0/2] usb: dwc2: fix isoc split in transfer issue

This patch fix dma unaligned problem and data lost problem for isoc split in transfer. Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb fs audio device (Plantronics headset) to capture and playback. William Wu (2): usb: dwc2: alloc dma aligned buffer for isoc split in usb:

[PATCH v4 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in a more supported way") rips out a lot of code to simply the allocation of aligned DMA. However, it also introduces a new issue when use isoc split in transfer. In my test case, I connect the dwc2 controller with an usb hs Hub

[PATCH v4 2/2] usb: dwc2: fix isoc split in transfer with no data

If isoc split in transfer with no data (the length of DATA0 packet is zero), we can't simply return immediately. Because the DATA0 can be the first transaction or the second transaction for the isoc split in transaction. If the DATA0 packet with no data is in the first transaction, we can return

Re: [PATCH v3 1/2] usb: dwc2: alloc dma aligned buffer for isoc split in

Dear Doug, 在 2018年05月08日 23:29, Doug Anderson 写道: Hi, On Tue, May 8, 2018 at 12:43 AM, wlf wrote: Dear Doug, 在 2018年05月08日 13:11, Doug Anderson 写道: Hi, On Mon, May 7, 2018 at 8:07 PM, William Wu wrote: +static int