Re: [PATCH v3 1/1] usb: ulpi: ulpi_init should be executed in subsys_initcall

[Lu, Baolu]

On 05/26/2015 10:50 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, May 25, 2015 at 02:24:00PM +0800, Lu, Baolu wrote:
> > On 05/23/2015 12:08 AM, David Cohen wrote:
> > > Hi,
> > >
> > > On Fri, May 22, 2015 at 07:29:15PM +0800, Lu Baolu wrote:
> > > > Phy drivers and the ulpi interface providers depend on the
> > > > registeration of the ulpi bus.  Ulpi registers the bus in
> > > > module_init(). This could result in a load order issue, i.e.
> > > It's still not an issue :(
> > > I'd say "unnecessary probe delays".
> > I managed to boot a kernel built from the top of Felipe's
> > remotes/origin/next branch under an Ubuntu environment
> > on Intel's Bay Trail tablet.
> >
> > The same panic (as I found in the Android environment previously)
> > shows up as well. And if I replace module_init() with sys_initcall(),
> > the panic disappears.
> the problem is something else... Moving things around in the init levels
> is just a workaround for another issue. Seems like there's some missing
> EPROBE_DEFER somewhere.

Yes, I agree.

Heikki, I assume "missing EPROBE_DEFER issue" will be fixed by
Sasha's patch. I will resend the patch with a new commit
message.

Thanks,
Baolu

>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/