@@ -10,16 +10,15 @@ description: |
1010 pin properties.
1111
1212 Each Zephyr-based application has its own set of pin muxing/pin configuration
13- requirements. The next use ESP-WROVER-KIT's I2C_0 to illustrate how one could
14- change a node's pin state properties. Though based on a particular board, the
15- same following steps can be tweaked to address specifics of any other target
16- board.
13+ requirements. The next steps use ESP-WROVER-KIT's I2C_0 to illustrate how one
14+ could change a node's pin state properties. Though based on a particular board,
15+ the same steps can be tweaked to address specifics of any other target board.
1716
1817 Suppose an application running on top of the ESP-WROVER-KIT board, for some
1918 reason it needs I2C_0's SDA signal to be routed to GPIO_33. When looking at
2019 that board's original device tree source file (i.e., 'esp_wrover_kit.dts'),
21- you'll note that the I2C_0 node is already assigned to a set of states. Below
22- is highlighted the information that most interests us on that file
20+ you'll notice that the I2C_0 node is already assigned to a set of states.
21+ Below is highlighted the information that most interests us on that file
2322
2423
2524 #include "esp_wrover_kit-pinctrl.dtsi"
@@ -66,7 +65,7 @@ description: |
6665 target SoC in the following URL
6766
6867
69- https://github.com/zephyrproject-rtos/hal_espressif/tree/include/dt-bindings/pinctrl
68+ https://github.com/zephyrproject-rtos/hal_espressif/tree/zephyr/ include/dt-bindings/pinctrl
7069
7170
7271 The ESP-WROVER-KIT board is based on the ESP32 SoC, in that case, we search
@@ -144,7 +143,7 @@ child-binding:
144143 required : true
145144 type : int
146145 description : |
147- Integer array , represents pin mux settings.
146+ Integer value , represents pin mux settings.
148147 With:
149148 - pin: The gpio pin number (0, 1, ..., GPIO_NUM_MAX)
150149 - sigi: The input signal assigned to a pin, if not available, it gets
0 commit comments