Hi All, Following on from Kyle's email on 2017-11-29 in questioning the "correct" way to deal with the device type being set as spidev, I'm still not clear on the solution. Before I dig deeper into understanding it, is there a reason why we can't have an "spi-generic" device as a catch-all for a DT defined userspace SPI bus? The clear use case for more flexibility in the system is around FPGA based SoCs (in my case a Zynq). In such a scenario the use of userspace is a natural complement to runtime configurable hardware blocks. It would really ease access to (at least somewhat) correct use of the driver if it could be recognised that the kernel might not actually need to know what's on the end of an SPI bus. Best wishes, Henry
Attachment:
signature.asc
Description: OpenPGP digital signature
