Re: [PATCH 1/9] staging: sm750fb: fix line length coding style issue in ddk750_chip.c

On Mon, Aug 29, 2016 at 11:50:01PM +0300, Moshe Green wrote: > Fix a line length warning found by the checkpatch.pl tool in > ddk750_chip.c. > > Signed-off-by: Moshe Green > --- > drivers/staging/sm750fb/ddk750_chip.c | 2 +- What does this file have to do with the linux-usb

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi All Adding Vivek Gautam. On 29 August 2016 at 16:35, Michael Niewöhner wrote: > Hi Mathias, > On Mo, 2016-08-29 at 13:59 +0300, Mathias Nyman wrote: >> On 29.08.2016 10:28, Felipe Balbi wrote: >> > >> > >> > Hi, >> > >> > Michael Niewöhner writes:

[PATCH 1/9] staging: sm750fb: fix line length coding style issue in ddk750_chip.c

Fix a line length warning found by the checkpatch.pl tool in ddk750_chip.c. Signed-off-by: Moshe Green --- drivers/staging/sm750fb/ddk750_chip.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/sm750fb/ddk750_chip.c

[PATCH 0/6] usb: dwc2: gadget: Fix TX FIFO handling

Hi, This is a resend of a patch series originally submitted by Robert Baldyga back in February. Somehow I missed it back then. Sorry about that. It should fix some FIFO programming related issues on RPi and maybe other platforms. Also, this series makes the g-tx-fifo-size DT property obsolete.

[PATCH 3/6] usb: dwc2: gadget: change variable name to more meaningful

From: Robert Baldyga Since we handle FIFOs and endpoint separately, using variable named 'ep' in context of FIFO is misleading, hence we rename it to 'fifo'. Signed-off-by: Robert Baldyga Signed-off-by: John Youn ---

[PATCH 2/6] usb: dwc2: gadget: fix TX FIFO size and address initialization

From: Robert Baldyga According to DWC2 documentation, DPTxFSize field of DPTXFSIZn register is read only, which means that software cannot change FIFO size. Register description says: "The value of this register is the Largest Device Mode Periodic Tx Data FIFO Depth

[PATCH 1/6] usb: dwc2: gadget: use ep->fifo_index in context of FIFO registers

From: Robert Baldyga In context of FIFO registers we use ep->fifo_index instead of ep->index. Signed-off-by: Robert Baldyga Signed-off-by: John Youn --- drivers/usb/dwc2/gadget.c | 5 +++-- 1 file changed, 3 insertions(+),

[PATCH 4/6] usb: dwc2: gadget: remove dead code from dwc2_hsotg_ep_enable()

From: Robert Baldyga Since FIFO is always freed in dwc2_hsotg_ep_disable(), ep->fifo_index is always 0 in dwc2_hsotg_ep_enable(), hence code inside if() block is never executed. Signed-off-by: Robert Baldyga Signed-off-by: John Youn

[PATCH 6/6] Documentation: devicetree: dwc2: Deprecate g-tx-fifo-size

This property is not needed because the periodic fifos are not configurable. So it was incorrect to add this property in the first place. Signed-off-by: John Youn --- Documentation/devicetree/bindings/usb/dwc2.txt | 5 - 1 file changed, 4 insertions(+), 1 deletion(-)

[PATCH 5/6] usb: dwc2: gadget: free TX FIFO after killing requests

From: Robert Baldyga As kill_all_requests() potentially flushes TX FIFO, we should should free FIFO after calling it. Otherwise FIFO could stay unflushed properly. Signed-off-by: Robert Baldyga Signed-off-by: John Youn ---

Re: [PATCHv6 1/3] usb: USB Type-C connector class

Hello Heikki, On Mon, Aug 29, 2016 at 05:07:39PM +0300, Heikki Krogerus wrote: > Hi Guenter, > > > > Overall this is quite vague and, especially for chargers, most of the time > > > misses the point. > > > > > > I would really prefer if we could stay closer to the specification in this > > >

Re: UAS and f_tcm -- is anyone using it?

