On Wed, Apr 30, 2014 at 11:06:09AM -0700, Maxime Ripard wrote: > On Tue, Apr 29, 2014 at 11:37:58AM -0700, Mark Brown wrote: > > Why can we not handle this by using sysfs to bind spidev to the > > device? > I just tried it, and apparently, you can't really use this, since spi > devices are created from the device tree (or ACPI) whenever the master > registers. Can you be more specific as to what the issue is here? If we actually have a specific kernel driver for a device I would strongly expect that we would want to use it and not spidev, if we don't have one I don't see the issue. > It doesn't really work either for a device that would be bound to a > driver, that you unbind, and then try to bind to spidev instead. It > looks like the device is released whenever you unbind it, so you can't > really use it afterwards. I guess this is the issue... what exactly is the use case here? I would only expect spidev to be used if there is no in kernel driver for a device.
Attachment:
signature.asc
Description: Digital signature
