From: Sergei Shtylyov
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?
That also doesn't sound like you are changing the PHY.
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
From: Ben Dooks
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
On 10/04/14 12:14, David Laight wrote:
From: Ben Dooks
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
On 10-04-2014 15:14, 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
Return to the 'phy' field of 'struct usb_hcd' its historic name 'transceiver'.
This is in preparation to adding the generic PHY support.
Signed-off-by: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
---
This patch is against the 'usb-next' branch of Greg KH's 'usb.git' repo.
On 04/09/2014 07:57 AM, Sergei Shtylyov wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name
'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we should be adding generic
transceiver support not generic PHY
Hello.
On 04/09/2014 07:31 PM, Stephen Warren wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name 'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we should be adding generic
transceiver support not
On 04/09/2014 10:27 AM, Sergei Shtylyov wrote:
Hello.
On 04/09/2014 07:31 PM, Stephen Warren wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name
'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we
On 04/09/2014 08:48 PM, Stephen Warren wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name
'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we should be adding generic
transceiver support not generic PHY
On 04/09/2014 10:53 AM, Sergei Shtylyov wrote:
On 04/09/2014 08:48 PM, Stephen Warren wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name
'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we should be
On 04/09/2014 09:37 PM, Stephen Warren wrote:
Return to the 'phy' field of 'struct usb_hcd' its historic name
'transceiver'.
This is in preparation to adding the generic PHY support.
Surely if the correct term is transceiver, we should be adding generic
transceiver support not generic PHY
On Wed, 9 Apr 2014, Sergei Shtylyov wrote:
Ok, the existing field is being replaced by something? I didn't get that
No, not replaced. I'm adding the support for generic PHY to the existing
USB PHY support. I thought that was clear from the changelog.
from the patch description; I
Hello.
On 04/09/2014 09:56 PM, Alan Stern wrote:
Ok, the existing field is being replaced by something? I didn't get that
No, not replaced. I'm adding the support for generic PHY to the existing
USB PHY support. I thought that was clear from the changelog.
from the patch
On 04/09/2014 12:16 PM, Sergei Shtylyov wrote:
Hello.
On 04/09/2014 09:56 PM, Alan Stern wrote:
Ok, the existing field is being replaced by something? I didn't get
that
No, not replaced. I'm adding the support for generic PHY to the
existing
USB PHY support. I thought that was
On 04/09/2014 11:01 PM, Stephen Warren wrote:
Ok, the existing field is being replaced by something? I didn't get
that
No, not replaced. I'm adding the support for generic PHY to the
existing
USB PHY support. I thought that was clear from the changelog.
from the patch description; I
16 matches
Mail list logo
