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"
263 Turn on this option to enable a very simple driver which uses vesa
264 to discover the video mode and then provides a frame buffer for use
265 by U-Boot. This can in principle be used with any platform that
266 supports PCI and video cards that support VESA BIOS Extension (VBE).
268 config FRAMEBUFFER_SET_VESA_MODE
269 bool "Set framebuffer graphics resolution"
270 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
272 Set VESA/native framebuffer mode (needed for bootsplash and graphical
276 prompt "framebuffer graphics resolution"
277 default FRAMEBUFFER_VESA_MODE_118
278 depends on FRAMEBUFFER_SET_VESA_MODE
280 This option sets the resolution used for the U-Boot framebuffer (and
283 config FRAMEBUFFER_VESA_MODE_100
284 bool "640x400 256-color"
286 config FRAMEBUFFER_VESA_MODE_101
287 bool "640x480 256-color"
289 config FRAMEBUFFER_VESA_MODE_102
290 bool "800x600 16-color"
292 config FRAMEBUFFER_VESA_MODE_103
293 bool "800x600 256-color"
295 config FRAMEBUFFER_VESA_MODE_104
296 bool "1024x768 16-color"
298 config FRAMEBUFFER_VESA_MODE_105
299 bool "1024x768 256-color"
301 config FRAMEBUFFER_VESA_MODE_106
302 bool "1280x1024 16-color"
304 config FRAMEBUFFER_VESA_MODE_107
305 bool "1280x1024 256-color"
307 config FRAMEBUFFER_VESA_MODE_108
310 config FRAMEBUFFER_VESA_MODE_109
313 config FRAMEBUFFER_VESA_MODE_10A
316 config FRAMEBUFFER_VESA_MODE_10B
319 config FRAMEBUFFER_VESA_MODE_10C
322 config FRAMEBUFFER_VESA_MODE_10D
323 bool "320x200 32k-color (1:5:5:5)"
325 config FRAMEBUFFER_VESA_MODE_10E
326 bool "320x200 64k-color (5:6:5)"
328 config FRAMEBUFFER_VESA_MODE_10F
329 bool "320x200 16.8M-color (8:8:8)"
331 config FRAMEBUFFER_VESA_MODE_110
332 bool "640x480 32k-color (1:5:5:5)"
334 config FRAMEBUFFER_VESA_MODE_111
335 bool "640x480 64k-color (5:6:5)"
337 config FRAMEBUFFER_VESA_MODE_112
338 bool "640x480 16.8M-color (8:8:8)"
340 config FRAMEBUFFER_VESA_MODE_113
341 bool "800x600 32k-color (1:5:5:5)"
343 config FRAMEBUFFER_VESA_MODE_114
344 bool "800x600 64k-color (5:6:5)"
346 config FRAMEBUFFER_VESA_MODE_115
347 bool "800x600 16.8M-color (8:8:8)"
349 config FRAMEBUFFER_VESA_MODE_116
350 bool "1024x768 32k-color (1:5:5:5)"
352 config FRAMEBUFFER_VESA_MODE_117
353 bool "1024x768 64k-color (5:6:5)"
355 config FRAMEBUFFER_VESA_MODE_118
356 bool "1024x768 16.8M-color (8:8:8)"
358 config FRAMEBUFFER_VESA_MODE_119
359 bool "1280x1024 32k-color (1:5:5:5)"
361 config FRAMEBUFFER_VESA_MODE_11A
362 bool "1280x1024 64k-color (5:6:5)"
364 config FRAMEBUFFER_VESA_MODE_11B
365 bool "1280x1024 16.8M-color (8:8:8)"
367 config FRAMEBUFFER_VESA_MODE_USER
368 bool "Manually select VESA mode"
372 # Map the config names to an integer (KB).
373 config FRAMEBUFFER_VESA_MODE
374 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
376 default 0x100 if FRAMEBUFFER_VESA_MODE_100
377 default 0x101 if FRAMEBUFFER_VESA_MODE_101
378 default 0x102 if FRAMEBUFFER_VESA_MODE_102
379 default 0x103 if FRAMEBUFFER_VESA_MODE_103
380 default 0x104 if FRAMEBUFFER_VESA_MODE_104
381 default 0x105 if FRAMEBUFFER_VESA_MODE_105
382 default 0x106 if FRAMEBUFFER_VESA_MODE_106
383 default 0x107 if FRAMEBUFFER_VESA_MODE_107
384 default 0x108 if FRAMEBUFFER_VESA_MODE_108
385 default 0x109 if FRAMEBUFFER_VESA_MODE_109
386 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
387 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
388 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
389 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
390 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
391 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
392 default 0x110 if FRAMEBUFFER_VESA_MODE_110
393 default 0x111 if FRAMEBUFFER_VESA_MODE_111
394 default 0x112 if FRAMEBUFFER_VESA_MODE_112
395 default 0x113 if FRAMEBUFFER_VESA_MODE_113
396 default 0x114 if FRAMEBUFFER_VESA_MODE_114
397 default 0x115 if FRAMEBUFFER_VESA_MODE_115
398 default 0x116 if FRAMEBUFFER_VESA_MODE_116
399 default 0x117 if FRAMEBUFFER_VESA_MODE_117
400 default 0x118 if FRAMEBUFFER_VESA_MODE_118
401 default 0x119 if FRAMEBUFFER_VESA_MODE_119
402 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
403 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
404 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
406 config VIDEO_LCD_ANX9804
407 bool "ANX9804 bridge chip"
409 Support for the ANX9804 bridge chip, which can take pixel data coming
410 from a parallel LCD interface and translate it on the fy into a DP
411 interface for driving eDP TFT displays. It uses I2C for configuration.
413 config VIDEO_LCD_ORISETECH_OTM8009A
414 bool "OTM8009A DSI LCD panel support"
416 select VIDEO_MIPI_DSI
418 Say Y here if you want to enable support for Orise Technology
419 otm8009a 480x800 dsi 2dl panel.
421 config VIDEO_LCD_RAYDIUM_RM68200
422 bool "RM68200 DSI LCD panel support"
424 select VIDEO_MIPI_DSI
426 Say Y here if you want to enable support for Raydium RM68200
427 720x1280 DSI video mode panel.
429 config VIDEO_LCD_SSD2828
430 bool "SSD2828 bridge chip"
432 Support for the SSD2828 bridge chip, which can take pixel data coming
433 from a parallel LCD interface and translate it on the fly into MIPI DSI
434 interface for driving a MIPI compatible LCD panel. It uses SPI for
437 config VIDEO_LCD_SSD2828_TX_CLK
438 int "SSD2828 TX_CLK frequency (in MHz)"
439 depends on VIDEO_LCD_SSD2828
442 The frequency of the crystal, which is clocking SSD2828. It may be
443 anything in the 8MHz-30MHz range and the exact value should be
444 retrieved from the board schematics. Or in the case of Allwinner
445 hardware, it can be usually found as 'lcd_xtal_freq' variable in
446 FEX files. It can be also set to 0 for selecting PCLK from the
447 parallel LCD interface instead of TX_CLK as the PLL clock source.
449 config VIDEO_LCD_SSD2828_RESET
450 string "RESET pin of SSD2828"
451 depends on VIDEO_LCD_SSD2828
454 The reset pin of SSD2828 chip. This takes a string in the format
455 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
457 config VIDEO_LCD_TDO_TL070WSH30
458 bool "TDO TL070WSH30 DSI LCD panel support"
460 select VIDEO_MIPI_DSI
462 Say Y here if you want to enable support for TDO TL070WSH30
463 1024x600 DSI video mode panel.
465 config VIDEO_LCD_HITACHI_TX18D42VM
466 bool "Hitachi tx18d42vm LVDS LCD panel support"
468 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
469 lcd controller which needs to be initialized over SPI, once that is
470 done they work like a regular LVDS panel.
472 config VIDEO_LCD_SPI_CS
473 string "SPI CS pin for LCD related config job"
474 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
477 This is one of the SPI communication pins, involved in setting up a
478 working LCD configuration. The exact role of SPI may differ for
479 different hardware setups. The option takes a string in the format
480 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
482 config VIDEO_LCD_SPI_SCLK
483 string "SPI SCLK pin for LCD related config job"
484 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
487 This is one of the SPI communication pins, involved in setting up a
488 working LCD configuration. The exact role of SPI may differ for
489 different hardware setups. The option takes a string in the format
490 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
492 config VIDEO_LCD_SPI_MOSI
493 string "SPI MOSI pin for LCD related config job"
494 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
497 This is one of the SPI communication pins, involved in setting up a
498 working LCD configuration. The exact role of SPI may differ for
499 different hardware setups. The option takes a string in the format
500 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
502 config VIDEO_LCD_SPI_MISO
503 string "SPI MISO pin for LCD related config job (optional)"
504 depends on VIDEO_LCD_SSD2828
507 This is one of the SPI communication pins, involved in setting up a
508 working LCD configuration. The exact role of SPI may differ for
509 different hardware setups. If wired up, this pin may provide additional
510 useful functionality. Such as bi-directional communication with the
511 hardware and LCD panel id retrieval (if the panel can report it). The
512 option takes a string in the format understood by 'name_to_gpio'
513 function, e.g. PH1 for pin 1 of port H.
515 source "drivers/video/meson/Kconfig"
518 bool "Armada XP LCD controller"
520 Support for the LCD controller integrated in the Marvell
524 bool "Enable OMAP3+ DSS Support"
525 depends on ARCH_OMAP2PLUS
527 This enables the Display subsystem (DSS) on OMAP3+ boards.
530 bool "Enable EDID library"
532 This enables library for accessing EDID data from an LCD panel.
535 bool "Enable Display support"
539 This supports drivers that provide a display, such as eDP (Embedded
540 DisplayPort) and HDMI (High Definition Multimedia Interface).
541 The devices provide a simple interface to start up the display,
542 read display information and enable it.
545 bool "Enable NXP TDA19988 support"
548 This enables support for the NXP TDA19988 HDMI encoder. This encoder
549 will convert RGB data streams into HDMI-encoded signals.
552 bool "Enable ATMEL video support using HLCDC"
554 HLCDC supports video output to an attached LCD panel.
556 source "drivers/video/ti/Kconfig"
558 config LOGICORE_DP_TX
559 bool "Enable Logicore DP TX driver"
562 Enable the driver for the transmitter part of the Xilinx LogiCORE
563 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
564 video interface as defined by VESA DisplayPort v1.2.
566 Note that this is a pure transmitter device, and has no display
567 capabilities by itself.
569 config VIDEO_BROADWELL_IGD
570 bool "Enable Intel Broadwell integrated graphics device"
573 This enables support for integrated graphics on Intel broadwell
574 devices. Initialisation is mostly performed by a VGA boot ROM, with
575 some setup handled by U-Boot itself. The graphics adaptor works as
576 a VESA device and supports LCD panels, eDP and LVDS outputs.
577 Configuration of most aspects of device operation is performed using
578 a special tool which configures the VGA ROM, but the graphics
579 resolution can be selected in U-Boot.
581 config VIDEO_IVYBRIDGE_IGD
582 bool "Enable Intel Ivybridge integration graphics support"
585 This enables support for integrated graphics on Intel ivybridge
586 devices. Initialisation is mostly performed by a VGA boot ROM, with
587 some setup handled by U-Boot itself. The graphics adaptor works as
588 a VESA device and supports LCD panels, eDP and LVDS outputs.
589 Configuration of most aspects of device operation is performed using
590 a special tool which configures the VGA ROM, but the graphics
591 resolution can be selected in U-Boot.
593 config VIDEO_FSL_DCU_FB
594 bool "Enable Freescale Display Control Unit"
595 depends on VIDEO || DM_VIDEO
597 This enables support for Freescale Display Control Unit (DCU4)
598 module found on Freescale Vybrid and QorIQ family of SoCs.
600 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
601 int "Freescale DCU framebuffer size"
602 depends on VIDEO_FSL_DCU_FB
605 Set maximum framebuffer size to be used for Freescale Display
606 Controller Unit (DCU4).
608 source "drivers/video/rockchip/Kconfig"
610 config VIDEO_ARM_MALIDP
611 bool "Enable Arm Mali Display Processor support"
612 depends on DM_VIDEO && OF_CONTROL
615 This enables support for Arm Ltd Mali Display Processors from
616 the DP500, DP550 and DP650 family.
618 config VIDEO_SANDBOX_SDL
619 bool "Enable sandbox video console using SDL"
622 When using sandbox you can enable an emulated LCD display which
623 appears as an SDL (Simple DirectMedia Layer) window. This is a
624 console device and can display stdout output. Within U-Boot is is
625 a normal bitmap display and can display images as well as text.
627 source "drivers/video/stm32/Kconfig"
630 bool "Enable LCD support on Tegra20"
631 depends on OF_CONTROL
633 Tegra20 supports video output to an attached LCD panel as well as
634 other options such as HDMI. Only the LCD is supported in U-Boot.
635 This option enables this support which can be used on devices which
636 have an LCD display connected.
638 config VIDEO_TEGRA124
639 bool "Enable video support on Tegra124"
642 Tegra124 supports many video output options including eDP and
643 HDMI. At present only eDP is supported by U-Boot. This option
644 enables this support which can be used on devices which
645 have an eDP display connected.
647 source "drivers/video/bridge/Kconfig"
649 source "drivers/video/imx/Kconfig"
652 bool "Enable video support on Nexell SoC"
653 depends on ARCH_S5P6818 || ARCH_S5P4418
655 Nexell SoC supports many video output options including eDP and
656 HDMI. This option enables this support which can be used on devices
657 which have an eDP display connected.
660 bool "Enable video support for Seps525"
663 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
664 Currently driver is supporting only SPI interface.
666 source "drivers/video/nexell/Kconfig"
669 bool "Enable legacy video support"
672 Define this for video support, without using driver model. Some
673 drivers use this because they are not yet converted to driver
674 model. Video drivers typically provide a colour text console and
678 bool "Enable colour frame buffer console"
679 depends on VIDEO || ARCH_OMAP2PLUS
682 Enables the colour frame buffer driver. This supports colour
683 output on a bitmap display from an in-memory frame buffer.
684 Several colour devices are supported along with various options to
685 adjust the supported features. The driver is implemented in
688 The following defines are needed (cf. smiLynxEM, i8042)
689 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
691 VIDEO_HW_RECTFILL graphic chip supports
692 rectangle fill (cf. smiLynxEM)
693 VIDEO_HW_BITBLT graphic chip supports
694 bit-blit (cf. smiLynxEM)
695 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
696 VIDEO_VISIBLE_ROWS visible pixel rows
697 VIDEO_PIXEL_SIZE bytes per pixel
698 VIDEO_DATA_FORMAT graphic data format
699 (0-5, cf. cfb_console.c)
700 VIDEO_FB_ADRS framebuffer address
701 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
702 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
703 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
704 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
705 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
706 for logo. Requires CONFIG_VIDEO_LOGO
707 CONFIG_CONSOLE_EXTRA_INFO
708 additional board info beside
710 CONFIG_HIDE_LOGO_VERSION
711 do not display bootloader
714 When CONFIG_CFB_CONSOLE is defined, the video console is the
715 default console. The serial console can be forced by setting the
716 environment 'console=serial'.
718 config CFB_CONSOLE_ANSI
719 bool "Support ANSI escape sequences"
720 depends on CFB_CONSOLE
722 This allows the colour buffer frame buffer driver to support
723 a limited number of ANSI escape sequences (cursor control,
724 erase functions and limited graphics rendition control). Normal
725 output from U-Boot will pass through this filter.
727 config VGA_AS_SINGLE_DEVICE
728 bool "Set the video as an output-only device"
729 depends on CFB_CONSOLE
732 If enable the framebuffer device will be initialized as an
733 output-only device. The Keyboard driver will not be set up. This
734 may be used if you have no keyboard device, or more than one
735 (USB Keyboard, AT Keyboard).
737 config VIDEO_SW_CURSOR
738 bool "Enable a software cursor"
739 depends on CFB_CONSOLE
740 default y if CFB_CONSOLE
742 This draws a cursor after the last character. No blinking is
743 provided. This makes it possible to see the current cursor
744 position when entering text on the console. It is recommended to
747 config CONSOLE_EXTRA_INFO
748 bool "Display additional board information"
749 depends on CFB_CONSOLE
751 Display additional board information strings that normally go to
752 the serial port. When this option is enabled, a board-specific
753 function video_get_info_str() is called to get the string for
754 each line of the display. The function should return the string,
755 which can be empty if there is nothing to display for that line.
757 config CONSOLE_SCROLL_LINES
758 int "Number of lines to scroll the console by"
759 depends on CFB_CONSOLE || DM_VIDEO || LCD
762 When the console need to be scrolled, this is the number of
763 lines to scroll by. It defaults to 1. Increasing this makes the
764 console jump but can help speed up operation when scrolling
767 config SYS_CONSOLE_BG_COL
768 hex "Background colour"
769 depends on CFB_CONSOLE
772 Defines the background colour for the console. The value is from
773 0x00 to 0xff and the meaning depends on the graphics card.
774 Typically, 0x00 means black and 0xff means white. Do not set
775 the background and foreground to the same colour or you will see
778 config SYS_CONSOLE_FG_COL
779 hex "Foreground colour"
780 depends on CFB_CONSOLE
783 Defines the foreground 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
790 bool "Enable legacy LCD support"
792 Define this to enable LCD support (for output to LCD display).
793 You will also need to select an LCD driver using an additional
794 CONFIG option. See the README for details. Drives which have been
795 converted to driver model will instead used CONFIG_DM_VIDEO.
800 Enables the common driver code for the Designware HDMI TX
801 block found in SoCs from various vendors.
802 As this does not provide any functionality by itself (but
803 rather requires a SoC-specific glue driver to call it), it
804 can not be enabled from the configuration menu.
806 config VIDEO_DSI_HOST_SANDBOX
807 bool "Enable sandbox for dsi host"
809 select VIDEO_MIPI_DSI
811 Enable support for sandbox dsi host device used for testing
813 Display Serial Interface (DSI) defines a serial bus and
814 a communication protocol between the host and the device
817 config VIDEO_DW_MIPI_DSI
819 select VIDEO_MIPI_DSI
821 Enables the common driver code for the Synopsis Designware
822 MIPI DSI block found in SoCs from various vendors.
823 As this does not provide any functionality by itself (but
824 rather requires a SoC-specific glue driver to call it), it
825 can not be enabled from the configuration menu.
828 bool "Simple display driver for preconfigured display"
830 Enables a simple generic display driver which utilizes the
831 simple-framebuffer devicetree bindings.
833 This driver assumes that the display hardware has been initialized
834 before u-boot starts, and u-boot will simply render to the pre-
835 allocated frame buffer surface.
837 config VIDEO_DT_SIMPLEFB
838 bool "Enable SimpleFB support for passing framebuffer to OS"
840 Enables the code to pass the framebuffer to the kernel as a
841 simple framebuffer in the device tree.
842 The video output is initialized by U-Boot, and kept by the
845 config VIDEO_MCDE_SIMPLE
846 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
849 Enables a simple display driver for ST-Ericsson MCDE
850 (Multichannel Display Engine), which reads the configuration from
853 This driver assumes that the display hardware has been initialized
854 before u-boot starts, and u-boot will simply render to the pre-
855 allocated frame buffer surface.
858 bool "Enable OSD support"
861 This supports drivers that provide a OSD (on-screen display), which
862 is a (usually text-oriented) graphics buffer to show information on
866 bool "Enable sandbox OSD"
869 Enable support for sandbox OSD device used for testing purposes.
872 bool "Enable IHS video out driver"
875 Enable support for the gdsys Integrated Hardware Systems (IHS) video
876 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
877 textual overlays of the display outputs.
880 bool "Show a splash-screen image"
882 If this option is set, the environment is checked for a variable
883 "splashimage". If found, the usual display of logo, copyright and
884 system information on the LCD is suppressed and the BMP image at the
885 address specified in "splashimage" is loaded instead. The console is
886 redirected to the "nulldev", too. This allows for a "silent" boot
887 where a splash screen is loaded very quickly after power-on.
889 The splash_screen_prepare() function is a weak function defined in
890 common/splash.c. It is called as part of the splash screen display
891 sequence. It gives the board an opportunity to prepare the splash
892 image data before it is processed and sent to the frame buffer by
893 U-Boot. Define your own version to use this feature.
895 config SPLASHIMAGE_GUARD
896 bool "Support unaligned BMP images"
897 depends on SPLASH_SCREEN
899 If this option is set, then U-Boot will prevent the environment
900 variable "splashimage" from being set to a problematic address
901 (see doc/README.displaying-bmps).
903 This option is useful for targets where, due to alignment
904 restrictions, an improperly aligned BMP image will cause a data
905 abort. If you think you will not have problems with unaligned
906 accesses (for example because your toolchain prevents them)
907 there is no need to set this option.
909 config SPLASH_SCREEN_ALIGN
910 bool "Allow positioning the splash image anywhere on the display"
911 depends on SPLASH_SCREEN || CMD_BMP
913 If this option is set the splash image can be freely positioned
914 on the screen. Environment variable "splashpos" specifies the
915 position as "x,y". If a positive number is given it is used as
916 number of pixel from left/top. If a negative number is given it
917 is used as number of pixel from right/bottom. You can also
918 specify 'm' for centering the image.
922 => image at center of screen
924 setenv splashpos 30,20
925 => image at x = 30 and y = 20
927 setenv splashpos -10,m
928 => vertically centered image
929 at x = dspWidth - bmpWidth - 9
932 bool "Control the source of the splash image"
933 depends on SPLASH_SCREEN
935 Use the splash_source.c library. This library provides facilities to
936 declare board specific splash image locations, routines for loading
937 splash image from supported locations, and a way of controlling the
938 selected splash location using the "splashsource" environment
941 This CONFIG works as follows:
943 - If splashsource is set to a supported location name as defined by
944 board code, use that splash location.
945 - If splashsource is undefined, use the first splash location as
947 - If splashsource is set to an unsupported value, do not load a splash
950 A splash source location can describe either storage with raw data, a
951 storage formatted with a file system or a FIT image. In case of a
952 filesystem, the splash screen data is loaded as a file. The name of
953 the splash screen file can be controlled with the environment variable
956 To enable loading the splash image from a FIT image, CONFIG_FIT must
957 be enabled. The FIT image has to start at the 'offset' field address
958 in the selected splash location. The name of splash image within the
959 FIT shall be specified by the environment variable "splashfile".
961 In case the environment variable "splashfile" is not defined the
962 default name 'splash.bmp' will be used.
964 config VIDEO_BMP_GZIP
965 bool "Gzip compressed BMP image support"
966 depends on CMD_BMP || SPLASH_SCREEN
968 If this option is set, additionally to standard BMP
969 images, gzipped BMP images can be displayed via the
970 splashscreen support or the bmp command.
972 config VIDEO_BMP_RLE8
973 bool "Run length encoded BMP image (RLE8) support"
974 depends on DM_VIDEO || CFB_CONSOLE
976 If this option is set, the 8-bit RLE compressed BMP images
980 bool "16-bit-per-pixel BMP image support"
981 depends on DM_VIDEO || LCD
983 Support display of bitmaps file with 16-bit-per-pixel
986 bool "24-bit-per-pixel BMP image support"
987 depends on DM_VIDEO || LCD
989 Support display of bitmaps file with 24-bit-per-pixel.
992 bool "32-bit-per-pixel BMP image support"
993 depends on DM_VIDEO || LCD
995 Support display of bitmaps file with 32-bit-per-pixel.
998 bool "Enable VCXK video controller driver support"
1000 This enables VCXK driver which can be used with VC2K, VC4K
1001 and VC8K devices on various boards from BuS Elektronik GmbH.