Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added LCD driver options to Kconfig. #5298

Merged
merged 1 commit into from
Jan 14, 2024
Merged

Added LCD driver options to Kconfig. #5298

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions Kconfig
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -346,7 +346,7 @@ menu "LVGL configuration"
bool "Use VG-Lite GPU."

config LV_VG_LITE_USE_GPU_INIT
bool "Enbale VG-Lite custom external 'gpu_init()' function."
bool "Enable VG-Lite custom external 'gpu_init()' function."
default n
depends on LV_USE_DRAW_VG_LITE

Expand Down Expand Up @@ -1265,7 +1265,7 @@ menu "LVGL configuration"
default y
help
This can save some memory, but not much. After the quick access bar is created, it can be hidden by clicking the button at the top left corner of the browsing area, which is very useful for small screen devices.

menuconfig LV_USE_VG_LITE_THORVG
bool "VG-Lite Simulator"
default n
Expand Down Expand Up @@ -1473,6 +1473,22 @@ menu "LVGL configuration"
config LV_USE_EVDEV
bool "Use evdev input driver"
default n

config LV_USE_ST7735
bool "Use ST7735 LCD driver"
default n

config LV_USE_ST7789
bool "Use ST7789 LCD driver"
default n

config LV_USE_ST7796
bool "Use ST7796 LCD driver"
default n

config LV_USE_ILI9341
bool "Use ILI9341 LCD driver"
default n
endmenu

menu "Examples"
Expand Down
3 changes: 1 addition & 2 deletions docs/integration/driver/display/gen_mipi.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ You need to implement two platform-dependent functions:

The only difference between the :cpp:func:`my_lcd_send_cmd()` and :cpp:func:`my_lcd_send_color()` functions is that :cpp:func:`my_lcd_send_cmd()` is used to send short commands and it is expected
complete the transaction when it returns (in other words, it should be blocking), while :cpp:func:`my_lcd_send_color()` is only used to send pixel data, and it is recommended to use
DMA to transmit data in the background. More sophisticated methods can be also implemented, like queing transfers and scheduling them in the background.
DMA to transmit data in the background. More sophisticated methods can be also implemented, like queuing transfers and scheduling them in the background.

Please note that while display flushing is handled by the driver, it is the user's responsibility to call :cpp:func:`lv_display_flush_ready()`
when the color transfer completes. In case of a DMA transfer this is usually done in a transfer ready callback.
Expand Down Expand Up @@ -102,7 +102,6 @@ Example

...


/* Initialize LCD I/O bus, reset LCD */
static int32_t my_lcd_io_init(void)
{
Expand Down
Loading