All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Al Cooper <alcooperx@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	"bcm-kernel-feedback-list@broadcom.com" 
	<bcm-kernel-feedback-list@broadcom.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Rob Herring <robh+dt@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: RE: [PATCH v8 1/5] usb: xhci: Change the XHCI link order in the Makefile
Date: Mon, 11 May 2020 11:08:55 +0000	[thread overview]
Message-ID: <TY2PR01MB3692CE6A245BE2C06AC4694CD8A10@TY2PR01MB3692.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20200508211929.39020-2-alcooperx@gmail.com>

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@gmail.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@renesas.com>

Best regards,
Yoshihiro Shimoda


  parent reply	other threads:[~2020-05-11 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 21:19 [PATCH v8 0/5] Add XHCI, EHCI and OHCI support for Broadcom STB SoS's Al Cooper
2020-05-08 21:19 ` [PATCH v8 1/5] usb: xhci: Change the XHCI link order in the Makefile Al Cooper
2020-05-08 22:50   ` Florian Fainelli
2020-05-11 11:08   ` Yoshihiro Shimoda [this message]
2020-05-08 21:19 ` [PATCH v8 2/5] dt-bindings: Add Broadcom STB USB support Al Cooper
2020-05-08 22:51   ` Florian Fainelli
2020-05-08 21:19 ` [PATCH v8 3/5] usb: xhci: xhci-plat: Add support for Broadcom STB SoC's Al Cooper
2020-05-08 22:51   ` Florian Fainelli
2020-05-08 21:19 ` [PATCH v8 4/5] usb: ehci: Add new EHCI driver " Al Cooper
2020-05-08 22:52   ` Florian Fainelli
2020-05-09  0:47   ` Alan Stern
2020-05-09 12:04     ` Andy Shevchenko
2020-05-08 21:19 ` [PATCH v8 5/5] usb: host: Add ability to build new Broadcom STB USB drivers Al Cooper
2020-05-08 22:53   ` Florian Fainelli

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=TY2PR01MB3692CE6A245BE2C06AC4694CD8A10@TY2PR01MB3692.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=alcooperx@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=robh+dt@kernel.org \
    --cc=stern@rowland.harvard.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.