From 2a34dec70ae971d71be436606101ac41dd07ac82 Mon Sep 17 00:00:00 2001 From: Rop Gonggrijp Date: Mon, 12 Jul 2021 18:28:32 +0200 Subject: [PATCH] typo --- i2c_manager/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i2c_manager/README.md b/i2c_manager/README.md index 00a70c8..a0501c0 100644 --- a/i2c_manager/README.md +++ b/i2c_manager/README.md @@ -10,7 +10,7 @@ `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 anyting special. -I2C Manager can help if you are in a situation where you want to avoid "bus conflicts" on teh 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. +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. If you have (or write) a driver for that 3D-accelerometer that can use I2C Manager (or the I2C HAL and i2cdev abstraction layers that I2C Manager is compatible with) then put I2C Manager in your components directory by cloning the repository from below and in your main program do: