Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Software implementation
The following picture shows how the software laye
[[File:TBDSBCX-Android-4.4.3-SPI.png|thumb|center|600px|Software stack]]
The solution depicted on the left is fully compliant with the Android/Android Things recommendations. The access to the I/O interface—the SPI bus in this case—is managed by the Peripheral Manager and by a specific service.
The solution depicted on the right is the one described in this Technical Note. From the application point of view, it is consistent with the Android Things APIs. However, it leverages is easier to implement thanks to the direct access to the device file associated with the SPI bus. === Requirements ===To implement such solution, the following requirements must be met:*The Linux kernel must support [https://www.kernel.org/doc/Documentation/spi/spidev spidev]*The device tree must be modified in order to instantiate the SPI bus to be accessed*The device file associated with the SPI bus
=== Managing the device connection ===