From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3] usb: hcd: add generic PHY support
Date: Fri, 04 Jul 2014 23:26:05 +0000 [thread overview]
Message-ID: <53B7380D.40504@cogentembedded.com> (raw)
In-Reply-To: <538891DC.605@renesas.com>
Hello.
On 06/25/2014 02:32 PM, Vivek Gautam wrote:
>> From Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Add the generic PHY support, analogous to the USB PHY support. Intended it to be
>> used with the PCI EHCI/OHCI drivers and the xHCI platform driver.
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>> ---
>> This patch is against the 'usb-next' branch of Greg KH's 'usb.git' repo.
>> (commit id = 70d2f61fc7559df3d5be32a9d01efdb9ee1b11d8)
>> Changes in version 3:
>> - rebased the current usb-next.
>> - I tested this patch on my R-Car H2 USB 3.0 driver (not merged yet)
>> drivers/usb/core/hcd.c | 42 ++++++++++++++++++++++++++++++++++++++++--
>> include/linux/usb/hcd.h | 3 ++-
>> 2 files changed, 42 insertions(+), 3 deletions(-)
>> diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
>> index bec31e2..2841149 100644
>> --- a/drivers/usb/core/hcd.c
>> +++ b/drivers/usb/core/hcd.c
[...]
>> @@ -2649,6 +2650,29 @@ int usb_add_hcd(struct usb_hcd *hcd,
>> }
>> }
>>
>> + if (IS_ENABLED(CONFIG_GENERIC_PHY)) {
>> + struct phy *phy = phy_get(hcd->self.controller, "usb");
> The xHCI host controller is going to have two controllers (main and
> shared) USB2 controller and
> USB3 controller. So they will have two different PHYs.
Not necessarily -- in my case there's going be one PHY, even for xHCI.
> For example, the DWC3, which has a xHCI controller, has to have 2
> different phys -- usb2-phy and usb3-phy.
Yes, I understood that.
> So, how the two 'hcd's' will be able to differentiate and get two separate PHYs.
Apparently, by name? I don't see any other way...
> Unfortunately, the xHCI with DWC3 doesn't have a device node too, so
> it needs to have
> a way out to look up the PHYs (in a way suggested by Heikki :
> usb: dwc3: host: convey the PHYs to xhci
> (https://lkml.org/lkml/2014/6/5/585) and related patch series.
> But this also has an issue, since we need to have two separate
> constant strings to distinguish between the two PHYs,
> while creating the lookup table.
I'm sorry, where's the issue?
> So how do you suggest me to get link the two PHYs in DWC3 with the
> XHCI host controller, the issue which i am
> facing currently while working with the patch:
> usb: host: xhci-plat: Add support to get PHYs and the related patch
> series, since we need to handle PHY from the hcd.
Well, I've already spoke out in another thread: you'll have to carry on
with your approach, ignoring the patch starting this thread. I'm sorry for
side-tracking you...
WBR, Sergei
next prev parent reply other threads:[~2014-07-04 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 14:12 [PATCH v3] usb: hcd: add generic PHY support Yoshihiro Shimoda
2014-05-30 14:16 ` Sergei Shtylyov
2014-06-25 10:44 ` Vivek Gautam
2014-07-03 6:12 ` Vivek Gautam
2014-07-04 23:26 ` Sergei Shtylyov [this message]
2014-07-07 4:57 ` Vivek Gautam
2014-08-21 12:56 ` Vivek Gautam
2014-08-21 13:07 ` Sergei Shtylyov
2014-08-21 13:36 ` Vivek Gautam
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=53B7380D.40504@cogentembedded.com \
--to=sergei.shtylyov@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 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.