[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <TY2PR01MB3692CE6A245BE2C06AC4694CD8A10@TY2PR01MB3692.jpnprd01.prod.outlook.com>
Date: Mon, 11 May 2020 11:08:55 +0000
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
To: Al Cooper <alcooperx@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: Alan Stern <stern@...land.harvard.edu>,
Andy Shevchenko <andy.shevchenko@...il.com>,
"bcm-kernel-feedback-list@...adcom.com"
<bcm-kernel-feedback-list@...adcom.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
Mathias Nyman <mathias.nyman@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: RE: [PATCH v8 1/5] usb: xhci: Change the XHCI link order in the
Makefile
Hi Al,
> From: Al Cooper, Sent: Saturday, May 9, 2020 6:19 AM
>
> Some BRCMSTB USB chips have an XHCI, EHCI and OHCI controller
> on the same port where XHCI handles 3.0 devices, EHCI handles 2.0
> devices and OHCI handles <2.0 devices. Currently the Makefile
> has XHCI linking at the bottom which will result in the XHIC driver
> initalizing after the EHCI and OHCI drivers and any installed 3.0
> device will be seen as a 2.0 device. Moving the XHCI linking
> above the EHCI and OHCI linking fixes the issue.
>
> Signed-off-by: Al Cooper <alcooperx@...il.com>
I tested on my environment (r8a77951 and r8a77961) and then
I didn't detect any regression. So,
Tested-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Best regards,
Yoshihiro Shimoda
Powered by blists - more mailing lists