zenermerps/lvgl_esp32_drivers
1
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity

Things suggested by @tore-espressif

Browse source 
See [here](https://github.com/lvgl/lvgl_esp32_drivers/pull/70#pullrequestreview-704302765) in #70
This commit is contained in:
Rop Gonggrijp 2021-07-14 13:12:49 +02:00
parent befa5d0730
commit 93a44492fc
4 changed files with 19 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
Kconfig
View file

@ -4,11 +4,11 @@ menu "LVGL ESP Drivers"
rsource "lvgl_touch/Kconfig"
menu "I2C Port Settings"
depends on LV_I2C && !HAVE_I2C_MANAGER
endmenu
rsource "lvgl_i2c/Kconfig"
endmenu
menu "I2C Port Settings"
depends on LV_I2C && !HAVE_I2C_MANAGER
rsource "lvgl_i2c/Kconfig"
endmenu

6
lvgl_i2c/README.md
View file

@ -8,7 +8,7 @@
### I2C Manager support
`lvgl_esp32_drivers` comes with built-in I2C support by integrating I2C Manager, which is used in case you select a touch sensor or screen that uses the I2C bus. If you're just using LVGL you don't need to do anything special.
`lvgl_esp32_drivers` integrates [I2C Manager](https://github.com/ropg/i2c_manager), which is used in case you select a touch sensor or screen that uses the I2C bus. If you're just using LVGL you don't need to do anything special.
I2C Manager can help if you are in a situation where you want to avoid "bus conflicts" on the I2C bus. Suppose you use LVGL with a touch sensor that uses I2C, and your device also has another I2C device that needs to be read frequently, such as a 3D-accelerometer. ESP-IDF is not inherently "thread-safe". So if you read that from another task than the one LVGL uses to read the touch data, you need some kind of mechanism to keep these communications from interfering.
@ -27,15 +27,13 @@ lvgl_driver_init();
The `lvgl_i2c_locking` part will cause the LVGL I2C driver to play nice with anything else that uses the I2C port(s) through I2C Manager.
Refer to the [I2C Manager GitHub repository](https://github.com/ropg/i2c_manager) for much more information.
 
## Information for LVGL driver developers
I2C support in the LVGL ESP drivers is provided exclusively by the files in this directory. Code from all over the project that was talking to the I2C hardware directly has been replaced by code that communicates through the functions provided in `i2c_manager.h`. I2C is handled by the I2C Manager that was built into `lvlg_esp32_drivers`, but the code would be the same if it was routed through I2C Manager as a separate component. If you are providing a driver, you need not worry about any of this.
I2C support in the LVGL ESP drivers is provided exclusively by the files in this directory. Driver code that uses I2C communicates through the functions provided in `i2c_manager.h`.
 

6
lvgl_tft/Kconfig
View file

@ -1006,10 +1006,16 @@ menu "LVGL TFT Display controller"
config LV_I2C_DISPLAY_PORT_0
bool
prompt "I2C port 0"
help
I2C is shared peripheral managed by I2C Manager. In order to configure I2C Manager (pinout, etc.) see menu
Component config->I2C Port Settings.
config LV_I2C_DISPLAY_PORT_1
bool
prompt "I2C port 1"
help
I2C is shared peripheral managed by I2C Manager. In order to configure I2C Manager (pinout, etc.) see menu
Component config->I2C Port Settings.
endchoice

6
lvgl_touch/Kconfig
View file

@ -492,10 +492,16 @@ menu "LVGL Touch controller"
config LV_I2C_TOUCH_PORT_0
bool
prompt "I2C port 0"
help
I2C is shared peripheral managed by I2C Manager. In order to configure I2C Manager (pinout, etc.) see menu
Component config->I2C Port Settings.
config LV_I2C_TOUCH_PORT_1
bool
prompt "I2C port 1"
help
I2C is shared peripheral managed by I2C Manager. In order to configure I2C Manager (pinout, etc.) see menu
Component config->I2C Port Settings.
endchoice