> I am confused here... Are you having a separate SPI driver create a > platform device and then you have mrstouch to bind to this > intermediate platform device? Are you doing that so you can introduce > I2C interface later? If so I think I prefer how adxl34x and ad7879 > drivers are structured - they are split into core and interface parts > but do not require extra devices/drivers (see in my 'next' brnach). There is no SPI interface to the device. It ended up in the kernel SPI because old versions of the device firmware listed it in the firmware tables as SPI and rather than doing the right thing (correcting the type) the x86 code created an SPI device for it. At a certain level it may be SPI, but it's all hidden behind the firmware on the SCU and nothing to do with Linux SPI at all. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
