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 "Show the U-Boot logo on the display"
21 This enables showing the U-Boot logo on the display when a video
22 device is probed. It appears at the top right. The logo itself is at
23 tools/logos/u-boot_logo.bmp and looks best when the display has a
27 bool "Enable panel backlight uclass support"
31 This provides backlight uclass driver that enables basic panel
34 config VIDEO_PCI_DEFAULT_FB_SIZE
35 hex "Default framebuffer size to use if no drivers request it"
37 default 0x1000000 if X86 && PCI
38 default 0 if !(X86 && PCI)
40 Generally, video drivers request the amount of memory they need for
41 the frame buffer when they are bound, by setting the size field in
42 struct video_uc_plat. That memory is then reserved for use after
43 relocation. But PCI drivers cannot be bound before relocation unless
44 they are mentioned in the devicetree.
46 With this value set appropriately, it is possible for PCI video
47 devices to have a framebuffer allocated by U-Boot.
49 Note: the framebuffer needs to be large enough to store all pixels at
50 maximum resolution. For example, at 1920 x 1200 with 32 bits per
51 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
54 bool "Enable copying the frame buffer to a hardware copy"
57 On some machines (e.g. x86), reading from the frame buffer is very
58 slow because it is uncached. To improve performance, this feature
59 allows the frame buffer to be kept in cached memory (allocated by
60 U-Boot) and then copied to the hardware frame-buffer as needed.
62 To use this, your video driver must set @copy_base in
66 bool "Generic PWM based Backlight Driver"
67 depends on BACKLIGHT && DM_PWM
70 If you have a LCD backlight adjustable by PWM, say Y to enable
72 This driver can be use with "simple-panel" and
73 it understands the standard device tree
74 (leds/backlight/pwm-backlight.txt)
77 bool "Generic GPIO based Backlight Driver"
80 If you have a LCD backlight adjustable by GPIO, say Y to enable
82 This driver can be used with "simple-panel" and
83 it understands the standard device tree
84 (leds/backlight/gpio-backlight.txt)
87 bool "Enable vidconsole commands lcdputs and setcurs"
91 Enabling this will provide 'setcurs' and 'lcdputs' commands which
92 support cursor positioning and drawing strings on video framebuffer.
95 bool "Support 8-bit-per-pixel displays"
99 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
100 Enabling this will include code to support this display. Without
101 this option, such displays will not be supported and console output
105 bool "Support 16-bit-per-pixel displays"
109 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
110 Enabling this will include code to support this display. Without
111 this option, such displays will not be supported and console output
115 bool "Support 32-bit-per-pixel displays"
119 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
120 Enabling this will include code to support this display. Without
121 this option, such displays will not be supported and console output
125 bool "Support ANSI escape sequences in video console"
129 Enable ANSI escape sequence decoding for a more fully functional
132 config VIDEO_MIPI_DSI
133 bool "Support MIPI DSI interface"
136 Support MIPI DSI interface for driving a MIPI compatible device.
137 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
138 serial interface between a host processor and a display module.
140 config CONSOLE_NORMAL
141 bool "Support a simple text console"
143 default y if DM_VIDEO
145 Support drawing text on the frame buffer console so that it can be
146 used as a console. Rotation is not supported by this driver (see
147 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
150 config CONSOLE_ROTATION
151 bool "Support rotated displays"
154 Sometimes, for example if the display is mounted in portrait
155 mode or even if it's mounted landscape but rotated by 180degree,
156 we need to rotate our content of the display relative to the
157 framebuffer, so that user can read the messages which are
158 printed out. Enable this option to include a text driver which can
159 support this. The rotation is set by the 'rot' parameter in
160 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
161 degrees, 3=270 degrees.
163 config CONSOLE_TRUETYPE
164 bool "Support a console that uses TrueType fonts"
167 TrueTrype fonts can provide outline-drawing capability rather than
168 needing to provide a bitmap for each font and size that is needed.
169 With this option you can adjust the text size and use a variety of
170 fonts. Note that this is noticeably slower than with normal console.
172 config DM_PANEL_HX8238D
173 bool "Enable Himax HX-8238D LCD driver"
176 Support for HX-8238D LCD Panel
177 The HX8238-D is a single chip controller and driver LSI that
178 integrates the power circuit.
179 It can drive a maximum 960x240 dot graphics on a-TFT panel
180 displays in 16M colors with dithering.
182 config CONSOLE_TRUETYPE_SIZE
183 int "TrueType font size"
184 depends on CONSOLE_TRUETYPE
187 This sets the font size for the console. The size is measured in
188 pixels and is the nominal height of a character. Note that fonts
189 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
190 However that measurement depends on the size of your display and
191 there is no standard display density. At present there is not a
192 method to select the display's physical size, which would allow
193 U-Boot to calculate the correct font size.
195 config SYS_WHITE_ON_BLACK
196 bool "Display console as white on a black background"
197 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
199 Normally the display is black on a white background, Enable this
200 option to invert this, i.e. white on a black background. This can be
201 better in low-light situations or to reduce eye strain in some
205 bool "Skip framebuffer clear"
207 If firmware (whatever loads u-boot) has already put a splash image
208 on screen, you might want to preserve it until whatever u-boot
209 loads takes over the screen. This, for example, can be used to
210 keep splash image on screen until grub graphical boot menu starts.
213 bool "Enable panel uclass support"
217 This provides panel uclass driver that enables basic panel support.
220 bool "Enable simple panel support"
221 depends on PANEL && BACKLIGHT && DM_GPIO
224 This turns on a simple panel driver that enables a compatible
227 source "drivers/video/fonts/Kconfig"
229 config VIDCONSOLE_AS_LCD
230 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
233 This is a work-around for boards which have 'lcd' or 'vga' in their
234 stdout environment variable, but have moved to use driver model for
235 video. In this case the console will no-longer work. While it is
236 possible to update the environment, the breakage may be confusing for
237 users. This option will be removed around the end of 2020.
239 config VIDCONSOLE_AS_NAME
240 string "Use 'vidconsole' when string defined here is seen in stdout"
241 depends on VIDCONSOLE_AS_LCD
242 default "lcd" if LCD || TEGRA_COMMON
243 default "vga" if !LCD
245 This is a work-around for boards which have 'lcd' or 'vga' in their
246 stdout environment variable, but have moved to use driver model for
247 video. In this case the console will no-longer work. While it is
248 possible to update the environment, the breakage may be confusing for
249 users. This option will be removed around the end of 2020.
251 config VIDEO_COREBOOT
252 bool "Enable coreboot framebuffer driver support"
255 Turn on this option to enable a framebuffer driver when U-Boot is
256 loaded by coreboot where the graphics device is configured by
257 coreboot already. This can in principle be used with any platform
258 that coreboot supports.
261 bool "Enable EFI framebuffer driver support"
262 depends on EFI_STUB || EFI_APP
264 Turn on this option to enable a framebuffeer driver when U-Boot is
265 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
266 the graphics device is configured by the EFI BIOS already. This can
267 in principle be used with any platform that has an EFI BIOS.
270 bool "Enable VESA video driver support"
272 Turn on this option to enable a very simple driver which uses vesa
273 to discover the video mode and then provides a frame buffer for use
274 by U-Boot. This can in principle be used with any platform that
275 supports PCI and video cards that support VESA BIOS Extension (VBE).
277 config FRAMEBUFFER_SET_VESA_MODE
278 bool "Set framebuffer graphics resolution"
279 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
281 Set VESA/native framebuffer mode (needed for bootsplash and graphical
285 prompt "framebuffer graphics resolution"
286 default FRAMEBUFFER_VESA_MODE_118
287 depends on FRAMEBUFFER_SET_VESA_MODE
289 This option sets the resolution used for the U-Boot framebuffer (and
292 config FRAMEBUFFER_VESA_MODE_100
293 bool "640x400 256-color"
295 config FRAMEBUFFER_VESA_MODE_101
296 bool "640x480 256-color"
298 config FRAMEBUFFER_VESA_MODE_102
299 bool "800x600 16-color"
301 config FRAMEBUFFER_VESA_MODE_103
302 bool "800x600 256-color"
304 config FRAMEBUFFER_VESA_MODE_104
305 bool "1024x768 16-color"
307 config FRAMEBUFFER_VESA_MODE_105
308 bool "1024x768 256-color"
310 config FRAMEBUFFER_VESA_MODE_106
311 bool "1280x1024 16-color"
313 config FRAMEBUFFER_VESA_MODE_107
314 bool "1280x1024 256-color"
316 config FRAMEBUFFER_VESA_MODE_108
319 config FRAMEBUFFER_VESA_MODE_109
322 config FRAMEBUFFER_VESA_MODE_10A
325 config FRAMEBUFFER_VESA_MODE_10B
328 config FRAMEBUFFER_VESA_MODE_10C
331 config FRAMEBUFFER_VESA_MODE_10D
332 bool "320x200 32k-color (1:5:5:5)"
334 config FRAMEBUFFER_VESA_MODE_10E
335 bool "320x200 64k-color (5:6:5)"
337 config FRAMEBUFFER_VESA_MODE_10F
338 bool "320x200 16.8M-color (8:8:8)"
340 config FRAMEBUFFER_VESA_MODE_110
341 bool "640x480 32k-color (1:5:5:5)"
343 config FRAMEBUFFER_VESA_MODE_111
344 bool "640x480 64k-color (5:6:5)"
346 config FRAMEBUFFER_VESA_MODE_112
347 bool "640x480 16.8M-color (8:8:8)"
349 config FRAMEBUFFER_VESA_MODE_113
350 bool "800x600 32k-color (1:5:5:5)"
352 config FRAMEBUFFER_VESA_MODE_114
353 bool "800x600 64k-color (5:6:5)"
355 config FRAMEBUFFER_VESA_MODE_115
356 bool "800x600 16.8M-color (8:8:8)"
358 config FRAMEBUFFER_VESA_MODE_116
359 bool "1024x768 32k-color (1:5:5:5)"
361 config FRAMEBUFFER_VESA_MODE_117
362 bool "1024x768 64k-color (5:6:5)"
364 config FRAMEBUFFER_VESA_MODE_118
365 bool "1024x768 16.8M-color (8:8:8)"
367 config FRAMEBUFFER_VESA_MODE_119
368 bool "1280x1024 32k-color (1:5:5:5)"
370 config FRAMEBUFFER_VESA_MODE_11A
371 bool "1280x1024 64k-color (5:6:5)"
373 config FRAMEBUFFER_VESA_MODE_11B
374 bool "1280x1024 16.8M-color (8:8:8)"
376 config FRAMEBUFFER_VESA_MODE_USER
377 bool "Manually select VESA mode"
381 # Map the config names to an integer (KB).
382 config FRAMEBUFFER_VESA_MODE
383 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
385 default 0x100 if FRAMEBUFFER_VESA_MODE_100
386 default 0x101 if FRAMEBUFFER_VESA_MODE_101
387 default 0x102 if FRAMEBUFFER_VESA_MODE_102
388 default 0x103 if FRAMEBUFFER_VESA_MODE_103
389 default 0x104 if FRAMEBUFFER_VESA_MODE_104
390 default 0x105 if FRAMEBUFFER_VESA_MODE_105
391 default 0x106 if FRAMEBUFFER_VESA_MODE_106
392 default 0x107 if FRAMEBUFFER_VESA_MODE_107
393 default 0x108 if FRAMEBUFFER_VESA_MODE_108
394 default 0x109 if FRAMEBUFFER_VESA_MODE_109
395 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
396 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
397 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
398 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
399 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
400 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
401 default 0x110 if FRAMEBUFFER_VESA_MODE_110
402 default 0x111 if FRAMEBUFFER_VESA_MODE_111
403 default 0x112 if FRAMEBUFFER_VESA_MODE_112
404 default 0x113 if FRAMEBUFFER_VESA_MODE_113
405 default 0x114 if FRAMEBUFFER_VESA_MODE_114
406 default 0x115 if FRAMEBUFFER_VESA_MODE_115
407 default 0x116 if FRAMEBUFFER_VESA_MODE_116
408 default 0x117 if FRAMEBUFFER_VESA_MODE_117
409 default 0x118 if FRAMEBUFFER_VESA_MODE_118
410 default 0x119 if FRAMEBUFFER_VESA_MODE_119
411 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
412 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
413 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
415 config VIDEO_LCD_ANX9804
416 bool "ANX9804 bridge chip"
418 Support for the ANX9804 bridge chip, which can take pixel data coming
419 from a parallel LCD interface and translate it on the fy into a DP
420 interface for driving eDP TFT displays. It uses I2C for configuration.
422 config VIDEO_LCD_ORISETECH_OTM8009A
423 bool "OTM8009A DSI LCD panel support"
425 select VIDEO_MIPI_DSI
427 Say Y here if you want to enable support for Orise Technology
428 otm8009a 480x800 dsi 2dl panel.
430 config VIDEO_LCD_RAYDIUM_RM68200
431 bool "RM68200 DSI LCD panel support"
433 select VIDEO_MIPI_DSI
435 Say Y here if you want to enable support for Raydium RM68200
436 720x1280 DSI video mode panel.
438 config VIDEO_LCD_SSD2828
439 bool "SSD2828 bridge chip"
441 Support for the SSD2828 bridge chip, which can take pixel data coming
442 from a parallel LCD interface and translate it on the fly into MIPI DSI
443 interface for driving a MIPI compatible LCD panel. It uses SPI for
446 config VIDEO_LCD_SSD2828_TX_CLK
447 int "SSD2828 TX_CLK frequency (in MHz)"
448 depends on VIDEO_LCD_SSD2828
451 The frequency of the crystal, which is clocking SSD2828. It may be
452 anything in the 8MHz-30MHz range and the exact value should be
453 retrieved from the board schematics. Or in the case of Allwinner
454 hardware, it can be usually found as 'lcd_xtal_freq' variable in
455 FEX files. It can be also set to 0 for selecting PCLK from the
456 parallel LCD interface instead of TX_CLK as the PLL clock source.
458 config VIDEO_LCD_SSD2828_RESET
459 string "RESET pin of SSD2828"
460 depends on VIDEO_LCD_SSD2828
463 The reset pin of SSD2828 chip. This takes a string in the format
464 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
466 config VIDEO_LCD_TDO_TL070WSH30
467 bool "TDO TL070WSH30 DSI LCD panel support"
469 select VIDEO_MIPI_DSI
471 Say Y here if you want to enable support for TDO TL070WSH30
472 1024x600 DSI video mode panel.
474 config VIDEO_LCD_HITACHI_TX18D42VM
475 bool "Hitachi tx18d42vm LVDS LCD panel support"
477 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
478 lcd controller which needs to be initialized over SPI, once that is
479 done they work like a regular LVDS panel.
481 config VIDEO_LCD_SPI_CS
482 string "SPI CS pin for LCD related config job"
483 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
486 This is one of the SPI communication pins, involved in setting up a
487 working LCD configuration. The exact role of SPI may differ for
488 different hardware setups. The option takes a string in the format
489 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
491 config VIDEO_LCD_SPI_SCLK
492 string "SPI SCLK pin for LCD related config job"
493 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
496 This is one of the SPI communication pins, involved in setting up a
497 working LCD configuration. The exact role of SPI may differ for
498 different hardware setups. The option takes a string in the format
499 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
501 config VIDEO_LCD_SPI_MOSI
502 string "SPI MOSI pin for LCD related config job"
503 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
506 This is one of the SPI communication pins, involved in setting up a
507 working LCD configuration. The exact role of SPI may differ for
508 different hardware setups. The option takes a string in the format
509 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
511 config VIDEO_LCD_SPI_MISO
512 string "SPI MISO pin for LCD related config job (optional)"
513 depends on VIDEO_LCD_SSD2828
516 This is one of the SPI communication pins, involved in setting up a
517 working LCD configuration. The exact role of SPI may differ for
518 different hardware setups. If wired up, this pin may provide additional
519 useful functionality. Such as bi-directional communication with the
520 hardware and LCD panel id retrieval (if the panel can report it). The
521 option takes a string in the format understood by 'sunxi_name_to_gpio'
522 function, e.g. PH1 for pin 1 of port H.
524 source "drivers/video/meson/Kconfig"
527 bool "Armada XP LCD controller"
529 Support for the LCD controller integrated in the Marvell
533 bool "Enable OMAP3+ DSS Support"
534 depends on ARCH_OMAP2PLUS
536 This enables the Display subsystem (DSS) on OMAP3+ boards.
539 bool "Enable EDID library"
541 This enables library for accessing EDID data from an LCD panel.
544 bool "Enable Display support"
548 This supports drivers that provide a display, such as eDP (Embedded
549 DisplayPort) and HDMI (High Definition Multimedia Interface).
550 The devices provide a simple interface to start up the display,
551 read display information and enable it.
554 bool "Enable NXP TDA19988 support"
557 This enables support for the NXP TDA19988 HDMI encoder. This encoder
558 will convert RGB data streams into HDMI-encoded signals.
561 bool "Enable ATMEL video support using HLCDC"
563 HLCDC supports video output to an attached LCD panel.
565 source "drivers/video/ti/Kconfig"
567 config LOGICORE_DP_TX
568 bool "Enable Logicore DP TX driver"
571 Enable the driver for the transmitter part of the Xilinx LogiCORE
572 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
573 video interface as defined by VESA DisplayPort v1.2.
575 Note that this is a pure transmitter device, and has no display
576 capabilities by itself.
578 config VIDEO_BROADWELL_IGD
579 bool "Enable Intel Broadwell integrated graphics device"
582 This enables support for integrated graphics on Intel broadwell
583 devices. Initialisation is mostly performed by a VGA boot ROM, with
584 some setup handled by U-Boot itself. The graphics adaptor works as
585 a VESA device and supports LCD panels, eDP and LVDS outputs.
586 Configuration of most aspects of device operation is performed using
587 a special tool which configures the VGA ROM, but the graphics
588 resolution can be selected in U-Boot.
590 config VIDEO_IVYBRIDGE_IGD
591 bool "Enable Intel Ivybridge integration graphics support"
594 This enables support for integrated graphics on Intel ivybridge
595 devices. Initialisation is mostly performed by a VGA boot ROM, with
596 some setup handled by U-Boot itself. The graphics adaptor works as
597 a VESA device and supports LCD panels, eDP and LVDS outputs.
598 Configuration of most aspects of device operation is performed using
599 a special tool which configures the VGA ROM, but the graphics
600 resolution can be selected in U-Boot.
602 config VIDEO_FSL_DCU_FB
603 bool "Enable Freescale Display Control Unit"
604 depends on VIDEO || DM_VIDEO
606 This enables support for Freescale Display Control Unit (DCU4)
607 module found on Freescale Vybrid and QorIQ family of SoCs.
609 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
610 int "Freescale DCU framebuffer size"
611 depends on VIDEO_FSL_DCU_FB
614 Set maximum framebuffer size to be used for Freescale Display
615 Controller Unit (DCU4).
617 source "drivers/video/rockchip/Kconfig"
619 config VIDEO_ARM_MALIDP
620 bool "Enable Arm Mali Display Processor support"
621 depends on DM_VIDEO && OF_CONTROL
624 This enables support for Arm Ltd Mali Display Processors from
625 the DP500, DP550 and DP650 family.
627 config VIDEO_SANDBOX_SDL
628 bool "Enable sandbox video console using SDL"
631 When using sandbox you can enable an emulated LCD display which
632 appears as an SDL (Simple DirectMedia Layer) window. This is a
633 console device and can display stdout output. Within U-Boot is is
634 a normal bitmap display and can display images as well as text.
636 source "drivers/video/stm32/Kconfig"
639 bool "Enable LCD support on Tegra20"
640 depends on OF_CONTROL
642 Tegra20 supports video output to an attached LCD panel as well as
643 other options such as HDMI. Only the LCD is supported in U-Boot.
644 This option enables this support which can be used on devices which
645 have an LCD display connected.
647 config VIDEO_TEGRA124
648 bool "Enable video support on Tegra124"
651 Tegra124 supports many video output options including eDP and
652 HDMI. At present only eDP is supported by U-Boot. This option
653 enables this support which can be used on devices which
654 have an eDP display connected.
656 source "drivers/video/bridge/Kconfig"
658 source "drivers/video/imx/Kconfig"
661 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
664 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
667 bool "Enable video support on Nexell SoC"
668 depends on ARCH_S5P6818 || ARCH_S5P4418
670 Nexell SoC supports many video output options including eDP and
671 HDMI. This option enables this support which can be used on devices
672 which have an eDP display connected.
675 bool "Enable video support for Seps525"
678 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
679 Currently driver is supporting only SPI interface.
681 source "drivers/video/nexell/Kconfig"
684 bool "Enable legacy video support"
687 Define this for video support, without using driver model. Some
688 drivers use this because they are not yet converted to driver
689 model. Video drivers typically provide a colour text console and
693 bool "Enable colour frame buffer console"
694 depends on VIDEO || ARCH_OMAP2PLUS
697 Enables the colour frame buffer driver. This supports colour
698 output on a bitmap display from an in-memory frame buffer.
699 Several colour devices are supported along with various options to
700 adjust the supported features. The driver is implemented in
703 The following defines are needed (cf. smiLynxEM, i8042)
704 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
706 VIDEO_HW_RECTFILL graphic chip supports
707 rectangle fill (cf. smiLynxEM)
708 VIDEO_HW_BITBLT graphic chip supports
709 bit-blit (cf. smiLynxEM)
710 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
711 VIDEO_VISIBLE_ROWS visible pixel rows
712 VIDEO_PIXEL_SIZE bytes per pixel
713 VIDEO_DATA_FORMAT graphic data format
714 (0-5, cf. cfb_console.c)
715 VIDEO_FB_ADRS framebuffer address
716 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
717 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
718 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
719 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
720 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
721 for logo. Requires CONFIG_VIDEO_LOGO
722 CONFIG_CONSOLE_EXTRA_INFO
723 additional board info beside
725 CONFIG_HIDE_LOGO_VERSION
726 do not display bootloader
729 When CONFIG_CFB_CONSOLE is defined, the video console is the
730 default console. The serial console can be forced by setting the
731 environment 'console=serial'.
733 config CFB_CONSOLE_ANSI
734 bool "Support ANSI escape sequences"
735 depends on CFB_CONSOLE
737 This allows the colour buffer frame buffer driver to support
738 a limited number of ANSI escape sequences (cursor control,
739 erase functions and limited graphics rendition control). Normal
740 output from U-Boot will pass through this filter.
742 config VGA_AS_SINGLE_DEVICE
743 bool "Set the video as an output-only device"
744 depends on CFB_CONSOLE
747 If enable the framebuffer device will be initialized as an
748 output-only device. The Keyboard driver will not be set up. This
749 may be used if you have no keyboard device, or more than one
750 (USB Keyboard, AT Keyboard).
752 config VIDEO_SW_CURSOR
753 bool "Enable a software cursor"
754 depends on CFB_CONSOLE
755 default y if CFB_CONSOLE
757 This draws a cursor after the last character. No blinking is
758 provided. This makes it possible to see the current cursor
759 position when entering text on the console. It is recommended to
762 config CONSOLE_EXTRA_INFO
763 bool "Display additional board information"
764 depends on CFB_CONSOLE
766 Display additional board information strings that normally go to
767 the serial port. When this option is enabled, a board-specific
768 function video_get_info_str() is called to get the string for
769 each line of the display. The function should return the string,
770 which can be empty if there is nothing to display for that line.
772 config CONSOLE_SCROLL_LINES
773 int "Number of lines to scroll the console by"
774 depends on CFB_CONSOLE || DM_VIDEO || LCD
777 When the console need to be scrolled, this is the number of
778 lines to scroll by. It defaults to 1. Increasing this makes the
779 console jump but can help speed up operation when scrolling
782 config SYS_CONSOLE_BG_COL
783 hex "Background colour"
784 depends on CFB_CONSOLE
787 Defines the background colour for the console. The value is from
788 0x00 to 0xff and the meaning depends on the graphics card.
789 Typically, 0x00 means black and 0xff means white. Do not set
790 the background and foreground to the same colour or you will see
793 config SYS_CONSOLE_FG_COL
794 hex "Foreground colour"
795 depends on CFB_CONSOLE
798 Defines the foreground colour for the console. The value is from
799 0x00 to 0xff and the meaning depends on the graphics card.
800 Typically, 0x00 means black and 0xff means white. Do not set
801 the background and foreground to the same colour or you will see
805 bool "Enable legacy LCD support"
807 Define this to enable LCD support (for output to LCD display).
808 You will also need to select an LCD driver using an additional
809 CONFIG option. See the README for details. Drives which have been
810 converted to driver model will instead used CONFIG_DM_VIDEO.
815 Enables the common driver code for the Designware HDMI TX
816 block found in SoCs from various vendors.
817 As this does not provide any functionality by itself (but
818 rather requires a SoC-specific glue driver to call it), it
819 can not be enabled from the configuration menu.
821 config VIDEO_DSI_HOST_SANDBOX
822 bool "Enable sandbox for dsi host"
824 select VIDEO_MIPI_DSI
826 Enable support for sandbox dsi host device used for testing
828 Display Serial Interface (DSI) defines a serial bus and
829 a communication protocol between the host and the device
832 config VIDEO_DW_MIPI_DSI
834 select VIDEO_MIPI_DSI
836 Enables the common driver code for the Synopsis Designware
837 MIPI DSI block found in SoCs from various vendors.
838 As this does not provide any functionality by itself (but
839 rather requires a SoC-specific glue driver to call it), it
840 can not be enabled from the configuration menu.
843 bool "Simple display driver for preconfigured display"
845 Enables a simple generic display driver which utilizes the
846 simple-framebuffer devicetree bindings.
848 This driver assumes that the display hardware has been initialized
849 before u-boot starts, and u-boot will simply render to the pre-
850 allocated frame buffer surface.
852 config VIDEO_DT_SIMPLEFB
853 bool "Enable SimpleFB support for passing framebuffer to OS"
855 Enables the code to pass the framebuffer to the kernel as a
856 simple framebuffer in the device tree.
857 The video output is initialized by U-Boot, and kept by the
860 config VIDEO_MCDE_SIMPLE
861 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
864 Enables a simple display driver for ST-Ericsson MCDE
865 (Multichannel Display Engine), which reads the configuration from
868 This driver assumes that the display hardware has been initialized
869 before u-boot starts, and u-boot will simply render to the pre-
870 allocated frame buffer surface.
873 bool "Enable OSD support"
876 This supports drivers that provide a OSD (on-screen display), which
877 is a (usually text-oriented) graphics buffer to show information on
881 bool "Enable sandbox OSD"
884 Enable support for sandbox OSD device used for testing purposes.
887 bool "Enable IHS video out driver"
890 Enable support for the gdsys Integrated Hardware Systems (IHS) video
891 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
892 textual overlays of the display outputs.
895 bool "Show a splash-screen image"
897 If this option is set, the environment is checked for a variable
898 "splashimage". If found, the usual display of logo, copyright and
899 system information on the LCD is suppressed and the BMP image at the
900 address specified in "splashimage" is loaded instead. The console is
901 redirected to the "nulldev", too. This allows for a "silent" boot
902 where a splash screen is loaded very quickly after power-on.
904 The splash_screen_prepare() function is a weak function defined in
905 common/splash.c. It is called as part of the splash screen display
906 sequence. It gives the board an opportunity to prepare the splash
907 image data before it is processed and sent to the frame buffer by
908 U-Boot. Define your own version to use this feature.
910 config SPLASHIMAGE_GUARD
911 bool "Support unaligned BMP images"
912 depends on SPLASH_SCREEN
914 If this option is set, then U-Boot will prevent the environment
915 variable "splashimage" from being set to a problematic address
916 (see doc/README.displaying-bmps).
918 This option is useful for targets where, due to alignment
919 restrictions, an improperly aligned BMP image will cause a data
920 abort. If you think you will not have problems with unaligned
921 accesses (for example because your toolchain prevents them)
922 there is no need to set this option.
924 config SPLASH_SCREEN_ALIGN
925 bool "Allow positioning the splash image anywhere on the display"
926 depends on SPLASH_SCREEN || CMD_BMP
928 If this option is set the splash image can be freely positioned
929 on the screen. Environment variable "splashpos" specifies the
930 position as "x,y". If a positive number is given it is used as
931 number of pixel from left/top. If a negative number is given it
932 is used as number of pixel from right/bottom. You can also
933 specify 'm' for centering the image.
937 => image at center of screen
939 setenv splashpos 30,20
940 => image at x = 30 and y = 20
942 setenv splashpos -10,m
943 => vertically centered image
944 at x = dspWidth - bmpWidth - 9
947 bool "Control the source of the splash image"
948 depends on SPLASH_SCREEN
950 Use the splash_source.c library. This library provides facilities to
951 declare board specific splash image locations, routines for loading
952 splash image from supported locations, and a way of controlling the
953 selected splash location using the "splashsource" environment
956 This CONFIG works as follows:
958 - If splashsource is set to a supported location name as defined by
959 board code, use that splash location.
960 - If splashsource is undefined, use the first splash location as
962 - If splashsource is set to an unsupported value, do not load a splash
965 A splash source location can describe either storage with raw data, a
966 storage formatted with a file system or a FIT image. In case of a
967 filesystem, the splash screen data is loaded as a file. The name of
968 the splash screen file can be controlled with the environment variable
971 To enable loading the splash image from a FIT image, CONFIG_FIT must
972 be enabled. The FIT image has to start at the 'offset' field address
973 in the selected splash location. The name of splash image within the
974 FIT shall be specified by the environment variable "splashfile".
976 In case the environment variable "splashfile" is not defined the
977 default name 'splash.bmp' will be used.
979 config VIDEO_BMP_GZIP
980 bool "Gzip compressed BMP image support"
981 depends on CMD_BMP || SPLASH_SCREEN
983 If this option is set, additionally to standard BMP
984 images, gzipped BMP images can be displayed via the
985 splashscreen support or the bmp command.
987 config VIDEO_BMP_RLE8
988 bool "Run length encoded BMP image (RLE8) support"
989 depends on DM_VIDEO || CFB_CONSOLE
991 If this option is set, the 8-bit RLE compressed BMP images
995 bool "16-bit-per-pixel BMP image support"
996 depends on DM_VIDEO || LCD
998 Support display of bitmaps file with 16-bit-per-pixel
1001 bool "24-bit-per-pixel BMP image support"
1002 depends on DM_VIDEO || LCD
1004 Support display of bitmaps file with 24-bit-per-pixel.
1007 bool "32-bit-per-pixel BMP image support"
1008 depends on DM_VIDEO || LCD
1010 Support display of bitmaps file with 32-bit-per-pixel.
1013 bool "Enable VCXK video controller driver support"
1015 This enables VCXK driver which can be used with VC2K, VC4K
1016 and VC8K devices on various boards from BuS Elektronik GmbH.