Added LCD driver options to Kconfig. (#5298)

Co-authored-by: Gabor Kiss-Vamosi <kisvegabor@gmail.com>

Kconfig

@@ -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
 
@@ -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"

docs/integration/driver/display/gen_mipi.rst

@@ -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.
@@ -102,7 +102,6 @@ Example
 
 	...
 
-
 	/* Initialize LCD I/O bus, reset LCD */
 	static int32_t my_lcd_io_init(void)
 	{