> The device tree defines the SPI controller associated with mikroBUS SPI > pins. The driver on match queries and takes a reference to the SPI > controller but does nothing with it. Once a mikroBUS add-on board is > detected (by passing manifest using sysfs or reading from 1-wire EEPROM), > the driver parses the manifest, and if it detects an SPI device in manifest, > it registers SPI device along with setting properties such as `chip_select`, > `max_speed_hz`, `mode`, etc., How complex can the description of the hardware be in the manifest? Could i describe an SPI to I2C converter? And then a few temperature sensors, a fan controller, and a GPIO controller on that I2C bus? And the GPIO controller is then used for LEDs and a push button? DT overlays could describe that. Can the manifest? Andrew _______________________________________________ greybus-dev mailing list -- greybus-dev@xxxxxxxxxxxxxxxx To unsubscribe send an email to greybus-dev-leave@xxxxxxxxxxxxxxxx
|