public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] USB: add generic onboard USB HUB driver
Date: Thu, 17 Dec 2015 00:13:07 +0100	[thread overview]
Message-ID: <1827708.e1pfN6rEID@wuerfel> (raw)
In-Reply-To: <CAL_Jsq+KAF6FGyOyC0JzODsSVoK4+V6umpj=cANywgui_wOKMg@mail.gmail.com>

On Wednesday 16 December 2015 16:59:39 Rob Herring wrote:
> On Mon, Dec 14, 2015 at 3:35 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Monday 14 December 2015 15:26:11 Peter Chen wrote:
>
> I agree on doing it properly, but am not sure that pwrseq binding for
> MMC is proper. The pwrseq binding is fairly limited and working around
> the driver model IMO. Hubs may also need I2C setup which I don't think
> could be done generically other than some defined sequence of i2c
> transactions. The current project I'm working on needs to use I2C to
> configure the hub to use HSIC mode for example. I really think we need
> a pre-probe driver hook to handle this. That would allow device
> specific setup to live in the driver.
> 
> Perhaps a more simple approach would be just forcing driver probe if a
> DT node is present. I'm not all that familiar with USB drivers, but
> presumably there is some setup before probe like setting the USB
> device address. We'd have to allow doing that later during probe.

Yes, good idea. I was also advocating that approach for MMC at some
point, but the power sequencing made it in the end.

	Arnd

  reply	other threads:[~2015-12-16 23:13 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
2015-12-16 22:59   ` Rob Herring
2015-12-16 23:13     ` Arnd Bergmann [this message]
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=1827708.e1pfN6rEID@wuerfel \
    --to=arnd@arndb.de \
    --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