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
20 bool "4 x 6 font size"
22 Font for video console driver, 4 x 6 pixels.
23 Provides character bitmap data in header file.
24 When selecting multiple fonts, you may want to enable CMD_SELECT_FONT too.
26 config VIDEO_FONT_8X16
27 bool "8 x 16 font size"
30 Font for video console driver, 8 x 16 pixels
31 Provides character bitmap data in header file.
32 When selecting multiple fonts, you may want to enable CMD_SELECT_FONT too.
35 bool "Show the U-Boot logo on the display"
36 default y if !SPLASH_SCREEN
39 This enables showing the U-Boot logo on the display when a video
40 device is probed. It appears at the top right. The logo itself is at
41 tools/logos/u-boot_logo.bmp and looks best when the display has a
45 bool "Enable panel backlight uclass support"
48 This provides backlight uclass driver that enables basic panel
51 config VIDEO_PCI_DEFAULT_FB_SIZE
52 hex "Default framebuffer size to use if no drivers request it"
53 default 0x1000000 if X86 && PCI
54 default 0 if !(X86 && PCI)
56 Generally, video drivers request the amount of memory they need for
57 the frame buffer when they are bound, by setting the size field in
58 struct video_uc_plat. That memory is then reserved for use after
59 relocation. But PCI drivers cannot be bound before relocation unless
60 they are mentioned in the devicetree.
62 With this value set appropriately, it is possible for PCI video
63 devices to have a framebuffer allocated by U-Boot.
65 Note: the framebuffer needs to be large enough to store all pixels at
66 maximum resolution. For example, at 1920 x 1200 with 32 bits per
67 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
70 bool "Enable copying the frame buffer to a hardware copy"
72 On some machines (e.g. x86), reading from the frame buffer is very
73 slow because it is uncached. To improve performance, this feature
74 allows the frame buffer to be kept in cached memory (allocated by
75 U-Boot) and then copied to the hardware frame-buffer as needed.
77 To use this, your video driver must set @copy_base in
81 bool "Generic PWM based Backlight Driver"
82 depends on BACKLIGHT && DM_PWM
85 If you have a LCD backlight adjustable by PWM, say Y to enable
87 This driver can be use with "simple-panel" and
88 it understands the standard device tree
89 (leds/backlight/pwm-backlight.txt)
92 bool "Generic GPIO based Backlight Driver"
95 If you have a LCD backlight adjustable by GPIO, say Y to enable
97 This driver can be used with "simple-panel" and
98 it understands the standard device tree
99 (leds/backlight/gpio-backlight.txt)
102 bool "Support 8-bit-per-pixel displays"
105 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
106 Enabling this will include code to support this display. Without
107 this option, such displays will not be supported and console output
111 bool "Support 16-bit-per-pixel displays"
114 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
115 Enabling this will include code to support this display. Without
116 this option, such displays will not be supported and console output
120 bool "Support 32-bit-per-pixel displays"
123 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
124 Enabling this will include code to support this display. Without
125 this option, such displays will not be supported and console output
129 bool "Support ANSI escape sequences in video console"
130 default y if EFI_LOADER
132 Enable ANSI escape sequence decoding for a more fully functional
133 console. Functionality includes changing the text colour and moving
134 the cursor. These date from the 1970s and are still widely used today
135 to control a text terminal. U-Boot implements these by decoding the
136 sequences and performing the appropriate operation.
138 config VIDEO_MIPI_DSI
139 bool "Support MIPI DSI interface"
141 Support MIPI DSI interface for driving a MIPI compatible device.
142 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
143 serial interface between a host processor and a display module.
145 config CONSOLE_NORMAL
146 bool "Support a simple text console"
149 Support drawing text on the frame buffer console so that it can be
150 used as a console. Rotation is not supported by this driver (see
151 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
154 config CONSOLE_ROTATION
155 bool "Support rotated displays"
157 Sometimes, for example if the display is mounted in portrait
158 mode or even if it's mounted landscape but rotated by 180degree,
159 we need to rotate our content of the display relative to the
160 framebuffer, so that user can read the messages which are
161 printed out. Enable this option to include a text driver which can
162 support this. The rotation is set by the 'rot' parameter in
163 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
164 degrees, 3=270 degrees.
166 config CONSOLE_TRUETYPE
167 bool "Support a console that uses TrueType fonts"
169 TrueTrype fonts can provide outline-drawing capability rather than
170 needing to provide a bitmap for each font and size that is needed.
171 With this option you can adjust the text size and use a variety of
172 fonts. Note that this is noticeably slower than with normal console.
174 config CONSOLE_TRUETYPE_SIZE
175 int "TrueType font size"
176 depends on CONSOLE_TRUETYPE
179 This sets the font size for the console. The size is measured in
180 pixels and is the nominal height of a character. Note that fonts
181 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
182 However that measurement depends on the size of your display and
183 there is no standard display density. At present there is not a
184 method to select the display's physical size, which would allow
185 U-Boot to calculate the correct font size.
187 config CONSOLE_TRUETYPE_MAX_METRICS
188 int "TrueType maximum number of font / size combinations"
189 depends on CONSOLE_TRUETYPE
193 This sets the number of font / size combinations which can be used by
194 the console. For simple console use a single font is enough. When
195 boot menus are in use, this may need to be increased.
197 Note that a separate entry is needed for each font size, even if the
198 font itself is the same. This is because the entry caches various
199 font metrics which are expensive to regenerate each time the font
202 config SYS_WHITE_ON_BLACK
203 bool "Display console as white on a black background"
204 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
206 Normally the display is black on a white background, Enable this
207 option to invert this, i.e. white on a black background. This can be
208 better in low-light situations or to reduce eye strain in some
212 bool "Skip framebuffer clear"
214 If firmware (whatever loads u-boot) has already put a splash image
215 on screen, you might want to preserve it until whatever u-boot
216 loads takes over the screen. This, for example, can be used to
217 keep splash image on screen until grub graphical boot menu starts.
220 bool "Enable panel uclass support"
223 This provides panel uclass driver that enables basic panel support.
226 bool "Enable simple panel support"
227 depends on PANEL && BACKLIGHT && DM_GPIO
230 This turns on a simple panel driver that enables a compatible
234 bool "Enable Himax HX-8238D LCD driver"
237 Support for HX-8238D LCD Panel
238 The HX8238-D is a single chip controller and driver LSI that
239 integrates the power circuit.
240 It can drive a maximum 960x240 dot graphics on a-TFT panel
241 displays in 16M colors with dithering.
243 source "drivers/video/fonts/Kconfig"
245 config VIDCONSOLE_AS_LCD
246 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
248 This is a work-around for boards which have 'lcd' or 'vga' in their
249 stdout environment variable, but have moved to use driver model for
250 video. In this case the console will no-longer work. While it is
251 possible to update the environment, the breakage may be confusing for
252 users. This option will be removed around the end of 2020.
254 config VIDCONSOLE_AS_NAME
255 string "Use 'vidconsole' when string defined here is seen in stdout"
256 depends on VIDCONSOLE_AS_LCD
257 default "lcd" if LCD || TEGRA_COMMON
258 default "vga" if !LCD
260 This is a work-around for boards which have 'lcd' or 'vga' in their
261 stdout environment variable, but have moved to use driver model for
262 video. In this case the console will no-longer work. While it is
263 possible to update the environment, the breakage may be confusing for
264 users. This option will be removed around the end of 2020.
266 config VIDEO_COREBOOT
267 bool "Enable coreboot framebuffer driver support"
270 Turn on this option to enable a framebuffer driver when U-Boot is
271 loaded by coreboot where the graphics device is configured by
272 coreboot already. This can in principle be used with any platform
273 that coreboot supports.
276 bool "Enable EFI framebuffer driver support"
277 depends on EFI_STUB || EFI_APP
279 Turn on this option to enable a framebuffeer driver when U-Boot is
280 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
281 the graphics device is configured by the EFI BIOS already. This can
282 in principle be used with any platform that has an EFI BIOS.
285 bool "Enable VESA video driver support"
287 Turn on this option to enable a very simple driver which uses vesa
288 to discover the video mode and then provides a frame buffer for use
289 by U-Boot. This can in principle be used with any platform that
290 supports PCI and video cards that support VESA BIOS Extension (VBE).
292 config FRAMEBUFFER_SET_VESA_MODE
293 bool "Set framebuffer graphics resolution"
294 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
296 Set VESA/native framebuffer mode (needed for bootsplash and graphical
300 prompt "framebuffer graphics resolution"
301 default FRAMEBUFFER_VESA_MODE_118
302 depends on FRAMEBUFFER_SET_VESA_MODE
304 This option sets the resolution used for the U-Boot framebuffer (and
307 config FRAMEBUFFER_VESA_MODE_100
308 bool "640x400 256-color"
310 config FRAMEBUFFER_VESA_MODE_101
311 bool "640x480 256-color"
313 config FRAMEBUFFER_VESA_MODE_102
314 bool "800x600 16-color"
316 config FRAMEBUFFER_VESA_MODE_103
317 bool "800x600 256-color"
319 config FRAMEBUFFER_VESA_MODE_104
320 bool "1024x768 16-color"
322 config FRAMEBUFFER_VESA_MODE_105
323 bool "1024x768 256-color"
325 config FRAMEBUFFER_VESA_MODE_106
326 bool "1280x1024 16-color"
328 config FRAMEBUFFER_VESA_MODE_107
329 bool "1280x1024 256-color"
331 config FRAMEBUFFER_VESA_MODE_108
334 config FRAMEBUFFER_VESA_MODE_109
337 config FRAMEBUFFER_VESA_MODE_10A
340 config FRAMEBUFFER_VESA_MODE_10B
343 config FRAMEBUFFER_VESA_MODE_10C
346 config FRAMEBUFFER_VESA_MODE_10D
347 bool "320x200 32k-color (1:5:5:5)"
349 config FRAMEBUFFER_VESA_MODE_10E
350 bool "320x200 64k-color (5:6:5)"
352 config FRAMEBUFFER_VESA_MODE_10F
353 bool "320x200 16.8M-color (8:8:8)"
355 config FRAMEBUFFER_VESA_MODE_110
356 bool "640x480 32k-color (1:5:5:5)"
358 config FRAMEBUFFER_VESA_MODE_111
359 bool "640x480 64k-color (5:6:5)"
361 config FRAMEBUFFER_VESA_MODE_112
362 bool "640x480 16.8M-color (8:8:8)"
364 config FRAMEBUFFER_VESA_MODE_113
365 bool "800x600 32k-color (1:5:5:5)"
367 config FRAMEBUFFER_VESA_MODE_114
368 bool "800x600 64k-color (5:6:5)"
370 config FRAMEBUFFER_VESA_MODE_115
371 bool "800x600 16.8M-color (8:8:8)"
373 config FRAMEBUFFER_VESA_MODE_116
374 bool "1024x768 32k-color (1:5:5:5)"
376 config FRAMEBUFFER_VESA_MODE_117
377 bool "1024x768 64k-color (5:6:5)"
379 config FRAMEBUFFER_VESA_MODE_118
380 bool "1024x768 16.8M-color (8:8:8)"
382 config FRAMEBUFFER_VESA_MODE_119
383 bool "1280x1024 32k-color (1:5:5:5)"
385 config FRAMEBUFFER_VESA_MODE_11A
386 bool "1280x1024 64k-color (5:6:5)"
388 config FRAMEBUFFER_VESA_MODE_11B
389 bool "1280x1024 16.8M-color (8:8:8)"
391 config FRAMEBUFFER_VESA_MODE_USER
392 bool "Manually select VESA mode"
396 # Map the config names to an integer (KB).
397 config FRAMEBUFFER_VESA_MODE
398 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
400 default 0x100 if FRAMEBUFFER_VESA_MODE_100
401 default 0x101 if FRAMEBUFFER_VESA_MODE_101
402 default 0x102 if FRAMEBUFFER_VESA_MODE_102
403 default 0x103 if FRAMEBUFFER_VESA_MODE_103
404 default 0x104 if FRAMEBUFFER_VESA_MODE_104
405 default 0x105 if FRAMEBUFFER_VESA_MODE_105
406 default 0x106 if FRAMEBUFFER_VESA_MODE_106
407 default 0x107 if FRAMEBUFFER_VESA_MODE_107
408 default 0x108 if FRAMEBUFFER_VESA_MODE_108
409 default 0x109 if FRAMEBUFFER_VESA_MODE_109
410 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
411 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
412 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
413 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
414 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
415 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
416 default 0x110 if FRAMEBUFFER_VESA_MODE_110
417 default 0x111 if FRAMEBUFFER_VESA_MODE_111
418 default 0x112 if FRAMEBUFFER_VESA_MODE_112
419 default 0x113 if FRAMEBUFFER_VESA_MODE_113
420 default 0x114 if FRAMEBUFFER_VESA_MODE_114
421 default 0x115 if FRAMEBUFFER_VESA_MODE_115
422 default 0x116 if FRAMEBUFFER_VESA_MODE_116
423 default 0x117 if FRAMEBUFFER_VESA_MODE_117
424 default 0x118 if FRAMEBUFFER_VESA_MODE_118
425 default 0x119 if FRAMEBUFFER_VESA_MODE_119
426 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
427 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
428 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
430 config VIDEO_LCD_ANX9804
431 bool "ANX9804 bridge chip"
433 Support for the ANX9804 bridge chip, which can take pixel data coming
434 from a parallel LCD interface and translate it on the fy into a DP
435 interface for driving eDP TFT displays. It uses I2C for configuration.
438 bool "Atmel LCD panel support"
441 config ATMEL_LCD_BGR555
442 bool "Display in BGR555 mode"
444 Use the BGR555 output mode. Otherwise RGB565 is used.
447 bool "Display support for BCM2835"
449 The graphics processor already sets up the display so this driver
450 simply checks the resolution and then sets up the frame buffer with
451 that same resolution (or as near as possible) and 32bpp depth, so
452 that U-Boot can access it with full colour depth.
454 config VIDEO_LCD_ORISETECH_OTM8009A
455 bool "OTM8009A DSI LCD panel support"
456 select VIDEO_MIPI_DSI
458 Say Y here if you want to enable support for Orise Technology
459 otm8009a 480x800 dsi 2dl panel.
461 config VIDEO_LCD_RAYDIUM_RM68200
462 bool "RM68200 DSI LCD panel support"
463 select VIDEO_MIPI_DSI
465 Say Y here if you want to enable support for Raydium RM68200
466 720x1280 DSI video mode panel.
468 config VIDEO_LCD_SSD2828
469 bool "SSD2828 bridge chip"
471 Support for the SSD2828 bridge chip, which can take pixel data coming
472 from a parallel LCD interface and translate it on the fly into MIPI DSI
473 interface for driving a MIPI compatible LCD panel. It uses SPI for
476 config VIDEO_LCD_SSD2828_TX_CLK
477 int "SSD2828 TX_CLK frequency (in MHz)"
478 depends on VIDEO_LCD_SSD2828
481 The frequency of the crystal, which is clocking SSD2828. It may be
482 anything in the 8MHz-30MHz range and the exact value should be
483 retrieved from the board schematics. Or in the case of Allwinner
484 hardware, it can be usually found as 'lcd_xtal_freq' variable in
485 FEX files. It can be also set to 0 for selecting PCLK from the
486 parallel LCD interface instead of TX_CLK as the PLL clock source.
488 config VIDEO_LCD_SSD2828_RESET
489 string "RESET pin of SSD2828"
490 depends on VIDEO_LCD_SSD2828
493 The reset pin of SSD2828 chip. This takes a string in the format
494 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
496 config VIDEO_LCD_TDO_TL070WSH30
497 bool "TDO TL070WSH30 DSI LCD panel support"
498 select VIDEO_MIPI_DSI
500 Say Y here if you want to enable support for TDO TL070WSH30
501 1024x600 DSI video mode panel.
503 config VIDEO_LCD_HITACHI_TX18D42VM
504 bool "Hitachi tx18d42vm LVDS LCD panel support"
506 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
507 lcd controller which needs to be initialized over SPI, once that is
508 done they work like a regular LVDS panel.
510 config VIDEO_LCD_SPI_CS
511 string "SPI CS pin for LCD related config job"
512 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
515 This is one of the SPI communication pins, involved in setting up a
516 working LCD configuration. The exact role of SPI may differ for
517 different hardware setups. The option takes a string in the format
518 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
520 config VIDEO_LCD_SPI_SCLK
521 string "SPI SCLK pin for LCD related config job"
522 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
525 This is one of the SPI communication pins, involved in setting up a
526 working LCD configuration. The exact role of SPI may differ for
527 different hardware setups. The option takes a string in the format
528 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
530 config VIDEO_LCD_SPI_MOSI
531 string "SPI MOSI pin for LCD related config job"
532 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
535 This is one of the SPI communication pins, involved in setting up a
536 working LCD configuration. The exact role of SPI may differ for
537 different hardware setups. The option takes a string in the format
538 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
540 config VIDEO_LCD_SPI_MISO
541 string "SPI MISO pin for LCD related config job (optional)"
542 depends on VIDEO_LCD_SSD2828
545 This is one of the SPI communication pins, involved in setting up a
546 working LCD configuration. The exact role of SPI may differ for
547 different hardware setups. If wired up, this pin may provide additional
548 useful functionality. Such as bi-directional communication with the
549 hardware and LCD panel id retrieval (if the panel can report it). The
550 option takes a string in the format understood by 'sunxi_name_to_gpio'
551 function, e.g. PH1 for pin 1 of port H.
553 source "drivers/video/meson/Kconfig"
556 bool "Armada XP LCD controller"
558 Support for the LCD controller integrated in the Marvell
562 bool "Enable OMAP3+ DSS Support"
563 depends on ARCH_OMAP2PLUS
565 This enables the Display subsystem (DSS) on OMAP3+ boards.
568 bool "Enable EDID library"
570 This enables library for accessing EDID data from an LCD panel.
573 bool "Enable Display support"
577 This supports drivers that provide a display, such as eDP (Embedded
578 DisplayPort) and HDMI (High Definition Multimedia Interface).
579 The devices provide a simple interface to start up the display,
580 read display information and enable it.
583 bool "Enable NXP TDA19988 support"
586 This enables support for the NXP TDA19988 HDMI encoder. This encoder
587 will convert RGB data streams into HDMI-encoded signals.
590 bool "Enable ATMEL video support using HLCDC"
592 HLCDC supports video output to an attached LCD panel.
594 source "drivers/video/ti/Kconfig"
596 source "drivers/video/exynos/Kconfig"
598 config LOGICORE_DP_TX
599 bool "Enable Logicore DP TX driver"
602 Enable the driver for the transmitter part of the Xilinx LogiCORE
603 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
604 video interface as defined by VESA DisplayPort v1.2.
606 Note that this is a pure transmitter device, and has no display
607 capabilities by itself.
609 config VIDEO_BROADWELL_IGD
610 bool "Enable Intel Broadwell integrated graphics device"
613 This enables support for integrated graphics on Intel broadwell
614 devices. Initialisation is mostly performed by a VGA boot ROM, with
615 some setup handled by U-Boot itself. The graphics adaptor works as
616 a VESA device and supports LCD panels, eDP and LVDS outputs.
617 Configuration of most aspects of device operation is performed using
618 a special tool which configures the VGA ROM, but the graphics
619 resolution can be selected in U-Boot.
621 config VIDEO_IVYBRIDGE_IGD
622 bool "Enable Intel Ivybridge integration graphics support"
625 This enables support for integrated graphics on Intel ivybridge
626 devices. Initialisation is mostly performed by a VGA boot ROM, with
627 some setup handled by U-Boot itself. The graphics adaptor works as
628 a VESA device and supports LCD panels, eDP and LVDS outputs.
629 Configuration of most aspects of device operation is performed using
630 a special tool which configures the VGA ROM, but the graphics
631 resolution can be selected in U-Boot.
633 source "drivers/video/rockchip/Kconfig"
635 config VIDEO_ARM_MALIDP
636 bool "Enable Arm Mali Display Processor support"
637 depends on OF_CONTROL
640 This enables support for Arm Ltd Mali Display Processors from
641 the DP500, DP550 and DP650 family.
643 config VIDEO_SANDBOX_SDL
644 bool "Enable sandbox video console using SDL"
645 depends on SANDBOX_SDL
647 When using sandbox you can enable an emulated LCD display which
648 appears as an SDL (Simple DirectMedia Layer) window. This is a
649 console device and can display stdout output. Within U-Boot is is
650 a normal bitmap display and can display images as well as text.
652 source "drivers/video/stm32/Kconfig"
654 source "drivers/video/tidss/Kconfig"
657 bool "Enable LCD support on Tegra20"
658 depends on OF_CONTROL
660 Tegra20 supports video output to an attached LCD panel as well as
661 other options such as HDMI. Only the LCD is supported in U-Boot.
662 This option enables this support which can be used on devices which
663 have an LCD display connected.
665 config VIDEO_TEGRA124
666 bool "Enable video support on Tegra124"
668 Tegra124 supports many video output options including eDP and
669 HDMI. At present only eDP is supported by U-Boot. This option
670 enables this support which can be used on devices which
671 have an eDP display connected.
673 source "drivers/video/bridge/Kconfig"
675 source "drivers/video/imx/Kconfig"
678 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
680 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
683 bool "Enable video support on Nexell SoC"
684 depends on ARCH_S5P6818 || ARCH_S5P4418
686 Nexell SoC supports many video output options including eDP and
687 HDMI. This option enables this support which can be used on devices
688 which have an eDP display connected.
691 bool "Enable video support for Seps525"
694 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
695 Currently driver is supporting only SPI interface.
697 config VIDEO_ZYNQMP_DPSUB
698 bool "Enable video support for ZynqMP Display Port"
699 depends on ZYNQMP_POWER_DOMAIN
701 Enable support for Xilinx ZynqMP Display Port. Currently this file
702 is used as placeholder for driver. The main reason is to record
703 compatible string and calling power domain driver.
705 source "drivers/video/nexell/Kconfig"
707 config CONSOLE_SCROLL_LINES
708 int "Number of lines to scroll the console by"
711 When the console need to be scrolled, this is the number of
712 lines to scroll by. It defaults to 1. Increasing this makes the
713 console jump but can help speed up operation when scrolling
719 Enables the common driver code for the Designware HDMI TX
720 block found in SoCs from various vendors.
721 As this does not provide any functionality by itself (but
722 rather requires a SoC-specific glue driver to call it), it
723 can not be enabled from the configuration menu.
725 config VIDEO_DSI_HOST_SANDBOX
726 bool "Enable sandbox for dsi host"
728 select VIDEO_MIPI_DSI
730 Enable support for sandbox dsi host device used for testing
732 Display Serial Interface (DSI) defines a serial bus and
733 a communication protocol between the host and the device
736 config VIDEO_DW_MIPI_DSI
738 select VIDEO_MIPI_DSI
740 Enables the common driver code for the Synopsis Designware
741 MIPI DSI block found in SoCs from various vendors.
742 As this does not provide any functionality by itself (but
743 rather requires a SoC-specific glue driver to call it), it
744 can not be enabled from the configuration menu.
747 bool "Simple display driver for preconfigured display"
749 Enables a simple generic display driver which utilizes the
750 simple-framebuffer devicetree bindings.
752 This driver assumes that the display hardware has been initialized
753 before u-boot starts, and u-boot will simply render to the pre-
754 allocated frame buffer surface.
756 config VIDEO_DT_SIMPLEFB
757 bool "Enable SimpleFB support for passing framebuffer to OS"
759 Enables the code to pass the framebuffer to the kernel as a
760 simple framebuffer in the device tree.
761 The video output is initialized by U-Boot, and kept by the
764 config VIDEO_MCDE_SIMPLE
765 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
767 Enables a simple display driver for ST-Ericsson MCDE
768 (Multichannel Display Engine), which reads the configuration from
771 This driver assumes that the display hardware has been initialized
772 before u-boot starts, and u-boot will simply render to the pre-
773 allocated frame buffer surface.
776 bool "Enable OSD support"
779 This supports drivers that provide a OSD (on-screen display), which
780 is a (usually text-oriented) graphics buffer to show information on
784 bool "Enable sandbox OSD"
787 Enable support for sandbox OSD device used for testing purposes.
790 bool "Enable IHS video out driver"
793 Enable support for the gdsys Integrated Hardware Systems (IHS) video
794 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
795 textual overlays of the display outputs.
798 bool "Show a splash-screen image"
800 If this option is set, the environment is checked for a variable
801 "splashimage". If found, the usual display of logo, copyright and
802 system information on the LCD is suppressed and the BMP image at the
803 address specified in "splashimage" is loaded instead. The console is
804 redirected to the "nulldev", too. This allows for a "silent" boot
805 where a splash screen is loaded very quickly after power-on.
807 The splash_screen_prepare() function is a weak function defined in
808 common/splash.c. It is called as part of the splash screen display
809 sequence. It gives the board an opportunity to prepare the splash
810 image data before it is processed and sent to the frame buffer by
811 U-Boot. Define your own version to use this feature.
815 config SPLASH_SCREEN_ALIGN
816 bool "Allow positioning the splash image anywhere on the display"
818 If this option is set the splash image can be freely positioned
819 on the screen. Environment variable "splashpos" specifies the
820 position as "x,y". If a positive number is given it is used as
821 number of pixel from left/top. If a negative number is given it
822 is used as number of pixel from right/bottom. You can also
823 specify 'm' for centering the image.
827 => image at center of screen
829 setenv splashpos 30,20
830 => image at x = 30 and y = 20
832 setenv splashpos -10,m
833 => vertically centered image
834 at x = dspWidth - bmpWidth - 9
836 config HIDE_LOGO_VERSION
837 bool "Hide the version information on the splash screen"
839 Normally the U-Boot version string is shown on the display when the
840 splash screen is enabled. This information is not otherwise visible
841 since video starts up after U-Boot has displayed the initial banner.
843 Enable this option to hide this information.
846 bool "Control the source of the splash image"
848 Use the splash_source.c library. This library provides facilities to
849 declare board specific splash image locations, routines for loading
850 splash image from supported locations, and a way of controlling the
851 selected splash location using the "splashsource" environment
854 This CONFIG works as follows:
856 - If splashsource is set to a supported location name as defined by
857 board code, use that splash location.
858 - If splashsource is undefined, use the first splash location as
860 - If splashsource is set to an unsupported value, do not load a splash
863 A splash source location can describe either storage with raw data, a
864 storage formatted with a file system or a FIT image. In case of a
865 filesystem, the splash screen data is loaded as a file. The name of
866 the splash screen file can be controlled with the environment variable
869 To enable loading the splash image from a FIT image, CONFIG_FIT must
870 be enabled. The FIT image has to start at the 'offset' field address
871 in the selected splash location. The name of splash image within the
872 FIT shall be specified by the environment variable "splashfile".
874 In case the environment variable "splashfile" is not defined the
875 default name 'splash.bmp' will be used.
877 endif # SPLASH_SCREEN
879 config VIDEO_BMP_GZIP
880 bool "Gzip compressed BMP image support"
881 depends on CMD_BMP || SPLASH_SCREEN
883 If this option is set, additionally to standard BMP
884 images, gzipped BMP images can be displayed via the
885 splashscreen support or the bmp command.
887 config VIDEO_LOGO_MAX_SIZE
888 hex "Maximum size of the bitmap logo in bytes"
891 Sets the maximum uncompressed size of the logo. This is needed when
892 decompressing a BMP file using the gzip algorithm, since it cannot
893 read the size from the bitmap header.
895 config VIDEO_BMP_RLE8
896 bool "Run length encoded BMP image (RLE8) support"
898 If this option is set, the 8-bit RLE compressed BMP images
902 bool "16-bit-per-pixel BMP image support"
904 Support display of bitmaps file with 16-bit-per-pixel
907 bool "24-bit-per-pixel BMP image support"
909 Support display of bitmaps file with 24-bit-per-pixel.
912 bool "32-bit-per-pixel BMP image support"
914 Support display of bitmaps file with 32-bit-per-pixel.