summaryrefslogtreecommitdiff
path: root/docs/esp32/tutorial/index.rst
diff options
context:
space:
mode:
authorMaureen Helm <maureen.helm@analog.com>2024-08-05 12:58:36 -0500
committerMaureen Helm <maureen.helm@analog.com>2024-10-01 20:02:01 -0500
commita9803f47115ff2319232e89b6c4c5b380bad5c2b (patch)
tree309dbad27d086597c29faa7b7d24b72361f25cf9 /docs/esp32/tutorial/index.rst
parentf33df7197e30db1e0ede3632a0baebf8f711d7d2 (diff)
zephyr: Allow using devicetree node labels to construct machine objects.
Zephyr v3.7.0 added a new feature to allow getting devices by their devicetree node labels. Use this feature in the MicroPython Zephyr port to simplify constructing machine module objects, including Pin, SPI, I2C, and UART. It's still possible to use the more verbose device names (e.g., gpio@400ff040, i2c@40066000, spi@4002c000), but now we can also use their devicetree node labels (e.g., gpiob, i2c0, spi0). Node labels aren't standardized across all SoC families because they generally try to follow their respective SoC hardware user manual naming convention, however many boards define common labels for devices routed to Arduino headers (e.g., arduino_i2c, arduino_serial, and arduino_spi). That means I2C("arduino_i2c") will work on quite a few boards (>100 in the main Zephyr tree). Signed-off-by: Maureen Helm <maureen.helm@analog.com>
Diffstat (limited to 'docs/esp32/tutorial/index.rst')
0 files changed, 0 insertions, 0 deletions