On 8/29/2016 12:33 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: >> On 8/26/2016 12:48 AM, Felipe Balbi wrote: >>> >>> Hi, >>> >>> John Youn writes: I was wondering if anyone is using the f_tcm function? Specifically for UAS in

Re: [RESEND PATCH 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

On 8/29/2016 12:51 AM, Felipe Balbi wrote: > > Hi, > > John Youn writes: > > [...] > > + */ > + if (of_device_is_compatible(np, "rockchip,rk3288-usb")) > + hsotg->phy->ops->reset(hsotg->phy); > +

Re: pl2303_read_int_callback - usb_submit_urb failed with result -19

On Mon, 29 Aug 2016, Greg KH wrote: > > >> I have since compiled 4.8.0_rc1. And just as you guys suggested a part > > >> of problem is solved. The minor number now definitely goes up to 512 > > >> before giving no more free serial devices. But it still doesn't reuse > > >> the minors after

Re: pl2303_read_int_callback - usb_submit_urb failed with result -19

On Mon, Aug 29, 2016 at 10:22:43PM +0530, Malith Yapa wrote: > On Mon, Aug 29, 2016 at 4:46 PM, Greg KH wrote: > > On Mon, Aug 29, 2016 at 02:49:23PM +0530, Malith Yapa wrote: > >> On Thu, Jul 14, 2016 at 9:14 AM, Malith Yapa wrote: > >> > On

Re: pl2303_read_int_callback - usb_submit_urb failed with result -19

On Mon, Aug 29, 2016 at 4:46 PM, Greg KH wrote: > On Mon, Aug 29, 2016 at 02:49:23PM +0530, Malith Yapa wrote: >> On Thu, Jul 14, 2016 at 9:14 AM, Malith Yapa wrote: >> > On Thu, Jul 14, 2016 at 2:14 AM, Greg KH >> >

Re: [PATCHv6 1/3] usb: USB Type-C connector class

Hi Guenter, > > Overall this is quite vague and, especially for chargers, most of the time > > misses the point. > > > > I would really prefer if we could stay closer to the specification in this > > case, and not try to merge multiple orthogonal attributes into one. > > OK. So what would you

Re: [PATCHv6 0/3] USB Type-C Connector class

On Mon, Aug 29, 2016 at 06:06:39AM -0700, Guenter Roeck wrote: > On 08/29/2016 05:36 AM, Heikki Krogerus wrote: > > The USB Type-C class is meant to provide unified interface to the > > userspace to present the USB Type-C ports in a system. > > > The subject says "v6". True. I used the wrong

[PATCH v3 3/5] net: asix: Fix AX88772x resume failures

From: Robert Foss From: Allan Chou The change fixes AX88772x resume failure by - Restore incorrect AX88772A PHY registers when resetting - Need to stop MAC operation when suspending - Need to restart MII when restoring PHY Signed-off-by: Allan

[PATCH v3 2/5] net: asix: Avoid looping when the device is disconnected

From: Vincent Palatin Check the answers from the USB stack and avoid re-sending multiple times the request if the device has disappeared. Signed-off-by: Vincent Palatin Signed-off-by: Robert Foss Tested-by: Robert Foss

Re: [PATCHv6 1/3] usb: USB Type-C connector class

On Mon, Aug 29, 2016 at 06:04:52AM -0700, Guenter Roeck wrote: > Heikki, > > On 08/26/2016 07:07 AM, Heikki Krogerus wrote: > > > > > > > > +What: /sys/class/typec/-partner/type > > > > > > +Date: June 2016 > > > > > > +Contact: Heikki Krogerus

[PATCH v3 0/5] net/usb: asix driver improvements

From: Robert Foss This is a resubmission of v3, since the netdev mailinlist was not sent the previous submission. This series improves power management of the asix driver. - Suspend/resume support is improved to save needed registers. - Device disconnection is

[PATCH v3 5/5] net: asix: autoneg will set WRITE_MEDIUM reg

From: Grant Grundler The miii_nway_restart() causes a PHY link change activity and ax88772_link_reset will be called. link_reset will set AX_CMD_WRITE_MEDIUM_MODE register correctly. The asix_write_medium_mode in reset() fills in a default value to the register which may

[PATCH v3 3/5] net: asix: Fix AX88772x resume failures

From: Allan Chou The change fixes AX88772x resume failure by - Restore incorrect AX88772A PHY registers when resetting - Need to stop MAC operation when suspending - Need to restart MII when restoring PHY Signed-off-by: Allan Chou Signed-off-by: Robert

[PATCH v3 5/5] net: asix: autoneg will set WRITE_MEDIUM reg

From: Robert Foss From: Grant Grundler The miii_nway_restart() causes a PHY link change activity and ax88772_link_reset will be called. link_reset will set AX_CMD_WRITE_MEDIUM_MODE register correctly. The asix_write_medium_mode in reset()

[PATCH v3 4/5] net: asix: see 802.3 spec for phy reset

From: Grant Grundler https://lkml.org/lkml/2014/11/11/947 Ben Hutchings is correct. IEEE 802.3 spec section "22.2.4.1.1 Reset" requires up to 500ms delay. Mitigate the "max" delay by polling the phy until BCM_RESET bit is clear. Signed-off-by: Grant Grundler

[PATCH v3 1/5] net: asix: Add in_pm parameter

From: Freddy Xin In order to R/W registers in suspend/resume functions, in_pm flags are added to some functions to determine whether the nopm version of usb functions is called. Save BMCR and ANAR PHY registers in suspend function and restore them in resume function. Reset

[PATCH v3 4/5] net: asix: see 802.3 spec for phy reset

From: Robert Foss From: Grant Grundler https://lkml.org/lkml/2014/11/11/947 Ben Hutchings is correct. IEEE 802.3 spec section "22.2.4.1.1 Reset" requires up to 500ms delay. Mitigate the "max" delay by polling the phy until BCM_RESET bit is

[PATCH v3 2/5] net: asix: Avoid looping when the device is disconnected

From: Robert Foss From: Vincent Palatin Check the answers from the USB stack and avoid re-sending multiple times the request if the device has disappeared. Signed-off-by: Vincent Palatin Signed-off-by: Robert Foss

Re: [PATCHv6 1/3] usb: USB Type-C connector class

On Mon, Aug 29, 2016 at 2:36 PM, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role

Re: [PATCHv6 0/3] USB Type-C Connector class

On 08/29/2016 05:36 AM, Heikki Krogerus wrote: The USB Type-C class is meant to provide unified interface to the userspace to present the USB Type-C ports in a system. The subject says "v6". Guenter Changes since v6: - current_vconn_role attr renamed to vconn_source (no API changes) -

Re: [PATCHv6 1/3] usb: USB Type-C connector class

Heikki, On 08/26/2016 07:07 AM, Heikki Krogerus wrote: +What: /sys/class/typec/-partner/type +Date: June 2016 +Contact: Heikki Krogerus +Description: + Shows the type of the partner. Can be one of the following: +

Re: Queries regrading USB-driver software-architecture

Thanks Felipe and Greg for the replies. There is no one forcing us to use this kernel. Would http://releases.ubuntu.com/16.04.1/ubuntu-16.04.1-desktop-i386.iso.torrent?_ga=1.67231377.145502248.1467027188 be good enough to install? On Mon, Aug 29, 2016 at 6:19 PM, Greg KH

Re: Queries regrading USB-driver software-architecture

On Mon, Aug 29, 2016 at 05:56:03PM +0530, Ajay Garg wrote: > Hi All. > > We have a PC-in-a-box unit, with 2 COM-ports, 2 USB 2.0 ports and 1 > USB 3.0 port. > We are testing the COM-ports (COM1 and COM2) and the USB-ports. > > We proceeded as follows :: > > a) > In the setup > > User-App <=>

