Re: dwc: Load order of glue diver and core driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Thu, Aug 16, 2012 at 11:34:26AM +0530, Pratyush Anand wrote:
> May be something silly, but I am not getting it :(
> 
> Probe of glue logic driver such as dwc3_exynos_probe must be called
> before core driver ie dwc3_probe.
> 
> Since both drivers are called through module_init, How do we insure that?

There are no requirements actually. dwc3.ko will only probe when there's
a device/driver match. Even if you register dwc3.ko first (modprobe
dwc3.ko) there will be no match because the device is created by the
glue layer. If you let udev handle device probing, you will see that it
will happen with no problems.

-> $ARCH creates glue layer's device
-> udev loads dwc3-$ARCH.ko
-> dwc3-$ARCH.ko creates dwc3.ko's device
-> udev loads dwc3.ko

and everybody's happy ;-)

-- 
balbi

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux