Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1306005 > unrolled thread

Correct place for USB PHY driver

Back to article view | Back to linux.kernel

Contents

  Correct place for USB PHY driver Mason <slash.tmp@free.fr> - 2016-01-11 11:10 +0100
    Re: Correct place for USB PHY driver Kishon Vijay Abraham I <kishon@ti.com> - 2016-01-11 11:30 +0100
      Re: Correct place for USB PHY driver Mason <slash.tmp@free.fr> - 2016-01-11 13:00 +0100
        Re: Correct place for USB PHY driver Arnd Bergmann <arnd@arndb.de> - 2016-01-11 15:00 +0100

#1306005 — Correct place for USB PHY driver

Hello,

I have a board with a Chipidea controller.
I use a custom PHY driver for it.

Should the PHY driver live in drivers/phy or in drivers/usb/phy ?

I was playing with a modular build and hit this problem:
ERROR: "of_usb_get_phy_mode" [drivers/usb/chipidea/ci_hdrc.ko] undefined!

I'm currently using v4.1.13 and I saw that Arnd fixed something related
probably in a later version:

  http://thread.gmane.org/gmane.linux.ports.arm.kernel/457561

Was this patch accepted upstream?

Regards.

[toc] | [next] | [standalone]

#1306014

hI,

On Monday 11 January 2016 03:37 PM, Mason wrote:
> Hello,
> 
> I have a board with a Chipidea controller.
> I use a custom PHY driver for it.
> 
> Should the PHY driver live in drivers/phy or in drivers/usb/phy ?

All new phy drivers should be in drivers/phy using the generic PHY framework.
> 
> I was playing with a modular build and hit this problem:
> ERROR: "of_usb_get_phy_mode" [drivers/usb/chipidea/ci_hdrc.ko] undefined!
> 
> I'm currently using v4.1.13 and I saw that Arnd fixed something related
> probably in a later version:
> 
>   http://thread.gmane.org/gmane.linux.ports.arm.kernel/457561
> 
> Was this patch accepted upstream?

I think no.

Thanks
Kishon

[toc] | [prev] | [next] | [standalone]

#1306113

On 11/01/2016 11:28, Kishon Vijay Abraham I wrote:

> On Monday 11 January 2016 03:37 PM, Mason wrote:
>
>> I have a board with a Chipidea controller.
>> I use a custom PHY driver for it.
>>
>> Should the PHY driver live in drivers/phy or in drivers/usb/phy ?
> 
> All new phy drivers should be in drivers/phy using the generic PHY framework.
>
>> I was playing with a modular build and hit this problem:
>> ERROR: "of_usb_get_phy_mode" [drivers/usb/chipidea/ci_hdrc.ko] undefined!
>>
>> I'm currently using v4.1.13 and I saw that Arnd fixed something related
>> probably in a later version:
>>
>>   http://thread.gmane.org/gmane.linux.ports.arm.kernel/457561
>>
>> Was this patch accepted upstream?
> 
> I think no.

The driver I use is in drivers/phy and my config has

CONFIG_GENERIC_PHY=y
# CONFIG_USB_PHY is not set

But I do hit the "of_usb_get_phy_mode undefined" error when I
set all of USB to m.

Arnd, do you think your patch needs to be carried over to generic PHY?

Regards.

[toc] | [prev] | [next] | [standalone]

#1306237

On Monday 11 January 2016 12:56:27 Mason wrote:
> On 11/01/2016 11:28, Kishon Vijay Abraham I wrote:
> 
> > On Monday 11 January 2016 03:37 PM, Mason wrote:
> >
> >> I have a board with a Chipidea controller.
> >> I use a custom PHY driver for it.
> >>
> >> Should the PHY driver live in drivers/phy or in drivers/usb/phy ?
> > 
> > All new phy drivers should be in drivers/phy using the generic PHY framework.
> >
> >> I was playing with a modular build and hit this problem:
> >> ERROR: "of_usb_get_phy_mode" [drivers/usb/chipidea/ci_hdrc.ko] undefined!
> >>
> >> I'm currently using v4.1.13 and I saw that Arnd fixed something related
> >> probably in a later version:
> >>
> >>   http://thread.gmane.org/gmane.linux.ports.arm.kernel/457561
> >>
> >> Was this patch accepted upstream?
> > 
> > I think no.
> 
> The driver I use is in drivers/phy and my config has
> 
> CONFIG_GENERIC_PHY=y
> # CONFIG_USB_PHY is not set
> 
> But I do hit the "of_usb_get_phy_mode undefined" error when I
> set all of USB to m.
> 
> Arnd, do you think your patch needs to be carried over to generic PHY?

I think my patch is still needed, I will resubmit it if it doesn't make
it into 4.5-rc1.

In the meantime you can work around the problem by setting CONFIG_USB=y
instead of CONFIG_USB=m.

	Arnd

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web