Re: Queries regrading USB-driver software-architecture

Hi, Ajay Garg writes: > Hi All. > > We have a PC-in-a-box unit, with 2 COM-ports, 2 USB 2.0 ports and 1 > USB 3.0 port. > We are testing the COM-ports (COM1 and COM2) and the USB-ports. > > We proceeded as follows :: > > a) > In the setup > > User-App <=> COM1 <=>

[PATCHv6 1/3] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[PATCHv6 0/3] USB Type-C Connector class

The USB Type-C class is meant to provide unified interface to the userspace to present the USB Type-C ports in a system. Changes since v6: - current_vconn_role attr renamed to vconn_source (no API changes) - Small documentation improvements proposed by Vincent Palatin Changes since v5: - Only

[PATCHv6 2/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

This adds driver for the USB Type-C PHY on Intel WhiskeyCove PMIC which is available on some of the Intel Broxton SoC based platforms. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/Kconfig | 14 ++ drivers/usb/typec/Makefile | 1 +

[PATCHv6 3/3] mfd: intel_soc_pmic_bxtwc: add support for USB Type-C PHY on WhiskeyCove

Intel WhiskeyCove PMIC has also a USB Type-C PHY, so let's create a device for it. Signed-off-by: Heikki Krogerus Cc: Lee Jones --- drivers/mfd/intel_soc_pmic_bxtwc.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

Queries regrading USB-driver software-architecture

Hi All. We have a PC-in-a-box unit, with 2 COM-ports, 2 USB 2.0 ports and 1 USB 3.0 port. We are testing the COM-ports (COM1 and COM2) and the USB-ports. We proceeded as follows :: a) In the setup User-App <=> COM1 <=> RS232-data <=> RS232-to-RS485 converter <=> RS485-data <=> Modbus-Device

Re: [PATCHv7 1/3] usb: USB Type-C connector class

> > + Valid values: > > + - source > > + - sink > > + > > +What: /sys/class/typec//current_vconn_role > > Isn't the cover letter saying you have changed this ? I have accidentally send the patches I prepared originally that did not include this

Re: [PATCHv7 1/3] usb: USB Type-C connector class

On Mon, Aug 29, 2016 at 12:23 PM, Heikki Krogerus wrote: > > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role

Re: pl2303_read_int_callback - usb_submit_urb failed with result -19

On Mon, Aug 29, 2016 at 02:49:23PM +0530, Malith Yapa wrote: > On Thu, Jul 14, 2016 at 9:14 AM, Malith Yapa wrote: > > On Thu, Jul 14, 2016 at 2:14 AM, Greg KH wrote: > >> On Wed, Jul 13, 2016 at 10:59:10AM +0530, Malith Yapa wrote: > >>> I think

Re: [PATCH v3 0/8] usb: ulpi: remove "dev" field from struct ulpi_ops

On Mon, Aug 29, 2016 at 10:58:25AM +0300, Felipe Balbi wrote: > > Hi folks, > > Tal Shorer writes: > > struct ulpi_ops is defined as follows: > > > > struct ulpi_ops { > > struct device *dev; > > int (*read)(struct ulpi_ops *ops, u8 addr); > > int

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi Mathias, On Mo, 2016-08-29 at 13:59 +0300, Mathias Nyman wrote: > On 29.08.2016 10:28, Felipe Balbi wrote: > > > > > > Hi, > > > > Michael Niewöhner writes: > > > > > > [1.] One line summary of the problem: > > > DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

On 29.08.2016 10:28, Felipe Balbi wrote: Hi, Michael Niewöhner writes: [1.] One line summary of the problem: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 [2.] Full description of the problem/report: No usb 3.0 devices are being detected when attached while

[PATCHv7 1/3] usb: USB Type-C connector class

The purpose of USB Type-C connector class is to provide unified interface for the user space to get the status and basic information about USB Type-C connectors on a system, control over data role swapping, and when the port supports USB Power Delivery, also control over power role swapping and

[PATCHv7 3/3] mfd: intel_soc_pmic_bxtwc: add support for USB Type-C PHY on WhiskeyCove

Intel WhiskeyCove PMIC has also a USB Type-C PHY, so let's create a device for it. Signed-off-by: Heikki Krogerus Cc: Lee Jones --- drivers/mfd/intel_soc_pmic_bxtwc.c | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCHv7 0/3] USB Type-C Connector class

The USB Type-C class is meant to provide unified interface to the userspace to present the USB Type-C ports in a system. Changes since v6: - current_vconn_role attr renamed to vconn_source (no API changes) - Small documentation improvements proposed by Vincent Palatin Changes since v5: - Only

[PATCHv7 2/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

This adds driver for the USB Type-C PHY on Intel WhiskeyCove PMIC which is available on some of the Intel Broxton SoC based platforms. Signed-off-by: Heikki Krogerus --- drivers/usb/typec/Kconfig | 14 ++ drivers/usb/typec/Makefile | 1 +

Re: [PATCH 2/4] phy: rockchip-usb: use rockchip_usb_phy_reset to reset phy during wakeup

Hi, On Monday 22 August 2016 06:30 PM, Heiko Stübner wrote: > Am Montag, 22. August 2016, 17:17:41 schrieb Kishon Vijay Abraham I: >> Hi, >> >> On Sunday 21 August 2016 02:02 AM, Randy Li wrote: >>> It is a hardware bug in RK3288, the only way to solve it is to >>> reset the phy. >>> >>>

Re: pl2303_read_int_callback - usb_submit_urb failed with result -19

On Thu, Jul 14, 2016 at 9:14 AM, Malith Yapa wrote: > On Thu, Jul 14, 2016 at 2:14 AM, Greg KH wrote: >> On Wed, Jul 13, 2016 at 10:59:10AM +0530, Malith Yapa wrote: >>> I think i am. >>> >>> int readDword(int addr) { >>> >>> uint16_t

[PATCH v2] usb: gadget: configfs: log function unbinding as debug

Disabling USB gadget functions configured through configfs is something that can happen in normal use cases. Keep the existing log for this type of event, but only as debug, not as an error. Signed-off-by: Romain Izard --- v1 -> v2: - use dev_dbg instead of dev_info

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

Hi Felipe, On 11 August 2016 at 11:14, Baolin Wang wrote: > Hi Felipe, > > On 1 August 2016 at 15:09, Baolin Wang wrote: >> Currently the Linux kernel does not provide any standard integration of this >> feature that integrates the USB subsystem

[PATCH] usb: renesas_usbhs: fix clearing the {BRDY,BEMP}STS condition

The previous driver is possible to stop the transfer wrongly. For example: 1) An interrupt happens, but not BRDY interruption. 2) Read INTSTS0. And than state->intsts0 is not set to BRDY. 3) BRDY is set to 1 here. 4) Read BRDYSTS. 5) Clear the BRDYSTS. And then. the BRDY is cleared wrongly.

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 29 August 2016 at 10:41, Pavel Machek wrote: > On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote: >> On 29 August 2016 at 10:05, Pavel Machek wrote: >> >> >2) Having "ports" subdir with RW files, one per each existing physical >> >> >port >> >> >In this situation we

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On Mon 2016-08-29 10:21:48, Rafał Miłecki wrote: > On 29 August 2016 at 10:05, Pavel Machek wrote: > >> >2) Having "ports" subdir with RW files, one per each existing physical > >> >port > >> >In this situation we don't need "new_port" or "remove_port". If we > >> >want port to be

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 08/26/2016 09:50 PM, Pavel Machek wrote: On Thu 2016-08-25 20:48:04, Jacek Anaszewski wrote: On 08/25/2016 04:30 PM, Alan Stern wrote: On Thu, 25 Aug 2016, Jacek Anaszewski wrote: I'd see it as follows: #cat available_ports #1-1 1-2 2-1 #echo "1-1" > new_port #cat observed_ports #1-1

