From: peter.chen@freescale.com (Peter Chen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] USB: add generic onboard USB HUB driver
Date: Tue, 15 Dec 2015 16:33:26 +0800 [thread overview]
Message-ID: <20151215083259.GA13809@shlinux2> (raw)
In-Reply-To: <3023844.AYbAYqvHUZ@wuerfel>
On Mon, Dec 14, 2015 at 10:35:19AM +0100, Arnd Bergmann wrote:
> On Monday 14 December 2015 15:26:11 Peter Chen wrote:
> > Hi all,
> >
> > There is a known issue that the USB code can't handle USB HUB's
> > external pins well, in that case, it may cause some onboard
> > USB HUBs can't work since their PHY's clock or reset pin needs to
> > operate.
> >
> > The user reported this issue at below:
> > http://www.spinics.net/lists/linux-usb/msg131502.html
> >
> > In this patch set, I add a generic onboard USB HUB driver to
> > handle this problem, the external signals will be configured
> > before usb controller's initialization, it much likes we did
> > it at board code before.
> >
> > The user needs to add this generic hub node at dts to support it.
> >
> > @The udoo users, help to test please.
>
> I still think need to do this properly by representing the hub
> device as a USB device, using power sequencing code like MMC does.
>
> Arnd
I will try to have a patch set for general onboard USB device.
--
Best Regards,
Peter Chen
next prev parent reply other threads:[~2015-12-15 8:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 7:26 [PATCH v2 0/3] USB: add generic onboard USB HUB driver Peter Chen
2015-12-14 7:26 ` [PATCH v2 1/3] usb: misc: generic_onboard_hub: " Peter Chen
2015-12-14 7:26 ` [PATCH v2 2/3] doc: dt-binding: generic onboard USB HUB Peter Chen
2015-12-14 7:26 ` [PATCH v2 3/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2015-12-14 9:35 ` [PATCH v2 0/3] USB: add generic onboard USB HUB driver Arnd Bergmann
2015-12-15 8:33 ` Peter Chen [this message]
2015-12-16 22:59 ` Rob Herring
2015-12-16 23:13 ` Arnd Bergmann
2015-12-17 2:31 ` Peter Chen
2015-12-17 13:49 ` Rob Herring
2015-12-18 7:38 ` Peter Chen
2015-12-17 16:13 ` Alan Stern
2015-12-18 7:42 ` Peter Chen
2015-12-18 15:38 ` Alan Stern
2015-12-21 8:33 ` Peter Chen
2015-12-21 19:40 ` Alan Stern
2015-12-22 3:32 ` Peter Chen
2015-12-22 15:48 ` Alan Stern
2016-01-05 14:36 ` Rob Herring
2016-01-05 15:59 ` Alan Stern
2016-01-06 3:20 ` Peter Chen
2016-01-07 14:18 ` Rob Herring
2016-01-08 3:33 ` Peter Chen
2016-02-24 9:22 ` Peter Chen
2015-12-14 11:26 ` Fabio Estevam
2015-12-15 6:28 ` Peter Chen
2015-12-15 11:32 ` Fabio Estevam
2015-12-16 4:11 ` Peter Chen
2015-12-16 10:11 ` Fabio Estevam
2015-12-16 20:05 ` Maciej S. Szmigiero
2015-12-17 6:57 ` Peter Chen
2015-12-18 23:48 ` Maciej S. Szmigiero
2015-12-21 8:44 ` Peter Chen
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=20151215083259.GA13809@shlinux2 \
--to=peter.chen@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).