Re: RFC: Platform data for onboard USB assets

Greg KH
2011-03-11T16:36:50Z

On Fri, Mar 11, 2011 at 04:27:59PM +0000, Mark Brown wrote:
> On Fri, Mar 11, 2011 at 08:14:21AM -0800, Greg KH wrote:
> > On Fri, Mar 11, 2011 at 04:03:09PM +0000, Mark Brown wrote:
>
> > > Like I say, it's not just MAC addresses that can need configuring this
> > > way - it can be other random "you're wired up this way" type
> > > information that would normally be figured out from the USB IDs.
>
> > And all of that should be done in userspace, like all other device
> > names, I still fail to see what is so different here from any other type
> > of system.
>
> I'm actually not that fussed about the MAC address use case itself and
> do tend to agree with you that that's handlable in userspace but for the
> other things that might need to be configured there's a lot of things
> that for non-discoverable buses we're currently passing through platform
> data so switching to bouncing things through userspace would itself be a
> substantial change from other systems.

But USB _is_ discoverable, that's my point.

> You can't in general rely on the system being neatly abstracted and
> while discoverable buses do avoid many problems in this sort of area
> there are still things which can only be discovered through reference to
> the schematics or similar, especially if you care about the microamps.

Again, that's not USB, so it isn't relevant here.

thanks,

greg k-h