Re: [PATCH v1] usb: gadget: configfs: log function unbinding as information

2016-08-29 10:13 GMT+02:00 Felipe Balbi : > > Hi, > > Romain Izard writes: >> Disabling USB gadget functions configured through configfs is something >> that can happen in normal use cases. Keep the existing log for this type >> of event, but only as

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 29 August 2016 at 10:05, Pavel Machek wrote: >> >2) Having "ports" subdir with RW files, one per each existing physical port >> >In this situation we don't need "new_port" or "remove_port". If we >> >want port to be observable we just do: >> >echo 1 > 1-1 >> >Implementing this

Re: [PATCH v1] usb: gadget: configfs: log function unbinding as information

Hi, Romain Izard writes: > Disabling USB gadget functions configured through configfs is something > that can happen in normal use cases. Keep the existing log for this type > of event, but only as information, not as an error. > > Signed-off-by: Romain Izard

Re: [PATCH v1] usb: gadget: configfs: log function unbinding as information

2016-07-26 18:21 GMT+02:00 Romain Izard : > Disabling USB gadget functions configured through configfs is something > that can happen in normal use cases. Keep the existing log for this type > of event, but only as information, not as an error. > > Signed-off-by: Romain

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

Hi! > >2) Having "ports" subdir with RW files, one per each existing physical port > >In this situation we don't need "new_port" or "remove_port". If we > >want port to be observable we just do: > >echo 1 > 1-1 > >Implementing this solution needs reading more details from USB subsystem. > > The

