5 menu "Graphics support"
8 bool "Enable driver model support for LCD/video"
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
18 bool "Enable panel backlight uclass support"
22 This provides backlight uclass driver that enables basic panel
25 config VIDEO_PCI_DEFAULT_FB_SIZE
26 hex "Default framebuffer size to use if no drivers request it"
28 default 0x1000000 if X86 && PCI
29 default 0 if !(X86 && PCI)
31 Generally, video drivers request the amount of memory they need for
32 the frame buffer when they are bound, by setting the size field in
33 struct video_uc_plat. That memory is then reserved for use after
34 relocation. But PCI drivers cannot be bound before relocation unless
35 they are mentioned in the devicetree.
37 With this value set appropriately, it is possible for PCI video
38 devices to have a framebuffer allocated by U-Boot.
40 Note: the framebuffer needs to be large enough to store all pixels at
41 maximum resolution. For example, at 1920 x 1200 with 32 bits per
42 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
45 bool "Enable copying the frame buffer to a hardware copy"
48 On some machines (e.g. x86), reading from the frame buffer is very
49 slow because it is uncached. To improve performance, this feature
50 allows the frame buffer to be kept in cached memory (allocated by
51 U-Boot) and then copied to the hardware frame-buffer as needed.
53 To use this, your video driver must set @copy_base in
57 bool "Generic PWM based Backlight Driver"
58 depends on BACKLIGHT && DM_PWM
61 If you have a LCD backlight adjustable by PWM, say Y to enable
63 This driver can be use with "simple-panel" and
64 it understands the standard device tree
65 (leds/backlight/pwm-backlight.txt)
68 bool "Generic GPIO based Backlight Driver"
71 If you have a LCD backlight adjustable by GPIO, say Y to enable
73 This driver can be used with "simple-panel" and
74 it understands the standard device tree
75 (leds/backlight/gpio-backlight.txt)
78 bool "Enable vidconsole commands lcdputs and setcurs"
82 Enabling this will provide 'setcurs' and 'lcdputs' commands which
83 support cursor positioning and drawing strings on video framebuffer.
86 bool "Support 8-bit-per-pixel displays"
90 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
91 Enabling this will include code to support this display. Without
92 this option, such displays will not be supported and console output
96 bool "Support 16-bit-per-pixel displays"
100 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
101 Enabling this will include code to support this display. Without
102 this option, such displays will not be supported and console output
106 bool "Support 32-bit-per-pixel displays"
110 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
111 Enabling this will include code to support this display. Without
112 this option, such displays will not be supported and console output
116 bool "Support ANSI escape sequences in video console"
120 Enable ANSI escape sequence decoding for a more fully functional
123 config VIDEO_MIPI_DSI
124 bool "Support MIPI DSI interface"
127 Support MIPI DSI interface for driving a MIPI compatible device.
128 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
129 serial interface between a host processor and a display module.
131 config CONSOLE_NORMAL
132 bool "Support a simple text console"
134 default y if DM_VIDEO
136 Support drawing text on the frame buffer console so that it can be
137 used as a console. Rotation is not supported by this driver (see
138 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
141 config CONSOLE_ROTATION
142 bool "Support rotated displays"
145 Sometimes, for example if the display is mounted in portrait
146 mode or even if it's mounted landscape but rotated by 180degree,
147 we need to rotate our content of the display relative to the
148 framebuffer, so that user can read the messages which are
149 printed out. Enable this option to include a text driver which can
150 support this. The rotation is set by the 'rot' parameter in
151 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
152 degrees, 3=270 degrees.
154 config CONSOLE_TRUETYPE
155 bool "Support a console that uses TrueType fonts"
158 TrueTrype fonts can provide outline-drawing capability rather than
159 needing to provide a bitmap for each font and size that is needed.
160 With this option you can adjust the text size and use a variety of
161 fonts. Note that this is noticeably slower than with normal console.
163 config DM_PANEL_HX8238D
164 bool "Enable Himax HX-8238D LCD driver"
167 Support for HX-8238D LCD Panel
168 The HX8238-D is a single chip controller and driver LSI that
169 integrates the power circuit.
170 It can drive a maximum 960x240 dot graphics on a-TFT panel
171 displays in 16M colors with dithering.
173 config CONSOLE_TRUETYPE_SIZE
174 int "TrueType font size"
175 depends on CONSOLE_TRUETYPE
178 This sets the font size for the console. The size is measured in
179 pixels and is the nominal height of a character. Note that fonts
180 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
181 However that measurement depends on the size of your display and
182 there is no standard display density. At present there is not a
183 method to select the display's physical size, which would allow
184 U-Boot to calculate the correct font size.
186 config SYS_WHITE_ON_BLACK
187 bool "Display console as white on a black background"
188 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
190 Normally the display is black on a white background, Enable this
191 option to invert this, i.e. white on a black background. This can be
192 better in low-light situations or to reduce eye strain in some
196 bool "Skip framebuffer clear"
198 If firmware (whatever loads u-boot) has already put a splash image
199 on screen, you might want to preserve it until whatever u-boot
200 loads takes over the screen. This, for example, can be used to
201 keep splash image on screen until grub graphical boot menu starts.
204 bool "Enable panel uclass support"
208 This provides panel uclass driver that enables basic panel support.
211 bool "Enable simple panel support"
212 depends on PANEL && BACKLIGHT && DM_GPIO
215 This turns on a simple panel driver that enables a compatible
218 source "drivers/video/fonts/Kconfig"
220 config VIDCONSOLE_AS_LCD
221 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
224 This is a work-around for boards which have 'lcd' or 'vga' in their
225 stdout environment variable, but have moved to use driver model for
226 video. In this case the console will no-longer work. While it is
227 possible to update the environment, the breakage may be confusing for
228 users. This option will be removed around the end of 2020.
230 config VIDCONSOLE_AS_NAME
231 string "Use 'vidconsole' when string defined here is seen in stdout"
232 depends on VIDCONSOLE_AS_LCD
233 default "lcd" if LCD || TEGRA_COMMON
234 default "vga" if !LCD
236 This is a work-around for boards which have 'lcd' or 'vga' in their
237 stdout environment variable, but have moved to use driver model for
238 video. In this case the console will no-longer work. While it is
239 possible to update the environment, the breakage may be confusing for
240 users. This option will be removed around the end of 2020.
242 config VIDEO_COREBOOT
243 bool "Enable coreboot framebuffer driver support"
246 Turn on this option to enable a framebuffer driver when U-Boot is
247 loaded by coreboot where the graphics device is configured by
248 coreboot already. This can in principle be used with any platform
249 that coreboot supports.
252 bool "Enable EFI framebuffer driver support"
255 Turn on this option to enable a framebuffeer driver when U-Boot is
256 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
257 the graphics device is configured by the EFI BIOS already. This can
258 in principle be used with any platform that has an EFI BIOS.
261 bool "Enable VESA video driver support"
264 Turn on this option to enable a very simple driver which uses vesa
265 to discover the video mode and then provides a frame buffer for use
266 by U-Boot. This can in principle be used with any platform that
267 supports PCI and video cards that support VESA BIOS Extension (VBE).
269 config FRAMEBUFFER_SET_VESA_MODE
270 bool "Set framebuffer graphics resolution"
271 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
273 Set VESA/native framebuffer mode (needed for bootsplash and graphical
277 prompt "framebuffer graphics resolution"
278 default FRAMEBUFFER_VESA_MODE_118
279 depends on FRAMEBUFFER_SET_VESA_MODE
281 This option sets the resolution used for the U-Boot framebuffer (and
284 config FRAMEBUFFER_VESA_MODE_100
285 bool "640x400 256-color"
287 config FRAMEBUFFER_VESA_MODE_101
288 bool "640x480 256-color"
290 config FRAMEBUFFER_VESA_MODE_102
291 bool "800x600 16-color"
293 config FRAMEBUFFER_VESA_MODE_103
294 bool "800x600 256-color"
296 config FRAMEBUFFER_VESA_MODE_104
297 bool "1024x768 16-color"
299 config FRAMEBUFFER_VESA_MODE_105
300 bool "1024x768 256-color"
302 config FRAMEBUFFER_VESA_MODE_106
303 bool "1280x1024 16-color"
305 config FRAMEBUFFER_VESA_MODE_107
306 bool "1280x1024 256-color"
308 config FRAMEBUFFER_VESA_MODE_108
311 config FRAMEBUFFER_VESA_MODE_109
314 config FRAMEBUFFER_VESA_MODE_10A
317 config FRAMEBUFFER_VESA_MODE_10B
320 config FRAMEBUFFER_VESA_MODE_10C
323 config FRAMEBUFFER_VESA_MODE_10D
324 bool "320x200 32k-color (1:5:5:5)"
326 config FRAMEBUFFER_VESA_MODE_10E
327 bool "320x200 64k-color (5:6:5)"
329 config FRAMEBUFFER_VESA_MODE_10F
330 bool "320x200 16.8M-color (8:8:8)"
332 config FRAMEBUFFER_VESA_MODE_110
333 bool "640x480 32k-color (1:5:5:5)"
335 config FRAMEBUFFER_VESA_MODE_111
336 bool "640x480 64k-color (5:6:5)"
338 config FRAMEBUFFER_VESA_MODE_112
339 bool "640x480 16.8M-color (8:8:8)"
341 config FRAMEBUFFER_VESA_MODE_113
342 bool "800x600 32k-color (1:5:5:5)"
344 config FRAMEBUFFER_VESA_MODE_114
345 bool "800x600 64k-color (5:6:5)"
347 config FRAMEBUFFER_VESA_MODE_115
348 bool "800x600 16.8M-color (8:8:8)"
350 config FRAMEBUFFER_VESA_MODE_116
351 bool "1024x768 32k-color (1:5:5:5)"
353 config FRAMEBUFFER_VESA_MODE_117
354 bool "1024x768 64k-color (5:6:5)"
356 config FRAMEBUFFER_VESA_MODE_118
357 bool "1024x768 16.8M-color (8:8:8)"
359 config FRAMEBUFFER_VESA_MODE_119
360 bool "1280x1024 32k-color (1:5:5:5)"
362 config FRAMEBUFFER_VESA_MODE_11A
363 bool "1280x1024 64k-color (5:6:5)"
365 config FRAMEBUFFER_VESA_MODE_11B
366 bool "1280x1024 16.8M-color (8:8:8)"
368 config FRAMEBUFFER_VESA_MODE_USER
369 bool "Manually select VESA mode"
373 # Map the config names to an integer (KB).
374 config FRAMEBUFFER_VESA_MODE
375 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
377 default 0x100 if FRAMEBUFFER_VESA_MODE_100
378 default 0x101 if FRAMEBUFFER_VESA_MODE_101
379 default 0x102 if FRAMEBUFFER_VESA_MODE_102
380 default 0x103 if FRAMEBUFFER_VESA_MODE_103
381 default 0x104 if FRAMEBUFFER_VESA_MODE_104
382 default 0x105 if FRAMEBUFFER_VESA_MODE_105
383 default 0x106 if FRAMEBUFFER_VESA_MODE_106
384 default 0x107 if FRAMEBUFFER_VESA_MODE_107
385 default 0x108 if FRAMEBUFFER_VESA_MODE_108
386 default 0x109 if FRAMEBUFFER_VESA_MODE_109
387 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
388 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
389 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
390 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
391 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
392 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
393 default 0x110 if FRAMEBUFFER_VESA_MODE_110
394 default 0x111 if FRAMEBUFFER_VESA_MODE_111
395 default 0x112 if FRAMEBUFFER_VESA_MODE_112
396 default 0x113 if FRAMEBUFFER_VESA_MODE_113
397 default 0x114 if FRAMEBUFFER_VESA_MODE_114
398 default 0x115 if FRAMEBUFFER_VESA_MODE_115
399 default 0x116 if FRAMEBUFFER_VESA_MODE_116
400 default 0x117 if FRAMEBUFFER_VESA_MODE_117
401 default 0x118 if FRAMEBUFFER_VESA_MODE_118
402 default 0x119 if FRAMEBUFFER_VESA_MODE_119
403 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
404 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
405 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
407 config VIDEO_LCD_ANX9804
408 bool "ANX9804 bridge chip"
411 Support for the ANX9804 bridge chip, which can take pixel data coming
412 from a parallel LCD interface and translate it on the fy into a DP
413 interface for driving eDP TFT displays. It uses I2C for configuration.
415 config VIDEO_LCD_ORISETECH_OTM8009A
416 bool "OTM8009A DSI LCD panel support"
418 select VIDEO_MIPI_DSI
421 Say Y here if you want to enable support for Orise Technology
422 otm8009a 480x800 dsi 2dl panel.
424 config VIDEO_LCD_RAYDIUM_RM68200
425 bool "RM68200 DSI LCD panel support"
427 select VIDEO_MIPI_DSI
430 Say Y here if you want to enable support for Raydium RM68200
431 720x1280 DSI video mode panel.
433 config VIDEO_LCD_SSD2828
434 bool "SSD2828 bridge chip"
437 Support for the SSD2828 bridge chip, which can take pixel data coming
438 from a parallel LCD interface and translate it on the fly into MIPI DSI
439 interface for driving a MIPI compatible LCD panel. It uses SPI for
442 config VIDEO_LCD_SSD2828_TX_CLK
443 int "SSD2828 TX_CLK frequency (in MHz)"
444 depends on VIDEO_LCD_SSD2828
447 The frequency of the crystal, which is clocking SSD2828. It may be
448 anything in the 8MHz-30MHz range and the exact value should be
449 retrieved from the board schematics. Or in the case of Allwinner
450 hardware, it can be usually found as 'lcd_xtal_freq' variable in
451 FEX files. It can be also set to 0 for selecting PCLK from the
452 parallel LCD interface instead of TX_CLK as the PLL clock source.
454 config VIDEO_LCD_SSD2828_RESET
455 string "RESET pin of SSD2828"
456 depends on VIDEO_LCD_SSD2828
459 The reset pin of SSD2828 chip. This takes a string in the format
460 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
462 config VIDEO_LCD_TDO_TL070WSH30
463 bool "TDO TL070WSH30 DSI LCD panel support"
465 select VIDEO_MIPI_DSI
468 Say Y here if you want to enable support for TDO TL070WSH30
469 1024x600 DSI video mode panel.
471 config VIDEO_LCD_HITACHI_TX18D42VM
472 bool "Hitachi tx18d42vm LVDS LCD panel support"
475 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
476 lcd controller which needs to be initialized over SPI, once that is
477 done they work like a regular LVDS panel.
479 config VIDEO_LCD_SPI_CS
480 string "SPI CS pin for LCD related config job"
481 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
484 This is one of the SPI communication pins, involved in setting up a
485 working LCD configuration. The exact role of SPI may differ for
486 different hardware setups. The option takes a string in the format
487 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
489 config VIDEO_LCD_SPI_SCLK
490 string "SPI SCLK pin for LCD related config job"
491 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
494 This is one of the SPI communication pins, involved in setting up a
495 working LCD configuration. The exact role of SPI may differ for
496 different hardware setups. The option takes a string in the format
497 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
499 config VIDEO_LCD_SPI_MOSI
500 string "SPI MOSI pin for LCD related config job"
501 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
504 This is one of the SPI communication pins, involved in setting up a
505 working LCD configuration. The exact role of SPI may differ for
506 different hardware setups. The option takes a string in the format
507 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
509 config VIDEO_LCD_SPI_MISO
510 string "SPI MISO pin for LCD related config job (optional)"
511 depends on VIDEO_LCD_SSD2828
514 This is one of the SPI communication pins, involved in setting up a
515 working LCD configuration. The exact role of SPI may differ for
516 different hardware setups. If wired up, this pin may provide additional
517 useful functionality. Such as bi-directional communication with the
518 hardware and LCD panel id retrieval (if the panel can report it). The
519 option takes a string in the format understood by 'name_to_gpio'
520 function, e.g. PH1 for pin 1 of port H.
522 source "drivers/video/meson/Kconfig"
525 bool "Armada XP LCD controller"
528 Support for the LCD controller integrated in the Marvell
532 bool "Enable OMAP3+ DSS Support"
533 depends on ARCH_OMAP2PLUS
535 This enables the Display subsystem (DSS) on OMAP3+ boards.
538 bool "Enable EDID library"
541 This enables library for accessing EDID data from an LCD panel.
544 bool "Enable Display support"
549 This supports drivers that provide a display, such as eDP (Embedded
550 DisplayPort) and HDMI (High Definition Multimedia Interface).
551 The devices provide a simple interface to start up the display,
552 read display information and enable it.
555 bool "Enable NXP TDA19988 support"
559 This enables support for the NXP TDA19988 HDMI encoder. This encoder
560 will convert RGB data streams into HDMI-encoded signals.
563 bool "Enable ATMEL video support using HLCDC"
565 HLCDC supports video output to an attached LCD panel.
567 source "drivers/video/ti/Kconfig"
569 config LOGICORE_DP_TX
570 bool "Enable Logicore DP TX driver"
573 Enable the driver for the transmitter part of the Xilinx LogiCORE
574 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
575 video interface as defined by VESA DisplayPort v1.2.
577 Note that this is a pure transmitter device, and has no display
578 capabilities by itself.
580 config VIDEO_BROADWELL_IGD
581 bool "Enable Intel Broadwell integrated graphics device"
584 This enables support for integrated graphics on Intel broadwell
585 devices. Initialisation is mostly performed by a VGA boot ROM, with
586 some setup handled by U-Boot itself. The graphics adaptor works as
587 a VESA device and supports LCD panels, eDP and LVDS outputs.
588 Configuration of most aspects of device operation is performed using
589 a special tool which configures the VGA ROM, but the graphics
590 resolution can be selected in U-Boot.
592 config VIDEO_IVYBRIDGE_IGD
593 bool "Enable Intel Ivybridge integration graphics support"
596 This enables support for integrated graphics on Intel ivybridge
597 devices. Initialisation is mostly performed by a VGA boot ROM, with
598 some setup handled by U-Boot itself. The graphics adaptor works as
599 a VESA device and supports LCD panels, eDP and LVDS outputs.
600 Configuration of most aspects of device operation is performed using
601 a special tool which configures the VGA ROM, but the graphics
602 resolution can be selected in U-Boot.
604 config VIDEO_FSL_DCU_FB
605 bool "Enable Freescale Display Control Unit"
606 depends on VIDEO || DM_VIDEO
608 This enables support for Freescale Display Control Unit (DCU4)
609 module found on Freescale Vybrid and QorIQ family of SoCs.
611 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
612 int "Freescale DCU framebuffer size"
613 depends on VIDEO_FSL_DCU_FB
616 Set maximum framebuffer size to be used for Freescale Display
617 Controller Unit (DCU4).
619 source "drivers/video/rockchip/Kconfig"
621 config VIDEO_ARM_MALIDP
622 bool "Enable Arm Mali Display Processor support"
623 depends on DM_VIDEO && OF_CONTROL
626 This enables support for Arm Ltd Mali Display Processors from
627 the DP500, DP550 and DP650 family.
629 config VIDEO_SANDBOX_SDL
630 bool "Enable sandbox video console using SDL"
633 When using sandbox you can enable an emulated LCD display which
634 appears as an SDL (Simple DirectMedia Layer) window. This is a
635 console device and can display stdout output. Within U-Boot is is
636 a normal bitmap display and can display images as well as text.
638 source "drivers/video/stm32/Kconfig"
641 bool "Enable LCD support on Tegra20"
642 depends on OF_CONTROL
644 Tegra20 supports video output to an attached LCD panel as well as
645 other options such as HDMI. Only the LCD is supported in U-Boot.
646 This option enables this support which can be used on devices which
647 have an LCD display connected.
649 config VIDEO_TEGRA124
650 bool "Enable video support on Tegra124"
653 Tegra124 supports many video output options including eDP and
654 HDMI. At present only eDP is supported by U-Boot. This option
655 enables this support which can be used on devices which
656 have an eDP display connected.
658 source "drivers/video/bridge/Kconfig"
660 source "drivers/video/imx/Kconfig"
663 bool "Enable video support on Nexell SoC"
664 depends on ARCH_S5P6818 || ARCH_S5P4418
666 Nexell SoC supports many video output options including eDP and
667 HDMI. This option enables this support which can be used on devices
668 which have an eDP display connected.
671 bool "Enable video support for Seps525"
674 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
675 Currently driver is supporting only SPI interface.
677 source "drivers/video/nexell/Kconfig"
680 bool "Enable legacy video support"
683 Define this for video support, without using driver model. Some
684 drivers use this because they are not yet converted to driver
685 model. Video drivers typically provide a colour text console and
689 bool "Enable colour frame buffer console"
690 depends on VIDEO || ARCH_OMAP2PLUS
693 Enables the colour frame buffer driver. This supports colour
694 output on a bitmap display from an in-memory frame buffer.
695 Several colour devices are supported along with various options to
696 adjust the supported features. The driver is implemented in
699 The following defines are needed (cf. smiLynxEM, i8042)
700 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
702 VIDEO_HW_RECTFILL graphic chip supports
703 rectangle fill (cf. smiLynxEM)
704 VIDEO_HW_BITBLT graphic chip supports
705 bit-blit (cf. smiLynxEM)
706 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
707 VIDEO_VISIBLE_ROWS visible pixel rows
708 VIDEO_PIXEL_SIZE bytes per pixel
709 VIDEO_DATA_FORMAT graphic data format
710 (0-5, cf. cfb_console.c)
711 VIDEO_FB_ADRS framebuffer address
712 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
713 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
714 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
715 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
716 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
717 for logo. Requires CONFIG_VIDEO_LOGO
718 CONFIG_CONSOLE_EXTRA_INFO
719 additional board info beside
721 CONFIG_HIDE_LOGO_VERSION
722 do not display bootloader
725 When CONFIG_CFB_CONSOLE is defined, the video console is the
726 default console. The serial console can be forced by setting the
727 environment 'console=serial'.
729 config CFB_CONSOLE_ANSI
730 bool "Support ANSI escape sequences"
731 depends on CFB_CONSOLE
733 This allows the colour buffer frame buffer driver to support
734 a limited number of ANSI escape sequences (cursor control,
735 erase functions and limited graphics rendition control). Normal
736 output from U-Boot will pass through this filter.
738 config VGA_AS_SINGLE_DEVICE
739 bool "Set the video as an output-only device"
740 depends on CFB_CONSOLE
743 If enable the framebuffer device will be initialized as an
744 output-only device. The Keyboard driver will not be set up. This
745 may be used if you have no keyboard device, or more than one
746 (USB Keyboard, AT Keyboard).
748 config VIDEO_SW_CURSOR
749 bool "Enable a software cursor"
750 depends on CFB_CONSOLE
751 default y if CFB_CONSOLE
753 This draws a cursor after the last character. No blinking is
754 provided. This makes it possible to see the current cursor
755 position when entering text on the console. It is recommended to
758 config CONSOLE_EXTRA_INFO
759 bool "Display additional board information"
760 depends on CFB_CONSOLE
762 Display additional board information strings that normally go to
763 the serial port. When this option is enabled, a board-specific
764 function video_get_info_str() is called to get the string for
765 each line of the display. The function should return the string,
766 which can be empty if there is nothing to display for that line.
768 config CONSOLE_SCROLL_LINES
769 int "Number of lines to scroll the console by"
770 depends on CFB_CONSOLE || DM_VIDEO || LCD
773 When the console need to be scrolled, this is the number of
774 lines to scroll by. It defaults to 1. Increasing this makes the
775 console jump but can help speed up operation when scrolling
778 config SYS_CONSOLE_BG_COL
779 hex "Background colour"
780 depends on CFB_CONSOLE
783 Defines the background colour for the console. The value is from
784 0x00 to 0xff and the meaning depends on the graphics card.
785 Typically, 0x00 means black and 0xff means white. Do not set
786 the background and foreground to the same colour or you will see
789 config SYS_CONSOLE_FG_COL
790 hex "Foreground colour"
791 depends on CFB_CONSOLE
794 Defines the foreground colour for the console. The value is from
795 0x00 to 0xff and the meaning depends on the graphics card.
796 Typically, 0x00 means black and 0xff means white. Do not set
797 the background and foreground to the same colour or you will see
801 bool "Enable legacy LCD support"
803 Define this to enable LCD support (for output to LCD display).
804 You will also need to select an LCD driver using an additional
805 CONFIG option. See the README for details. Drives which have been
806 converted to driver model will instead used CONFIG_DM_VIDEO.
811 Enables the common driver code for the Designware HDMI TX
812 block found in SoCs from various vendors.
813 As this does not provide any functionality by itself (but
814 rather requires a SoC-specific glue driver to call it), it
815 can not be enabled from the configuration menu.
817 config VIDEO_DSI_HOST_SANDBOX
818 bool "Enable sandbox for dsi host"
820 select VIDEO_MIPI_DSI
822 Enable support for sandbox dsi host device used for testing
824 Display Serial Interface (DSI) defines a serial bus and
825 a communication protocol between the host and the device
828 config VIDEO_DW_MIPI_DSI
830 select VIDEO_MIPI_DSI
832 Enables the common driver code for the Synopsis Designware
833 MIPI DSI block found in SoCs from various vendors.
834 As this does not provide any functionality by itself (but
835 rather requires a SoC-specific glue driver to call it), it
836 can not be enabled from the configuration menu.
839 bool "Simple display driver for preconfigured display"
841 Enables a simple generic display driver which utilizes the
842 simple-framebuffer devicetree bindings.
844 This driver assumes that the display hardware has been initialized
845 before u-boot starts, and u-boot will simply render to the pre-
846 allocated frame buffer surface.
848 config VIDEO_DT_SIMPLEFB
849 bool "Enable SimpleFB support for passing framebuffer to OS"
851 Enables the code to pass the framebuffer to the kernel as a
852 simple framebuffer in the device tree.
853 The video output is initialized by U-Boot, and kept by the
856 config VIDEO_MCDE_SIMPLE
857 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
860 Enables a simple display driver for ST-Ericsson MCDE
861 (Multichannel Display Engine), which reads the configuration from
864 This driver assumes that the display hardware has been initialized
865 before u-boot starts, and u-boot will simply render to the pre-
866 allocated frame buffer surface.
869 bool "Enable OSD support"
873 This supports drivers that provide a OSD (on-screen display), which
874 is a (usually text-oriented) graphics buffer to show information on
878 bool "Enable sandbox OSD"
881 Enable support for sandbox OSD device used for testing purposes.
884 bool "Enable IHS video out driver"
887 Enable support for the gdsys Integrated Hardware Systems (IHS) video
888 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
889 textual overlays of the display outputs.
892 bool "Show a splash-screen image"
894 If this option is set, the environment is checked for a variable
895 "splashimage". If found, the usual display of logo, copyright and
896 system information on the LCD is suppressed and the BMP image at the
897 address specified in "splashimage" is loaded instead. The console is
898 redirected to the "nulldev", too. This allows for a "silent" boot
899 where a splash screen is loaded very quickly after power-on.
901 The splash_screen_prepare() function is a weak function defined in
902 common/splash.c. It is called as part of the splash screen display
903 sequence. It gives the board an opportunity to prepare the splash
904 image data before it is processed and sent to the frame buffer by
905 U-Boot. Define your own version to use this feature.
907 config SPLASHIMAGE_GUARD
908 bool "Support unaligned BMP images"
909 depends on SPLASH_SCREEN
911 If this option is set, then U-Boot will prevent the environment
912 variable "splashimage" from being set to a problematic address
913 (see doc/README.displaying-bmps).
915 This option is useful for targets where, due to alignment
916 restrictions, an improperly aligned BMP image will cause a data
917 abort. If you think you will not have problems with unaligned
918 accesses (for example because your toolchain prevents them)
919 there is no need to set this option.
921 config SPLASH_SCREEN_ALIGN
922 bool "Allow positioning the splash image anywhere on the display"
923 depends on SPLASH_SCREEN || CMD_BMP
925 If this option is set the splash image can be freely positioned
926 on the screen. Environment variable "splashpos" specifies the
927 position as "x,y". If a positive number is given it is used as
928 number of pixel from left/top. If a negative number is given it
929 is used as number of pixel from right/bottom. You can also
930 specify 'm' for centering the image.
934 => image at center of screen
936 setenv splashpos 30,20
937 => image at x = 30 and y = 20
939 setenv splashpos -10,m
940 => vertically centered image
941 at x = dspWidth - bmpWidth - 9
944 bool "Control the source of the splash image"
945 depends on SPLASH_SCREEN
947 Use the splash_source.c library. This library provides facilities to
948 declare board specific splash image locations, routines for loading
949 splash image from supported locations, and a way of controlling the
950 selected splash location using the "splashsource" environment
953 This CONFIG works as follows:
955 - If splashsource is set to a supported location name as defined by
956 board code, use that splash location.
957 - If splashsource is undefined, use the first splash location as
959 - If splashsource is set to an unsupported value, do not load a splash
962 A splash source location can describe either storage with raw data, a
963 storage formatted with a file system or a FIT image. In case of a
964 filesystem, the splash screen data is loaded as a file. The name of
965 the splash screen file can be controlled with the environment variable
968 To enable loading the splash image from a FIT image, CONFIG_FIT must
969 be enabled. The FIT image has to start at the 'offset' field address
970 in the selected splash location. The name of splash image within the
971 FIT shall be specified by the environment variable "splashfile".
973 In case the environment variable "splashfile" is not defined the
974 default name 'splash.bmp' will be used.
976 config VIDEO_BMP_GZIP
977 bool "Gzip compressed BMP image support"
978 depends on CMD_BMP || SPLASH_SCREEN
980 If this option is set, additionally to standard BMP
981 images, gzipped BMP images can be displayed via the
982 splashscreen support or the bmp command.
984 config VIDEO_BMP_RLE8
985 bool "Run length encoded BMP image (RLE8) support"
986 depends on DM_VIDEO || CFB_CONSOLE
988 If this option is set, the 8-bit RLE compressed BMP images
992 bool "16-bit-per-pixel BMP image support"
993 depends on DM_VIDEO || LCD
995 Support display of bitmaps file with 16-bit-per-pixel
998 bool "24-bit-per-pixel BMP image support"
999 depends on DM_VIDEO || LCD
1001 Support display of bitmaps file with 24-bit-per-pixel.
1004 bool "32-bit-per-pixel BMP image support"
1005 depends on DM_VIDEO || LCD
1007 Support display of bitmaps file with 32-bit-per-pixel.
1010 bool "Enable VCXK video controller driver support"
1013 This enables VCXK driver which can be used with VC2K, VC4K
1014 and VC8K devices on various boards from BuS Elektronik GmbH.