On Mon, Apr 18, 2016 at 04:48:27PM +0530, Bhuvanchandra DV wrote: > +++ b/Documentation/ABI/testing/sysfs-bus-spi-spidev > @@ -0,0 +1,8 @@ > +What: /sys/bus/spi/drivers/spidev/new_id > +Date: March 2016 > +Description: > + This allows to load spidev at runtime. new_id file accepts bus > + number and chip select in 'B.C' format. > + e.g. > + To load spidev1.1 at runtime: > + $ echo 1.1 > /sys/bus/spi/drivers/spidev/new_id I would expect a new_id file to allow a new device identifier to be added to a driver at runtime but this isn't doing that, it's specifying by bus and chip select instead which is totally different to how we normally bind SPI devices. That seems likely to cause confusion down the line. I'd expect to be able to supply a DT compatible string or a Linux SPI ID.
Attachment:
signature.asc
Description: PGP signature
