On Wed, May 13, 2015 at 07:50:34PM +0200, Maxime Ripard wrote: > On Wed, May 13, 2015 at 08:37:40AM -0700, Greg Kroah-Hartman wrote: > > That doesn't really work. I've been talking to the ACPI people about > > this, and the problem is "don't otherwise have a driver for" is an > > impossible thing to prove, as you never know when a driver is going to > > be loaded from userspace. > > You can easily bind drivers to devices today from userspace, why not > > just use the built-in functionality you have today if you "know" that > > there is no driver for this hardware. > What we're really after here is that we want to have an spidev > instance when we don't even have a device. We do? > And since SPI isn't really doing any kind of hotplug, the only > situation that might be problematic is if we have the DT overlays > registering new devices. Well, we still have the driver loaded from userspace in the future situation as well - the hardware might be static but the software isn't.
Attachment:
signature.asc
Description: Digital signature
