[no subject]

hi Linux http://bit.ly/2yfmtQy Best Wishes Manish Lachwani -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH] usb: "USB Host halt failed, -110" error when rebooting system

On Tue, Oct 17, 2017 at 07:57:39PM -0500, wenxi...@linux.vnet.ibm.com wrote: > From: Wen Xiong > > > We saw "Host halt failed, -110" error when rebooting system/ > shutdowning system/kexec constantly. > > This patch called usb_disconnect() before calling

Re: [PATCH 2/2] ARM: dts: r8a7743: Add xhci support to SoC dtsi

On Tue, Oct 17, 2017 at 01:39:33AM +, Yoshihiro Shimoda wrote: > Hi Biju-san, > > IIUC, when we submitted a patch for dts[i] file, > we don't need to submit such a patch to usb maintainers. > > > From: Biju Das, Sent: Monday, October 16, 2017 7:13 PM > > > > From: Fabrizio Castro

Re: [PATCH v3 10/14] extcon: intel-int3496: Add support for controlling the USB-role mux

Hi Hans, On 2017년 09월 23일 03:37, Hans de Goede wrote: > Cherry Trail SoCs have a built-in USB-role mux for switching between > the host and device controllers, rather then using an external mux > controller by a GPIO. > > There is a driver using the mux-subsys to control this mux, this > commit

Re: [PATCH v2] extcon: Split out extcon header file for consumer and provider device

Gently Ping. Dear Kishon, Could you please review this patch for 'drivers/phy/*'? Regards, Chanwoo Choi On 2017년 10월 12일 12:40, Chanwoo Choi wrote: > Dear Kishon, > > Could you please review this patch? > After that, I'll make the immutable brand and then send the pull request > for

[PATCH] usb: "USB Host halt failed, -110" error when rebooting system

From: Wen Xiong We saw "Host halt failed, -110" error when rebooting system/ shutdowning system/kexec constantly. This patch called usb_disconnect() before calling xhci_halt(). usb_disconnect()disconnect the parent and all of its children, clean up hardware state

Re: xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 2 with no TDs queued?

Applied it to 4.13.7, and it helps! Thanks a lot! 2017-10-16 14:33 GMT+03:00 Mathias Nyman : > On 13.10.2017 14:46, Yaroslav Isakov wrote: >> >> Hello, Mathias! Did you get a chance to look into this bug? > > > Other things came up and this got a bit delayed. >

[PATCH usb-next v6 0/3] initialize (multiple) PHYs on the roothub

