zephyr

History

Tomasz Bursztyka e18fcbba5a device: Const-ify all device driver instance pointers Now that device_api attribute is unmodified at runtime, as well as all the other attributes, it is possible to switch all device driver instance to be constant. A coccinelle rule is used for this: @r_const_dev_1 disable optional_qualifier @ @@ -struct device * +const struct device * @r_const_dev_2 disable optional_qualifier @ @@ -struct device * const +const struct device * Fixes #27399 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>		2020-09-02 13:48:13 +02:00
..
boards	tests: i2c_slave_api: add nucleo_l476rg as supported test platform	2020-08-13 11:49:12 +02:00
common	device: Const-ify all device driver instance pointers	2020-09-02 13:48:13 +02:00
src	device: Const-ify all device driver instance pointers	2020-09-02 13:48:13 +02:00
CMakeLists.txt	tests: make find_package(Zephyr...) REQUIRED	2020-05-29 10:47:25 +02:00
Kconfig	…
README.txt	tests: i2c_slave_api: document test requirements and design	2020-08-13 11:49:12 +02:00
prj.conf	drivers: move eeprom_slave driver to tests directory	2020-08-13 11:49:12 +02:00
testcase.yaml	sanitycheck: inclusive language	2020-08-27 07:04:07 -04:00

README.txt

I2C Slave API test
##################

This test verifies I2C slave driver implementations using two I2C
controllers on a common bus.  The test is supported by a test-specific
driver that simulates an EEPROM with an I2C bus follower ("slave")
interface.  Data is pre-loaded into the simulated devices outside the
I2C API, and the Zephyr application issues commands to one controller
that are responded to by the simulated EEPROM connected through the
other controller.

In slightly more detail the test has these phases:

* Use API specific to the simulated EEPROM to pre-populate the simulated
  devices with device-specific content.
* Register each simulated EEPROM as a I2C follower device on a bus.
* Issue commands on one bus controller (operating as the bus leader
  (master)) and verify that the data supplied by the other controller
  (as bus follower) match the expected values given the content known to
  be present on the simulated device.

Transfer of commands from one bus controller to the other is
accomplished by hardware through having the SCL (and SDA) signals
shorted to join the two buses.

Presence of this required hardware configuration is identified by the
`i2c_bus_short` fixture.  If the buses are not connected as required,
or the controller driver has bugs, the test will fail one or more I2C
transactions.