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