This series is the outcome of a discussion with Felipe Balbi, see [0] and [1] as well as Mathias Nyman, see [7] and [8]. The quick-summary of this is: - dwc3 already takes one USB2 and one USB3 PHY and initializes these correct - some other HCI platform drivers (like ehci-platform.c, xhci-mtk.c

[PATCH usb-next v6 1/3] dt-bindings: usb: add the documentation for USB root-hub

A USB root-hub may have several PHYs which need to be configured before the root-hub starts working. This adds the documentation for such a USB root-hub as well as a hint regarding the child-nodes on XHCI controllers which can include the roothub. Signed-off-by: Martin Blumenstingl

[PATCH usb-next v6 3/3] usb: core: hcd: integrate the PHY roothub wrapper

This integrates the PHY roothub wrapper into the core hcd infrastructure. Multiple PHYs which are part of the roothub devicetree node (which is a sub-node of the sysdev's node) are now managed (= powered on/off when needed), by the new usb_phy_roothub code. One example where this is required is

[PATCH usb-next v6 2/3] usb: core: add a wrapper for the USB PHYs on the root-hub

Many SoC platforms have separate devices for the USB PHY which are registered through the generic PHY framework. These PHYs have to be enabled to make the USB controller actually work. They also have to be disabled again on shutdown/suspend. Currently (at least) the following HCI platform drivers

Re: [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub

Hi Arnd, On Tue, Oct 17, 2017 at 11:10 PM, Arnd Bergmann wrote: > On Tue, Oct 17, 2017 at 11:00 PM, Martin Blumenstingl > wrote: >> On Fri, Oct 13, 2017 at 9:37 AM, Arnd Bergmann wrote: >>> On Thu, Oct 12, 2017 at 10:56 PM,

Re: [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub

On Tue, Oct 17, 2017 at 11:00 PM, Martin Blumenstingl wrote: > On Fri, Oct 13, 2017 at 9:37 AM, Arnd Bergmann wrote: >> On Thu, Oct 12, 2017 at 10:56 PM, Martin Blumenstingl >> wrote: >> >> It's possible that

Re: [RFC usb-next v5 3/3] usb: core: hcd: integrate the PHY roothub wrapper

On Fri, Oct 13, 2017 at 4:07 PM, Alan Stern wrote: > On Thu, 12 Oct 2017, Martin Blumenstingl wrote: > >> Hi Alan, >> >> On Mon, Oct 9, 2017 at 7:18 PM, Alan Stern wrote: >> > On Sun, 8 Oct 2017, Martin Blumenstingl wrote: >> > >> >> This

Re: [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub

Hi Alan, On Fri, Oct 13, 2017 at 4:15 PM, Alan Stern wrote: > On Thu, 12 Oct 2017, Martin Blumenstingl wrote: > >> Hi Alan, >> >> On Thu, Oct 12, 2017 at 11:17 PM, Alan Stern >> wrote: >> > On Thu, 12 Oct 2017, Martin Blumenstingl wrote: >>

Re: [RFC usb-next v5 1/3] dt-bindings: usb: add the documentation for USB root-hub

Hi Arnd, On Fri, Oct 13, 2017 at 9:37 AM, Arnd Bergmann wrote: > On Thu, Oct 12, 2017 at 10:56 PM, Martin Blumenstingl > wrote: >> Hi Arnd, >> >> thank you for reviewing this patch! >> >> On Mon, Oct 9, 2017 at 12:24 PM, Arnd Bergmann

Re: [PATCH v2 2/2] dt-bindings: max3421: Add bindings documentation

On 10/17/2017 12:22 AM, Jules Maselbas wrote: Thanks Sergei, Is it better if the documentation say: " Optional property: - interrupt-parent: the phandle of the associated interrupt controller. " That should be enough. or should I also add that "it may be inherited from the parent

Re: [PATCH v2 2/2] dt-bindings: max3421: Add bindings documentation

On Mon, Oct 16, 2017 at 01:43:06AM +0200, Jules Maselbas wrote: > Adds bindings documentation for the max3421 driver. > > Signed-off-by: Jules Maselbas > --- > .../devicetree/bindings/usb/maxim,max3421.txt | 24 > ++ > 1 file changed,

[PATCH v2] usb: Kconfig: clarify use of USB_PCI

Make the intended use of this option easier to grasp. Signed-off-by: Chris Mayo --- v2 changes: added description as requested. Chris drivers/usb/Kconfig | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/usb/Kconfig

Re: [PATCH v2] usb: hub: Allow reset retry for USB2 devices on connect bounce

On Tue, 17 Oct 2017, Mathias Nyman wrote: > If the connect status change is set during reset signaling, but > the status remains connected just retry port reset. > > This solves an issue with connecting a 90W HP Thunderbolt 3 dock > with a Lenovo Carbon x1 (5th generation) which causes a 30min

Re: [PATCH] MAINTAINERS: fix git tree url for musb module

Bin Liu writes: > Commit 3b2435192fe91 ("MAINTAINERS: drop OMAP USB and MUSB > maintainership") switched the maintainer for musb module, but didn't > update the git tree location. > > Delete the git tree information, since the current maintainer doesn't > have a public tree. > >

Re: [PATCH] usb/gadget/snps_udc_core: Convert timers to use timer_setup()

On Mon, Oct 16 2017, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > If the probe fails, udc_remove() will not be called, so

[PATCH] MAINTAINERS: fix git tree url for musb module

Commit 3b2435192fe91 ("MAINTAINERS: drop OMAP USB and MUSB maintainership") switched the maintainer for musb module, but didn't update the git tree location. Delete the git tree information, since the current maintainer doesn't have a public tree. Reported-by: Jonathan Liu

[PATCH v2] usb: hub: Allow reset retry for USB2 devices on connect bounce

If the connect status change is set during reset signaling, but the status remains connected just retry port reset. This solves an issue with connecting a 90W HP Thunderbolt 3 dock with a Lenovo Carbon x1 (5th generation) which causes a 30min loop of a high speed device being re-discovererd

Re: [PATCH] usb: Kconfig: clarify use of USB_PCI

On Tue, Oct 17, 2017 at 12:52:29PM +0100, Chris Mayo wrote: > Signed-off-by: Chris Mayo I can't take patches without any changelog text, sorry. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to

Re: [PATCH] xhci: Set DMA parameters appropriately

Hi Robin, On 2017-10-13 12:48, Robin Murphy wrote: On 13/10/17 09:15, Marek Szyprowski wrote: On 2017-10-11 15:56, Robin Murphy wrote: xHCI requires that data buffers do not cross 64KB boundaries (and are thus at most 64KB long as well) - whilst xhci_queue_{bulk,isoc}_tx() already split their

Re: [PATCH v2] usb: wusbcore: Use put_unaligned_le32

On Tue, Oct 17, 2017 at 05:20:29PM +0530, Himanshu Jha wrote: > On Tue, Oct 17, 2017 at 11:51:14AM +0200, Greg KH wrote: > > On Fri, Oct 06, 2017 at 08:38:07PM +0530, Himanshu Jha wrote: > > > Use put_unaligned_le32 rather than using byte ordering function and > > > memcpy which makes code clear.

[PATCH] usb: Kconfig: clarify use of USB_PCI

Signed-off-by: Chris Mayo --- drivers/usb/Kconfig | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/usb/Kconfig b/drivers/usb/Kconfig index 939a63bca82f..f699abab1787 100644 --- a/drivers/usb/Kconfig +++ b/drivers/usb/Kconfig @@ -77,11 +77,12

Re: [PATCH v2] usb: wusbcore: Use put_unaligned_le32

On Tue, Oct 17, 2017 at 11:51:14AM +0200, Greg KH wrote: > On Fri, Oct 06, 2017 at 08:38:07PM +0530, Himanshu Jha wrote: > > Use put_unaligned_le32 rather than using byte ordering function and > > memcpy which makes code clear. > > Also, add the header file where it is declared. > > > > Done

[PATCH v3] usb: wusbcore: Use put_unaligned_le32

Use put_unaligned_le32 rather than using byte ordering function and memcpy which makes code clear. Also, add the header file where it is declared. Done using Coccinelle and semantic patch used is : @ rule1 @ identifier tmp; expression ptr,x; type T; @@ - tmp = cpu_to_le32(x); <+... when !=

Re: [PATCH v2 12/15] RDMA/cma: make config_item_type const

On Mon, Oct 16, 2017 at 05:18:51PM +0200, Bhumika Goyal wrote: > Make these structures const as they are either passed to the functions > having the argument as const or stored as a reference in the "ci_type" > const field of a config_item structure. > > Signed-off-by: Bhumika Goyal

Re: [PATCH v2 7/9] usb: host: modify description for MTK xHCI config

On 17.10.2017 13:20, Greg Kroah-Hartman wrote: On Fri, Oct 13, 2017 at 01:32:14PM +0300, Mathias Nyman wrote: On 13.10.2017 11:26, Chunfeng Yun wrote: Due to all MediaTek SoCs with xHCI host controller use this driver, remove limitation for specific SoCs Signed-off-by: Chunfeng Yun

Re: [PATCH 07/58] net/usb/usbnet: Convert timers to use timer_setup()

Am Montag, den 16.10.2017, 17:28 -0700 schrieb Kees Cook: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. Since the callback is called from > both a

Re: [balbi-usb:testing/next 31/41] drivers/usb/mtu3/mtu3_qmu.c:261:25: warning: format '%p' expects argument of type 'void *', but argument 7 has type 'dma_addr_t {aka unsigned int}'

Hi, kbuild test robot writes: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git > testing/next > head: f2fedb17e8946a24c9cf2bd20ee466fb8659196a > commit: 46ed5b0c1fac208e727c8cea6c2db44a77fc256a [31/41] usb: mtu3: support > 36-bit DMA address >

Re: [PATCH v2 11/15] stm class: make config_item_type const

On Mon, Oct 16, 2017 at 05:18:50PM +0200, Bhumika Goyal wrote: > Make config_item_type structures const as they are either passed to a > function having the argument as const or used inside a if statement or > stored in the const "ci_type" field of a config_item structure. > > Done using

Re: [PATCH v2 01/15] configfs: make ci_type field, some pointers and function arguments const

On Mon, Oct 16, 2017 at 05:18:40PM +0200, Bhumika Goyal wrote: > The ci_type field of the config_item structure do not modify the fields > of the config_item_type structure it points to. And the other pointers > initialized with ci_type do not modify the fields as well. > So, make the ci_type

Re: [PATCH v2 00/15] make structure field, function arguments and structures const

On Tue, Oct 17, 2017 at 12:16:18PM +0200, Julia Lawall wrote: > > > On Tue, 17 Oct 2017, Greg KH wrote: > > > On Mon, Oct 16, 2017 at 05:18:39PM +0200, Bhumika Goyal wrote: > > > Make the ci_type field and some function arguments as const. After this > > > change, make config_item_type

Re: [PATCH v2 7/9] usb: host: modify description for MTK xHCI config

On Fri, Oct 13, 2017 at 01:32:14PM +0300, Mathias Nyman wrote: > On 13.10.2017 11:26, Chunfeng Yun wrote: > > Due to all MediaTek SoCs with xHCI host controller use this > > driver, remove limitation for specific SoCs > > > > Signed-off-by: Chunfeng Yun > > --- > >

Re: [PATCH v2 08/15] nvmet: make config_item_type const

Acked-by: Sagi Grimberg -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [PATCH v2 00/15] make structure field, function arguments and structures const

On Tue, 17 Oct 2017, Greg KH wrote: > On Mon, Oct 16, 2017 at 05:18:39PM +0200, Bhumika Goyal wrote: > > Make the ci_type field and some function arguments as const. After this > > change, make config_item_type structures as const. > > > > * Changes in v2- Combine all the followup patches and

[balbi-usb:testing/next 31/41] drivers/usb/mtu3/mtu3_qmu.c:261:25: warning: format '%p' expects argument of type 'void *', but argument 7 has type 'dma_addr_t {aka unsigned int}'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next head: f2fedb17e8946a24c9cf2bd20ee466fb8659196a commit: 46ed5b0c1fac208e727c8cea6c2db44a77fc256a [31/41] usb: mtu3: support 36-bit DMA address config: mips-allyesconfig (attached as .config) compiler:

Re: [PATCH v2 00/15] make structure field, function arguments and structures const

On Mon, Oct 16, 2017 at 05:18:39PM +0200, Bhumika Goyal wrote: > Make the ci_type field and some function arguments as const. After this > change, make config_item_type structures as const. > > * Changes in v2- Combine all the followup patches and the constification > patches into a series. Who

Re: [balbi-usb:testing/next 34/43] drivers/usb/mtu3/mtu3_qmu.c:261:2: note: in expansion of macro 'dev_dbg'

On Tue, 2017-10-17 at 12:37 +0300, Felipe Balbi wrote: > Hi, > > kbuild test robot writes: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git > > testing/next > > head: 39325b9a22301178ef684effade7c8bce04b5246 > > commit:

[balbi-usb:testing/next 31/41] drivers/usb/mtu3/mtu3_qmu.c:261:25: warning: format '%p' expects argument of type 'void *', but argument 7 has type 'dma_addr_t {aka long long unsigned int}'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next head: f2fedb17e8946a24c9cf2bd20ee466fb8659196a commit: 46ed5b0c1fac208e727c8cea6c2db44a77fc256a [31/41] usb: mtu3: support 36-bit DMA address config: alpha-allyesconfig (attached as .config) compiler:

Re: [PATCH v2] usb: wusbcore: Use put_unaligned_le32

On Fri, Oct 06, 2017 at 08:38:07PM +0530, Himanshu Jha wrote: > Use put_unaligned_le32 rather than using byte ordering function and > memcpy which makes code clear. > Also, add the header file where it is declared. > > Done using Coccinelle and semantic patch used is : > > @ rule1 @ > identifier

Re: [balbi-usb:testing/next 34/43] drivers/usb/mtu3/mtu3_qmu.c:261:2: note: in expansion of macro 'dev_dbg'

On Tue, 2017-10-17 at 12:37 +0300, Felipe Balbi wrote: > Hi, > > kbuild test robot writes: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git > > testing/next > > head: 39325b9a22301178ef684effade7c8bce04b5246 > > commit:

Re: [PATCH] usb: isp1301-omap: Convert timers to use timer_setup()

Hi, Greg Kroah-Hartman writes: >> Kees Cook writes: >> > In preparation for unconditionally passing the struct timer_list pointer to >> > all timer callbacks, switch to using the new timer_setup() and from_timer() >> > to pass the timer

RE: [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5

Hi, Biju Das writes: > Hi, > >> -Original Message- >> From: devicetree-ow...@vger.kernel.org [mailto:devicetree- >> ow...@vger.kernel.org] On Behalf Of Felipe Balbi >> Sent: 17 October 2017 09:26 >> To: Biju Das ; Greg Kroah-Hartman >>

Re: [balbi-usb:testing/next 34/43] drivers/usb/mtu3/mtu3_qmu.c:261:2: note: in expansion of macro 'dev_dbg'

Hi, kbuild test robot writes: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git > testing/next > head: 39325b9a22301178ef684effade7c8bce04b5246 > commit: 8706b37e87e58cd4d4dea593767d34447321610a [34/43] usb: mtu3: support > 36-bit DMA address >

[balbi-usb:testing/next 34/43] drivers/usb/mtu3/mtu3_qmu.c:261:2: note: in expansion of macro 'dev_dbg'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next head: 39325b9a22301178ef684effade7c8bce04b5246 commit: 8706b37e87e58cd4d4dea593767d34447321610a [34/43] usb: mtu3: support 36-bit DMA address config: xtensa-allyesconfig (attached as .config) compiler:

[balbi-usb:testing/next 34/43] drivers/usb/mtu3/mtu3_qmu.c:261:25: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 7 has type 'dma_addr_t {aka unsigned int}'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git testing/next head: 39325b9a22301178ef684effade7c8bce04b5246 commit: 8706b37e87e58cd4d4dea593767d34447321610a [34/43] usb: mtu3: support 36-bit DMA address config: mips-allyesconfig (attached as .config) compiler:

RE: [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5

Hi, > -Original Message- > From: devicetree-ow...@vger.kernel.org [mailto:devicetree- > ow...@vger.kernel.org] On Behalf Of Felipe Balbi > Sent: 17 October 2017 09:26 > To: Biju Das ; Greg Kroah-Hartman > ; Rob Herring

Re: usb: dwc2: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 146s

On Mon, Oct 16, 2017 at 01:49:11PM -0700, Julius Werner wrote: > > d9a14b00 339317035 C Ii:1:004:1 -32:1 0 > > d9a14b00 339317049 S Ii:1:004:1 -115:1 10 < > > d9a14b00 339318040 C Ii:1:004:1 -32:1 0 > > d9a14b00 339318057 S Ii:1:004:1 -115:1 10 < > > d9a14b00 339319042 C Ii:1:004:1 -32:1 0 > >

Re: [PATCH] usb: isp1301-omap: Convert timers to use timer_setup()

On Tue, Oct 17, 2017 at 11:09:56AM +0300, Felipe Balbi wrote: > > Hi, > > Kees Cook writes: > > In preparation for unconditionally passing the struct timer_list pointer to > > all timer callbacks, switch to using the new timer_setup() and from_timer() > > to pass the

Re: [RESEND x2][PATCH 0/3] dwc2 fixes for edge cases on hikey

On 10/17/2017 1:34 AM, John Stultz wrote: > On Mon, Oct 16, 2017 at 1:36 AM, Minas Harutyunyan > wrote: >> On b-plug disconnect should asserted GOTGINT.SesEndDet interrupt. >> According previously sent by you register dump (GHWCFG2 = 0x23affc70) >> your core

Re: [PATCH] usb: hub: Allow reset retry for USB2 devices on connect bounce

On 16.10.2017 22:34, Alan Stern wrote: On Mon, 16 Oct 2017, Mathias Nyman wrote: If the connect status change is set during reset signaling, but the status remains connected just retry port reset. This solves an issue with connecting a 90W HP Thunderbolt 3 dock with a Lenovo Carbon x1 (5th

Re: [PATCH v2 02/15] usb: gadget: make config_item_type structures const

Hi, Bhumika Goyal writes: > Make these structures const as they are only passed to the const > argument of the functions config_{group/item}_init_type_name. > > Signed-off-by: Bhumika Goyal > --- > * Changes in v2- Combine all the followup patches and

Re: [PATCH v2 07/15] usb: gadget: configfs: make config_item_type const

Bhumika Goyal writes: > Make config_item_type structures const as they are either passed to a > function having the argument as const or stored in the const "ci_type" > field of a config_item structure. > > Done using Coccinelle. > > Signed-off-by: Bhumika Goyal

Re: [PATCH] usb: phy: phy-generic: propagate clk_get error if clock is required

Hi, Lucas Stach writes: > Am Freitag, den 18.08.2017, 18:32 +0200 schrieb Lucas Stach: >> If the clock handle is given in the DT, it means the clock is >> required >> for proper operation of the PHY. In that case a failure to obtain the >> clock must be propagated to

RE: [PATCH 2/2] ARM: dts: r8a7743: Add xhci support to SoC dtsi

Hi Shimoda-San, > Hi Biju-san, > > IIUC, when we submitted a patch for dts[i] file, we don't need to submit such > a > patch to usb maintainers. Thanks. I will take care this in future. Regards, Biju Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End,

Re: [PATCH] usb: renesas_usbhs: Add compatible string for r8a7743/5

Hi, Biju Das writes: > This patch adds support for r8a7743/5 SoC. The Renesas RZ/G1[ME] > (R8A7743/5) usbhs is identical to the R-Car Gen2 family. > > This doesn't change the driver, so it does nothing by itself. But it does > mean that checkpatch won't complain about

Re: [PATCH] usb: isp1301-omap: Convert timers to use timer_setup()

Hi, Kees Cook writes: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: Felipe Balbi > Cc: Greg

Re: [PATCH 1/2] dt-bindings: usb-xhci: Document r8a7743 support

On Mon, Oct 16, 2017 at 11:12:48AM +0100, Biju Das wrote: > From: Fabrizio Castro > > Document r8a7743 xhci support. The driver will use the fallback > compatible string "renesas,rcar-gen2-xhci", therefore no driver > change is needed. > > Signed-off-by: Fabrizio

Re: [PATCH 4.14 REGRESSION fix] USB: devio: Revert "USB: devio: Don't corrupt user memory"

On Mon, Oct 16, 2017 at 03:12:07PM -0400, Alan Stern wrote: > On Mon, 16 Oct 2017, Hans de Goede wrote: > > > Taking the uurb->buffer_length userspace passes in as a maximum for the > > actual urbs transfer_buffer_length causes 2 serious issues: > > > > 1) It breaks isochronous support for all