etc:users:jcmvbkbc:linux-xtensa:esp32s3:gpio
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
etc:users:jcmvbkbc:linux-xtensa:esp32s3:gpio [2024/02/02 18:38] – jcmvbkbc | etc:users:jcmvbkbc:linux-xtensa:esp32s3:gpio [2024/02/05 11:34] (current) – jcmvbkbc | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== GPIO and pin muxing ====== | ====== GPIO and pin muxing ====== | ||
- | Take a look at the [[https:// | + | Take a look at the [[https:// |
+ | {{ : | ||
IO MUX pin settings (selected function, drive strength, pull-up, pull-down, input enable) are controlled by the children of the '' | IO MUX pin settings (selected function, drive strength, pull-up, pull-down, input enable) are controlled by the children of the '' | ||
Line 19: | Line 20: | ||
These properties cannot be changed at runtime (short of writing directly to IO_MUX_n_REG registers). | These properties cannot be changed at runtime (short of writing directly to IO_MUX_n_REG registers). | ||
- | When there' | + | When there' |
< | < | ||
& | & | ||
Line 48: | Line 49: | ||
</ | </ | ||
- | Other properties of a GPIO pin (input/ | + | Other properties of a GPIO pin (input/ |
< | < | ||
i2c0 { | i2c0 { | ||
Line 72: | Line 73: | ||
}; | }; | ||
</ | </ | ||
+ | |||
+ | GPIO pins may need to be in a specific state after boot, but there may be no device that would drive them. In that case they can be brought to that state by the gpio-hog nodes added under the gpio controller node, see [[https:// | ||
+ |
etc/users/jcmvbkbc/linux-xtensa/esp32s3/gpio.1706888326.txt.gz · Last modified: 2024/02/02 18:38 by jcmvbkbc