Re: [PATCH v3 0/3] USB Audio Gadget refactoring

Hi, Ruslan Bilovol writes: > I came to this patch series when wanted to do two things: > - use UAC1 as virtual ALSA sound card on gadget side, >just like UAC2 is used so it's possible to do rate >resampling > - have both playback/capture support in UAC1 > >

Re: [RESEND PATCH, v5 3/5] usb: xhci-mtk: make IPPC register optional

Chunfeng Yun writes: > Make IPPC register optional to support host side of dual-role mode, > due to it is moved into common glue layer for simplification. > > Signed-off-by: Chunfeng Yun Mathias? Are you taking these patches?? I don't wanna

[PATCH] usb: gadget: don't couple configfs to legacy gadgets

It's perfectly fine to have all configfs functions built-in while having modular legacy gadgets. Let's allow for that. Signed-off-by: Felipe Balbi --- drivers/usb/gadget/Kconfig | 38 +++--- 1 file changed, 19 insertions(+), 19

Re: [PATCH v3 0/8] usb: ulpi: remove "dev" field from struct ulpi_ops

Hi folks, Tal Shorer writes: > struct ulpi_ops is defined as follows: > > struct ulpi_ops { > struct device *dev; > int (*read)(struct ulpi_ops *ops, u8 addr); > int (*write)(struct ulpi_ops *ops, u8 addr, u8 val); > }; > > Upon calling

Re: [PATCH v4 08/10] usb: gadget: remove useless parameter in alloc_ep_req()

Hi, Felipe Ferreri Tonello writes: >> Felipe Ferreri Tonello writes: "Felipe F. Tonello" writes: > The default_length parameter of alloc_ep_req was not really necessary > and gadget drivers would almost

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 08/26/2016 05:58 PM, Rafał Miłecki wrote: On 25 August 2016 at 20:48, Jacek Anaszewski wrote: On 08/25/2016 04:30 PM, Alan Stern wrote: On Thu, 25 Aug 2016, Jacek Anaszewski wrote: I'd see it as follows: #cat available_ports #1-1 1-2 2-1 #echo "1-1" >

Re: [RESEND PATCH 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

Hi, John Youn writes: [...] + */ + if (of_device_is_compatible(np, "rockchip,rk3288-usb")) + hsotg->phy->ops->reset(hsotg->phy); + >>> >>> You should probably check for NULL before calling

Re: UAS and f_tcm -- is anyone using it?

Hi, John Youn writes: > On 8/26/2016 12:48 AM, Felipe Balbi wrote: >> >> Hi, >> >> John Youn writes: >>> I was wondering if anyone is using the f_tcm function? Specifically >>> for UAS in superspeed with streams? Any idea if it is being using

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

Hi, Michael Niewöhner writes: > [1.] One line summary of the problem: > DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422 > > [2.] Full description of the problem/report: > No usb 3.0 devices are being detected when attached while USB 2.0 > devices work on the same

Re: [PATCH] usb: xhci-plat: Add generic PHY support

Hi Mathias Nyman, Could you please provide your inputs on this? If you find it in good condition, please consider it for the next release. Thanks & Regards, Srinath. On Wed, Aug 3, 2016 at 7:03 PM, Srinath Mannam wrote: > Hi Mathias Nyman, > > Please review and