[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1406111520270.890-100000@iolanthe.rowland.org>
Date: Wed, 11 Jun 2014 15:27:13 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Greg KH <gregkh@...uxfoundation.org>
cc: Peter Chen <peter.chen@...escale.com>, <linux-usb@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: Disable bus's drivers_autoprobe before rootfs has mounted
On Wed, 11 Jun 2014, Greg KH wrote:
> We can't break existing systems, so I don't understand the issue here.
> Just don't configure your kernel for a system you don't have / want,
> right?
>
> > > > From what I read code, we can't implement above feature, but I may
> > > > be wrong, if you have some solutions, give me some hints please.
> > > > If there is no solution for above feature, do we agree with exporting
> > > > .drivers_autoprobe for bus driver or something similar?
> > >
> > > I don't understand what you mean by this, care to show me with code?
> >
> > I mean the individual bus driver can't change bus->p->drivers_autoprobe?
> > bus->p->drivers_autoprobe is handled at drivers/base/bus.c.
> >
> > If the individual bus driver can change bus->p->drivers_autoprobe, we
> > can disable autoprobe (auto-binding) during booting.
>
> No, that's a core only thing.
Peter, correct me if this is wrong. It sounds like you want to have a
way for the user to control which gadget driver gets bound to which UDC
driver when everything is compiled into the kernel, nothing is built
as a separate module. Is that the basic idea?
This shouldn't be a problem if you use configfs or libusbg.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists