On Tue, Aug 04, 2015 at 08:39:20AM +0200, Martin Sperl wrote: > How could we implement additional per spi-device parameters that > are interesting to the spi-master. Define parameters for the slave and read them from the slave device node at some appropriate point. Please send patches for review, your sketches look fine without context but when written as a proper patch other issues may become obvious. Given that setup() gets called repeatedly a one time call may be more sensible. > Examples for the spi-bcm2835 master for example could be: > * set minimum transfer size for dma to something else but the default > (of 96 bytes - setting for something high would disable it) > * change polling transfer limits (i.e disable it) Why would these things be configured in the device tree in the first place? They don't look like things that should be device tree properties, they look like something the kernel should figure out at runtime - the system tuning may change as the kernel evolves or depending on userspace needs.
Attachment:
signature.asc
Description: Digital signature
