From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
David Laight <David.Laight@ACULAB.COM>,
Stephen Warren <swarren@wwwdotorg.org>,
Alan Stern <stern@rowland.harvard.edu>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Peter.Chen@freescale.com" <Peter.Chen@freescale.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"balbi@ti.com" <balbi@ti.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
"magnus.damm@gmail.com" <magnus.damm@gmail.com>
Subject: Re: [PATCH 1/2] usb: rename 'phy' field of 'struct usb_hcd' to 'transceiver'
Date: Thu, 10 Apr 2014 11:01:05 +0000 [thread overview]
Message-ID: <534679F1.3050607@codethink.co.uk> (raw)
In-Reply-To: <53467720.8000400@cogentembedded.com>
On 10/04/14 11:49, Sergei Shtylyov wrote:
> On 10-04-2014 13:20, David Laight wrote:
>
>>> It doesn't do any pin muxing. It switches SoC internal USB
>>> signals between
>>> USB controllers. The pins remain the same.
>
>> Doesn't something like that already happen for the companion USB1
>> controllers for USB2 ports?
>
> Did you mean USB 1.1 and USB 2.0 controllers by USB1 and USB2?
>
>> That also doesn't sound like you are changing the PHY.
>
> I am changing one of the PHY registers that controls USB port
> (Renesas calls it channel) multiplexing.
>
>> I'd have thought that would happen if you had a single controller
>> that select between multiply PHY.
>
> No, it's not the case.
There is an interesting case, the USB3 shares a PHY with a SATA
and the PCIE and SATA also share a PHY on the R8A7790.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-04-10 11:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 13:57 [PATCH 1/2] usb: rename 'phy' field of 'struct usb_hcd' to 'transceiver' Sergei Shtylyov
2014-04-09 15:31 ` Stephen Warren
2014-04-09 16:27 ` Sergei Shtylyov
2014-04-09 16:48 ` Stephen Warren
[not found] ` <534579D5.10306-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-09 16:53 ` Sergei Shtylyov
2014-04-09 17:37 ` Stephen Warren
2014-04-09 17:52 ` Sergei Shtylyov
2014-04-09 17:56 ` Alan Stern
2014-04-09 18:16 ` Sergei Shtylyov
[not found] ` <53458E95.4080505-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2014-04-09 19:01 ` Stephen Warren
[not found] ` <534598EF.3010102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-04-09 19:06 ` Sergei Shtylyov
2014-04-10 9:20 ` David Laight
2014-04-10 10:49 ` Sergei Shtylyov
2014-04-10 11:01 ` Ben Dooks [this message]
2014-04-10 11:14 ` David Laight
2014-04-10 11:20 ` Ben Dooks
[not found] ` <063D6719AE5E284EB5DD2968C1650D6D0F6F44A4-VkEWCZq2GCInGFn1LkZF6NBPR1lH4CV8@public.gmane.org>
2014-04-10 12:40 ` Sergei Shtylyov
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=534679F1.3050607@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=David.Laight@ACULAB.COM \
--cc=Peter.Chen@freescale.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=stern@rowland.harvard.edu \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
/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).