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