linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Valentine <valentine.barshak@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] usb: phy: Move R-Car Gen2 driver registration to postcore_inictall
Date: Tue, 05 Nov 2013 19:57:10 +0000	[thread overview]
Message-ID: <52794D96.30209@cogentembedded.com> (raw)
In-Reply-To: <1383063666-4291-1-git-send-email-valentine.barshak@cogentembedded.com>

On 11/01/2013 07:55 PM, Alan Stern wrote:
> On Fri, 1 Nov 2013, Valentine wrote:
>
>> The USB HDC PCI deferred probing could be used on R-Car. But I'm not sure how to make a particular
>> PCI USB HDC device attached to a particular PCI host controller on a particular SoC defer its probing
>> while waiting for the USB phy. At the same time other identical PCI USB HCD devices (with the same PCI id)
>> on the same SoC should be probed as usual.
>
> That is the hard part.  That's what we need to discuss.
>
> And not just on the linux-usb mailing list.  Get other people
> (especially PCI people) involved too.
>
>> We can't use PCI ids here to distinguish between PCI USB HCD devices. Neither can we use PCI busses
>> to distinguish between PCI host controllers, since bus numbers are assigned dynamically.
>
> There must be some way for you to tell which PCI devices use the PHY.
> But I'm not a PCI expert, and I'm not familiar with your platform.
>
>> It looks that it's quite hard to do that without bigger hacks in the PCI USB HCD driver that are
>> most likely not to be used on any other platforms except for R-Car.
>
> You never know what will happen in the future.  Besides, even if nobody
> else needs to do this for a PCI device, you can be certain that the
> same sort of thing will be needed for devices on other buses.  A
> suitably general solution would help them too.
>
> Alan Stern
>

OK, I've tried to come up with more or less universal solution to defer HCD probing
until the external USB phy is ready. I'll start a new thread with the RFC patches in a bit.

Thanks,
Val.

      parent reply	other threads:[~2013-11-05 19:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 16:21 [PATCH] usb: phy: Move R-Car Gen2 driver registration to postcore_inictall Valentine Barshak
2013-10-29 16:59 ` Laurent Pinchart
2013-10-29 17:19 ` Valentine
2013-10-29 23:57 ` Greg KH
2013-10-30  9:56 ` Valentine
2013-10-30 14:12 ` Greg KH
2013-10-30 23:36 ` Valentine
2013-10-31 11:43 ` Valentine
2013-10-31 16:12 ` Ulrich Hecht
2013-10-31 16:29 ` Valentine
2013-10-31 16:54 ` Alan Stern
2013-11-01 13:59 ` Valentine
2013-11-01 14:17 ` Alan Stern
2013-11-01 14:32 ` Greg KH
2013-11-01 15:04 ` Valentine
2013-11-01 15:26 ` Valentine
2013-11-01 15:30 ` Greg KH
2013-11-01 15:33 ` Greg KH
2013-11-01 15:55 ` Alan Stern
2013-11-05 19:57 ` Valentine [this message]

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=52794D96.30209@cogentembedded.com \
    --to=valentine.barshak@cogentembedded.com \
    --cc=linux-sh@vger.kernel.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).