On 06/04/2014 01:17 PM, Mark Brown wrote:
You're saying you're controlling it from userspace. This is a particular detail of what you are doing in your system. You happen to want to control the devices you are hanging off the system with userspace drivers but that's just what you're doing right now.
Sorry, I don't get it. Yes, spidev is to control stuff from user space just like i2c-dev however bad that might sound.
No, that's in the controller node - the chip selects are described there. The child node references a chip select number that the master has and describes what's connected to that chip select.
Well, unfortunately SPI without any chip select is just plain simply useless. It won't work.
It's a perfectly fine way of controlling things from userspace if that's a sensible way of controlling devices but that does not mean you should describe it in the device tree in that fashion.
Only that without describing such a chip select in the device tree spidev won't ever work.
I don't see us reaching any consensus here therefore I retreat. I will re-submit the whole thing without spidev however sad having to see that useful feature being dropped.
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
