xref: /OK3568_Linux_fs/u-boot/drivers/video/Kconfig (revision 4882a59341e53eb6f0b4789bf948001014eff981)
1#
2# Video configuration
3#
4
5menu "Graphics support"
6
7config DM_VIDEO
8	bool "Enable driver model support for LCD/video"
9	depends on DM
10	help
11	  This enables driver model for LCD and video devices. These support
12	  a bitmap display of various sizes and depths which can be drawn on
13	  to display a command-line console or splash screen. Enabling this
14	  option compiles in the video uclass and routes all LCD/video access
15	  through this.
16
17config SPL_DM_VIDEO
18	bool "Enable driver model support for LCD/video in SPL"
19	depends on DM_VIDEO && SPL
20	help
21	  This enables driver model for LCD and video devices in SPL. These support
22	  a bitmap display of various sizes and depths which can be drawn on
23	  to display a command-line console or splash screen. Enabling this
24	  option compiles in the video uclass and routes all LCD/video access
25	  through this.
26
27config SPL_VIDEO_BUF
28	hex "SPL video memory buffer for any use"
29	depends on SPL_DM_VIDEO
30	default 0xa200000
31
32config BACKLIGHT_PWM
33	bool "Generic PWM based Backlight Driver"
34	depends on DM_VIDEO && DM_PWM
35	default y
36	help
37	  If you have a LCD backlight adjustable by PWM, say Y to enable
38	  this driver.
39	  This driver can be use with "simple-panel" and
40	  it understands the standard device tree
41	  (leds/backlight/pwm-backlight.txt)
42
43config BACKLIGHT_GPIO
44	bool "Generic GPIO based Backlight Driver"
45	depends on DM_VIDEO
46	help
47	  If you have a LCD backlight adjustable by GPIO, say Y to enable
48	  this driver.
49	  This driver can be used with "simple-panel" and
50	  it understands the standard device tree
51	  (leds/backlight/gpio-backlight.txt)
52
53config VIDEO_BPP8
54	bool "Support 8-bit-per-pixel displays"
55	depends on DM_VIDEO
56	default y if DM_VIDEO
57	help
58	  Support drawing text and bitmaps onto a 8-bit-per-pixel display.
59	  Enabling this will include code to support this display. Without
60	  this option, such displays will not be supported and console output
61	  will be empty.
62
63config VIDEO_BPP16
64	bool "Support 16-bit-per-pixel displays"
65	depends on DM_VIDEO
66	default y if DM_VIDEO
67	help
68	  Support drawing text and bitmaps onto a 16-bit-per-pixel display.
69	  Enabling this will include code to support this display. Without
70	  this option, such displays will not be supported and console output
71	  will be empty.
72
73config VIDEO_BPP32
74	bool "Support 32-bit-per-pixel displays"
75	depends on DM_VIDEO
76	default y if DM_VIDEO
77	help
78	  Support drawing text and bitmaps onto a 32-bit-per-pixel display.
79	  Enabling this will include code to support this display. Without
80	  this option, such displays will not be supported and console output
81	  will be empty.
82
83config CONSOLE_NORMAL
84	bool "Support a simple text console"
85	depends on DM_VIDEO
86	default y if DM_VIDEO
87	help
88	  Support drawing text on the frame buffer console so that it can be
89	  used as a console. Rotation is not supported by this driver (see
90	  CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
91	  for the display.
92
93config CONSOLE_ROTATION
94	bool "Support rotated displays"
95	depends on DM_VIDEO
96	help
97	  Sometimes, for example if the display is mounted in portrait
98	  mode or even if it's mounted landscape but rotated by 180degree,
99	  we need to rotate our content of the display relative to the
100	  framebuffer, so that user can read the messages which are
101	  printed out. Enable this option to include a text driver which can
102	  support this. The rotation is set by the 'rot' parameter in
103	  struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
104	  degrees, 3=270 degrees.
105
106config CONSOLE_TRUETYPE
107	bool "Support a console that uses TrueType fonts"
108	depends on DM_VIDEO
109	help
110	  TrueTrype fonts can provide outline-drawing capability rather than
111	  needing to provide a bitmap for each font and size that is needed.
112	  With this option you can adjust the text size and use a variety of
113	  fonts. Note that this is noticeably slower than with normal console.
114
115config CONSOLE_TRUETYPE_SIZE
116	int "TrueType font size"
117	depends on CONSOLE_TRUETYPE
118	default 18
119	help
120	  This sets the font size for the console. The size is measured in
121	  pixels and is the nominal height of a character. Note that fonts
122	  are commonly measured in 'points', being 1/72 inch (about 3.52mm).
123	  However that measurement depends on the size of your display and
124	  there is no standard display density. At present there is not a
125	  method to select the display's physical size, which would allow
126	  U-Boot to calculate the correct font size.
127
128config SYS_WHITE_ON_BLACK
129	bool "Display console as white on a black background"
130	default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86
131	help
132	 Normally the display is black on a white background, Enable this
133	 option to invert this, i.e. white on a black background. This can be
134	 better in low-light situations or to reduce eye strain in some
135	 cases.
136
137source "drivers/video/fonts/Kconfig"
138
139config VIDCONSOLE_AS_LCD
140	bool "Use 'vidconsole' when 'lcd' is seen in stdout"
141	depends on DM_VIDEO
142	help
143	  This is a work-around for boards which have 'lcd' in their stdout
144	  environment variable, but have moved to use driver model for video.
145	  In this case the console will no-longer work. While it is possible
146	  to update the environment, the breakage may be confusing for users.
147	  This option will be removed around the end of 2016.
148
149config VIDEO_COREBOOT
150	bool "Enable coreboot framebuffer driver support"
151	depends on X86 && SYS_COREBOOT
152	help
153	  Turn on this option to enable a framebuffer driver when U-Boot is
154	  loaded by coreboot where the graphics device is configured by
155	  coreboot already. This can in principle be used with any platform
156	  that coreboot supports.
157
158config VIDEO_VESA
159	bool "Enable VESA video driver support"
160	default n
161	help
162	  Turn on this option to enable a very simple driver which uses vesa
163	  to discover the video mode and then provides a frame buffer for use
164	  by U-Boot. This can in principle be used with any platform that
165	  supports PCI and video cards that support VESA BIOS Extension (VBE).
166
167config FRAMEBUFFER_SET_VESA_MODE
168	bool "Set framebuffer graphics resolution"
169	depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
170	help
171	  Set VESA/native framebuffer mode (needed for bootsplash and graphical
172	  framebuffer console)
173
174choice
175	prompt "framebuffer graphics resolution"
176	default FRAMEBUFFER_VESA_MODE_117
177	depends on FRAMEBUFFER_SET_VESA_MODE
178	help
179	  This option sets the resolution used for the U-Boot framebuffer (and
180	  bootsplash screen).
181
182config FRAMEBUFFER_VESA_MODE_100
183	bool "640x400 256-color"
184
185config FRAMEBUFFER_VESA_MODE_101
186	bool "640x480 256-color"
187
188config FRAMEBUFFER_VESA_MODE_102
189	bool "800x600 16-color"
190
191config FRAMEBUFFER_VESA_MODE_103
192	bool "800x600 256-color"
193
194config FRAMEBUFFER_VESA_MODE_104
195	bool "1024x768 16-color"
196
197config FRAMEBUFFER_VESA_MODE_105
198	bool "1024x768 256-color"
199
200config FRAMEBUFFER_VESA_MODE_106
201	bool "1280x1024 16-color"
202
203config FRAMEBUFFER_VESA_MODE_107
204	bool "1280x1024 256-color"
205
206config FRAMEBUFFER_VESA_MODE_108
207	bool "80x60 text"
208
209config FRAMEBUFFER_VESA_MODE_109
210	bool "132x25 text"
211
212config FRAMEBUFFER_VESA_MODE_10A
213	bool "132x43 text"
214
215config FRAMEBUFFER_VESA_MODE_10B
216	bool "132x50 text"
217
218config FRAMEBUFFER_VESA_MODE_10C
219	bool "132x60 text"
220
221config FRAMEBUFFER_VESA_MODE_10D
222	bool "320x200 32k-color (1:5:5:5)"
223
224config FRAMEBUFFER_VESA_MODE_10E
225	bool "320x200 64k-color (5:6:5)"
226
227config FRAMEBUFFER_VESA_MODE_10F
228	bool "320x200 16.8M-color (8:8:8)"
229
230config FRAMEBUFFER_VESA_MODE_110
231	bool "640x480 32k-color (1:5:5:5)"
232
233config FRAMEBUFFER_VESA_MODE_111
234	bool "640x480 64k-color (5:6:5)"
235
236config FRAMEBUFFER_VESA_MODE_112
237	bool "640x480 16.8M-color (8:8:8)"
238
239config FRAMEBUFFER_VESA_MODE_113
240	bool "800x600 32k-color (1:5:5:5)"
241
242config FRAMEBUFFER_VESA_MODE_114
243	bool "800x600 64k-color (5:6:5)"
244
245config FRAMEBUFFER_VESA_MODE_115
246	bool "800x600 16.8M-color (8:8:8)"
247
248config FRAMEBUFFER_VESA_MODE_116
249	bool "1024x768 32k-color (1:5:5:5)"
250
251config FRAMEBUFFER_VESA_MODE_117
252	bool "1024x768 64k-color (5:6:5)"
253
254config FRAMEBUFFER_VESA_MODE_118
255	bool "1024x768 16.8M-color (8:8:8)"
256
257config FRAMEBUFFER_VESA_MODE_119
258	bool "1280x1024 32k-color (1:5:5:5)"
259
260config FRAMEBUFFER_VESA_MODE_11A
261	bool "1280x1024 64k-color (5:6:5)"
262
263config FRAMEBUFFER_VESA_MODE_11B
264	bool "1280x1024 16.8M-color (8:8:8)"
265
266config FRAMEBUFFER_VESA_MODE_USER
267	bool "Manually select VESA mode"
268
269endchoice
270
271# Map the config names to an integer (KB).
272config FRAMEBUFFER_VESA_MODE
273	prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
274	hex
275	default 0x100 if FRAMEBUFFER_VESA_MODE_100
276	default 0x101 if FRAMEBUFFER_VESA_MODE_101
277	default 0x102 if FRAMEBUFFER_VESA_MODE_102
278	default 0x103 if FRAMEBUFFER_VESA_MODE_103
279	default 0x104 if FRAMEBUFFER_VESA_MODE_104
280	default 0x105 if FRAMEBUFFER_VESA_MODE_105
281	default 0x106 if FRAMEBUFFER_VESA_MODE_106
282	default 0x107 if FRAMEBUFFER_VESA_MODE_107
283	default 0x108 if FRAMEBUFFER_VESA_MODE_108
284	default 0x109 if FRAMEBUFFER_VESA_MODE_109
285	default 0x10A if FRAMEBUFFER_VESA_MODE_10A
286	default 0x10B if FRAMEBUFFER_VESA_MODE_10B
287	default 0x10C if FRAMEBUFFER_VESA_MODE_10C
288	default 0x10D if FRAMEBUFFER_VESA_MODE_10D
289	default 0x10E if FRAMEBUFFER_VESA_MODE_10E
290	default 0x10F if FRAMEBUFFER_VESA_MODE_10F
291	default 0x110 if FRAMEBUFFER_VESA_MODE_110
292	default 0x111 if FRAMEBUFFER_VESA_MODE_111
293	default 0x112 if FRAMEBUFFER_VESA_MODE_112
294	default 0x113 if FRAMEBUFFER_VESA_MODE_113
295	default 0x114 if FRAMEBUFFER_VESA_MODE_114
296	default 0x115 if FRAMEBUFFER_VESA_MODE_115
297	default 0x116 if FRAMEBUFFER_VESA_MODE_116
298	default 0x117 if FRAMEBUFFER_VESA_MODE_117
299	default 0x118 if FRAMEBUFFER_VESA_MODE_118
300	default 0x119 if FRAMEBUFFER_VESA_MODE_119
301	default 0x11A if FRAMEBUFFER_VESA_MODE_11A
302	default 0x11B if FRAMEBUFFER_VESA_MODE_11B
303	default 0x117 if FRAMEBUFFER_VESA_MODE_USER
304
305config VIDEO_LCD_ANX9804
306	bool "ANX9804 bridge chip"
307	default n
308	---help---
309	Support for the ANX9804 bridge chip, which can take pixel data coming
310	from a parallel LCD interface and translate it on the fy into a DP
311	interface for driving eDP TFT displays. It uses I2C for configuration.
312
313config VIDEO_LCD_SSD2828
314	bool "SSD2828 bridge chip"
315	default n
316	---help---
317	Support for the SSD2828 bridge chip, which can take pixel data coming
318	from a parallel LCD interface and translate it on the fly into MIPI DSI
319	interface for driving a MIPI compatible LCD panel. It uses SPI for
320	configuration.
321
322config VIDEO_LCD_SSD2828_TX_CLK
323	int "SSD2828 TX_CLK frequency (in MHz)"
324	depends on VIDEO_LCD_SSD2828
325	default 0
326	---help---
327	The frequency of the crystal, which is clocking SSD2828. It may be
328	anything in the 8MHz-30MHz range and the exact value should be
329	retrieved from the board schematics. Or in the case of Allwinner
330	hardware, it can be usually found as 'lcd_xtal_freq' variable in
331	FEX files. It can be also set to 0 for selecting PCLK from the
332	parallel LCD interface instead of TX_CLK as the PLL clock source.
333
334config VIDEO_LCD_SSD2828_RESET
335	string "RESET pin of SSD2828"
336	depends on VIDEO_LCD_SSD2828
337	default ""
338	---help---
339	The reset pin of SSD2828 chip. This takes a string in the format
340	understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
341
342config VIDEO_LCD_HITACHI_TX18D42VM
343	bool "Hitachi tx18d42vm LVDS LCD panel support"
344	depends on VIDEO
345	default n
346	---help---
347	Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
348	lcd controller which needs to be initialized over SPI, once that is
349	done they work like a regular LVDS panel.
350
351config VIDEO_LCD_SPI_CS
352	string "SPI CS pin for LCD related config job"
353	depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
354	default ""
355	---help---
356	This is one of the SPI communication pins, involved in setting up a
357	working LCD configuration. The exact role of SPI may differ for
358	different hardware setups. The option takes a string in the format
359	understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
360
361config VIDEO_LCD_SPI_SCLK
362	string "SPI SCLK pin for LCD related config job"
363	depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
364	default ""
365	---help---
366	This is one of the SPI communication pins, involved in setting up a
367	working LCD configuration. The exact role of SPI may differ for
368	different hardware setups. The option takes a string in the format
369	understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
370
371config VIDEO_LCD_SPI_MOSI
372	string "SPI MOSI pin for LCD related config job"
373	depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
374	default ""
375	---help---
376	This is one of the SPI communication pins, involved in setting up a
377	working LCD configuration. The exact role of SPI may differ for
378	different hardware setups. The option takes a string in the format
379	understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
380
381config VIDEO_LCD_SPI_MISO
382	string "SPI MISO pin for LCD related config job (optional)"
383	depends on VIDEO_LCD_SSD2828
384	default ""
385	---help---
386	This is one of the SPI communication pins, involved in setting up a
387	working LCD configuration. The exact role of SPI may differ for
388	different hardware setups. If wired up, this pin may provide additional
389	useful functionality. Such as bi-directional communication with the
390	hardware and LCD panel id retrieval (if the panel can report it). The
391	option takes a string in the format understood by 'name_to_gpio'
392	function, e.g. PH1 for pin 1 of port H.
393
394config VIDEO_MVEBU
395	bool "Armada XP LCD controller"
396	default n
397	---help---
398	Support for the LCD controller integrated in the Marvell
399	Armada XP SoC.
400
401config I2C_EDID
402	bool "Enable EDID library"
403	depends on DM_I2C
404	default n
405	help
406	   This enables library for accessing EDID data from an LCD panel.
407
408config SPL_I2C_EDID
409	bool "Enable EDID library in SPL"
410	depends on DM_I2C && SPL_DM_VIDEO
411	help
412	  This enables library in SPL for accessing EDID data from an LCD panel.
413
414config DISPLAY
415	bool "Enable Display support"
416	depends on DM
417	default n
418	select I2C_EDID
419	help
420	   This supports drivers that provide a display, such as eDP (Embedded
421	   DisplayPort) and HDMI (High Definition Multimedia Interface).
422	   The devices provide a simple interface to start up the display,
423	   read display information and enable it.
424
425config ATMEL_HLCD
426	bool "Enable ATMEL video support using HLCDC"
427	depends on DM_VIDEO
428	help
429	   HLCDC supports video output to an attached LCD panel.
430
431config VIDEO_BROADWELL_IGD
432	bool "Enable Intel Broadwell integrated graphics device"
433	depends on X86
434	help
435	  This enables support for integrated graphics on Intel broadwell
436	  devices. Initialisation is mostly performed by a VGA boot ROM, with
437	  some setup handled by U-Boot itself. The graphics adaptor works as
438	  a VESA device and supports LCD panels, eDP and LVDS outputs.
439	  Configuration of most aspects of device operation is performed using
440	  a special tool which configures the VGA ROM, but the graphics
441	  resolution can be selected in U-Boot.
442
443config VIDEO_IVYBRIDGE_IGD
444	bool "Enable Intel Ivybridge integration graphics support"
445	depends on X86
446	help
447	  This enables support for integrated graphics on Intel ivybridge
448	  devices. Initialisation is mostly performed by a VGA boot ROM, with
449	  some setup handled by U-Boot itself. The graphics adaptor works as
450	  a VESA device and supports LCD panels, eDP and LVDS outputs.
451	  Configuration of most aspects of device operation is performed using
452	  a special tool which configures the VGA ROM, but the graphics
453	  resolution can be selected in U-Boot.
454
455config VIDEO_FSL_DCU_FB
456	bool "Enable Freescale Display Control Unit"
457	depends on VIDEO
458	help
459	 This enables support for Freescale Display Control Unit (DCU4)
460	 module found on Freescale Vybrid and QorIQ family of SoCs.
461
462config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
463	int "Freescale DCU framebuffer size"
464	depends on VIDEO_FSL_DCU_FB
465	default 4194304
466	help
467	 Set maximum framebuffer size to be used for Freescale Display
468	 Controller Unit (DCU4).
469
470source "drivers/video/rockchip/Kconfig"
471source "drivers/video/drm/Kconfig"
472
473config VIDEO_SANDBOX_SDL
474	bool "Enable sandbox video console using SDL"
475	depends on SANDBOX
476	help
477	  When using sandbox you can enable an emulated LCD display which
478	  appears as an SDL (Simple DirectMedia Layer) window. This is a
479	  console device and can display stdout output. Within U-Boot is is
480	  a normal bitmap display and can display images as well as text.
481
482config VIDEO_TEGRA20
483	bool "Enable LCD support on Tegra20"
484	depends on OF_CONTROL
485	help
486	   Tegra20 supports video output to an attached LCD panel as well as
487	   other options such as HDMI. Only the LCD is supported in U-Boot.
488	   This option enables this support which can be used on devices which
489	   have an LCD display connected.
490
491config VIDEO_TEGRA124
492	bool "Enable video support on Tegra124"
493	depends on DM_VIDEO
494	help
495	   Tegra124 supports many video output options including eDP and
496	   HDMI. At present only eDP is supported by U-Boot. This option
497	   enables this support which can be used on devices which
498	   have an eDP display connected.
499
500source "drivers/video/bridge/Kconfig"
501
502config VIDEO
503	bool "Enable legacy video support"
504	depends on !DM_VIDEO
505	help
506	  Define this for video support, without using driver model. Some
507	  drivers use this because they are not yet converted to driver
508	  model. Video drivers typically provide a colour text console and
509	  cursor.
510
511config VIDEO_IPUV3
512	bool "i.MX IPUv3 Core video support"
513	depends on VIDEO && MX6
514	help
515	  This enables framebuffer driver for i.MX processors working
516	  on the IPUv3(Image Processing Unit) internal graphic processor.
517
518config CFB_CONSOLE
519	bool "Enable colour frame buffer console"
520	depends on VIDEO
521	default y if VIDEO
522	help
523	  Enables the colour frame buffer driver. This supports colour
524	  output on a bitmap display from an in-memory frame buffer.
525	  Several colour devices are supported along with various options to
526	  adjust the supported features. The driver is implemented in
527	  cfb_console.c
528
529	  The following defines are needed (cf. smiLynxEM, i8042)
530		VIDEO_FB_LITTLE_ENDIAN	graphic memory organisation
531					(default big endian)
532		VIDEO_HW_RECTFILL	graphic chip supports
533					rectangle fill (cf. smiLynxEM)
534		VIDEO_HW_BITBLT		graphic chip supports
535					bit-blit (cf. smiLynxEM)
536		VIDEO_VISIBLE_COLS	visible pixel columns (cols=pitch)
537		VIDEO_VISIBLE_ROWS	visible pixel rows
538		VIDEO_PIXEL_SIZE	bytes per pixel
539		VIDEO_DATA_FORMAT	graphic data format
540					(0-5, cf. cfb_console.c)
541		VIDEO_FB_ADRS		framebuffer address
542		VIDEO_KBD_INIT_FCT	keyboard int fct (i.e. rx51_kp_init())
543		VIDEO_TSTC_FCT		test char fct (i.e. rx51_kp_tstc)
544		VIDEO_GETC_FCT		get char fct (i.e. rx51_kp_getc)
545		CONFIG_VIDEO_LOGO	display Linux logo in upper left corner
546		CONFIG_VIDEO_BMP_LOGO	use bmp_logo.h instead of linux_logo.h
547					for logo. Requires CONFIG_VIDEO_LOGO
548		CONFIG_CONSOLE_EXTRA_INFO
549					additional board info beside
550					the logo
551		CONFIG_HIDE_LOGO_VERSION
552					do not display bootloader
553					version string
554
555	  When CONFIG_CFB_CONSOLE is defined, the video console is the
556	  default console. The serial console can be forced by setting the
557	  environment 'console=serial'.
558
559config CFB_CONSOLE_ANSI
560	bool "Support ANSI escape sequences"
561	depends on CFB_CONSOLE
562	help
563	  This allows the colour buffer frame buffer driver to support
564	  a limited number of ANSI escape sequences (cursor control,
565	  erase functions and limited graphics rendition control). Normal
566	  output from U-Boot will pass through this filter.
567
568config VGA_AS_SINGLE_DEVICE
569	bool "Set the video as an output-only device"
570	depends on CFB_CONSOLE
571	default y
572	help
573	  If enable the framebuffer device will be initialized as an
574	  output-only device. The Keyboard driver will not be set up. This
575	  may be used if you have no keyboard device, or more than one
576	  (USB Keyboard, AT Keyboard).
577
578config VIDEO_SW_CURSOR
579	bool "Enable a software cursor"
580	depends on CFB_CONSOLE
581	default y if CFB_CONSOLE
582	help
583	  This draws a cursor after the last character. No blinking is
584	  provided. This makes it possible to see the current cursor
585	  position when entering text on the console. It is recommended to
586	  enable this.
587
588config CONSOLE_EXTRA_INFO
589	bool "Display additional board information"
590	depends on CFB_CONSOLE
591	help
592	  Display additional board information strings that normally go to
593	  the serial port. When this option is enabled, a board-specific
594	  function video_get_info_str() is called to get the string for
595	  each line of the display. The function should return the string,
596	  which can be empty if there is nothing to display for that line.
597
598config CONSOLE_SCROLL_LINES
599	int "Number of lines to scroll the console by"
600	depends on CFB_CONSOLE || DM_VIDEO || LCD
601	default 1
602	help
603	  When the console need to be scrolled, this is the number of
604	  lines to scroll by. It defaults to 1. Increasing this makes the
605	  console jump but can help speed up operation when scrolling
606	  is slow.
607
608config SYS_CONSOLE_BG_COL
609	hex "Background colour"
610	depends on CFB_CONSOLE
611	default 0x00
612	help
613	  Defines the background colour for the console. The value is from
614	  0x00 to 0xff and the meaning depends on the graphics card.
615	  Typically, 0x00 means black and 0xff means white. Do not set
616	  the background and foreground to the same colour or you will see
617	  nothing.
618
619config SYS_CONSOLE_FG_COL
620	hex "Foreground colour"
621	depends on CFB_CONSOLE
622	default 0xa0
623	help
624	  Defines the foreground colour for the console. The value is from
625	  0x00 to 0xff and the meaning depends on the graphics card.
626	  Typically, 0x00 means black and 0xff means white. Do not set
627	  the background and foreground to the same colour or you will see
628	  nothing.
629
630config LCD
631	bool "Enable legacy LCD support"
632	help
633	  Define this to enable LCD support (for output to LCD display).
634	  You will also need to select an LCD driver using an additional
635	  CONFIG option. See the README for details. Drives which have been
636	  converted to driver model will instead used CONFIG_DM_VIDEO.
637
638config VIDEO_DW_HDMI
639	bool
640	help
641	  Enables the common driver code for the Designware HDMI TX
642	  block found in SoCs from various vendors.
643	  As this does not provide any functionality by itself (but
644	  rather requires a SoC-specific glue driver to call it), it
645	  can not be enabled from the configuration menu.
646
647config ROCKCHIP_EINK
648	bool "enable rockchip eink driver"
649	help
650	  Enable rockchip eink driver
651source "drivers/video/rk_eink/Kconfig"
652endmenu
653