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"
168 select CMD_SELECT_FONT
170 TrueTrype fonts can provide outline-drawing capability rather than
171 needing to provide a bitmap for each font and size that is needed.
172 With this option you can adjust the text size and use a variety of
173 fonts. Note that this is noticeably slower than with normal console.
175 config CONSOLE_TRUETYPE_SIZE
176 int "TrueType font size"
177 depends on CONSOLE_TRUETYPE
180 This sets the font size for the console. The size is measured in
181 pixels and is the nominal height of a character. Note that fonts
182 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
183 However that measurement depends on the size of your display and
184 there is no standard display density. At present there is not a
185 method to select the display's physical size, which would allow
186 U-Boot to calculate the correct font size.
188 config CONSOLE_TRUETYPE_MAX_METRICS
189 int "TrueType maximum number of font / size combinations"
190 depends on CONSOLE_TRUETYPE
194 This sets the number of font / size combinations which can be used by
195 the console. For simple console use a single font is enough. When
196 boot menus are in use, this may need to be increased.
198 Note that a separate entry is needed for each font size, even if the
199 font itself is the same. This is because the entry caches various
200 font metrics which are expensive to regenerate each time the font
203 config SYS_WHITE_ON_BLACK
204 bool "Display console as white on a black background"
205 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
207 Normally the display is black on a white background, Enable this
208 option to invert this, i.e. white on a black background. This can be
209 better in low-light situations or to reduce eye strain in some
213 bool "Skip framebuffer clear"
215 If firmware (whatever loads u-boot) has already put a splash image
216 on screen, you might want to preserve it until whatever u-boot
217 loads takes over the screen. This, for example, can be used to
218 keep splash image on screen until grub graphical boot menu starts.
221 bool "Enable panel uclass support"
224 This provides panel uclass driver that enables basic panel support.
227 bool "Enable simple panel support"
228 depends on PANEL && BACKLIGHT && DM_GPIO
231 This turns on a simple panel driver that enables a compatible
235 bool "Enable Himax HX-8238D LCD driver"
238 Support for HX-8238D LCD Panel
239 The HX8238-D is a single chip controller and driver LSI that
240 integrates the power circuit.
241 It can drive a maximum 960x240 dot graphics on a-TFT panel
242 displays in 16M colors with dithering.
244 source "drivers/video/fonts/Kconfig"
246 config VIDCONSOLE_AS_LCD
247 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
249 This is a work-around for boards which have 'lcd' or 'vga' in their
250 stdout environment variable, but have moved to use driver model for
251 video. In this case the console will no-longer work. While it is
252 possible to update the environment, the breakage may be confusing for
253 users. This option will be removed around the end of 2020.
255 config VIDCONSOLE_AS_NAME
256 string "Use 'vidconsole' when string defined here is seen in stdout"
257 depends on VIDCONSOLE_AS_LCD
258 default "lcd" if LCD || TEGRA_COMMON
259 default "vga" if !LCD
261 This is a work-around for boards which have 'lcd' or 'vga' in their
262 stdout environment variable, but have moved to use driver model for
263 video. In this case the console will no-longer work. While it is
264 possible to update the environment, the breakage may be confusing for
265 users. This option will be removed around the end of 2020.
267 config VIDEO_COREBOOT
268 bool "Enable coreboot framebuffer driver support"
271 Turn on this option to enable a framebuffer driver when U-Boot is
272 loaded by coreboot where the graphics device is configured by
273 coreboot already. This can in principle be used with any platform
274 that coreboot supports.
277 bool "Enable EFI framebuffer driver support"
278 depends on EFI_STUB || EFI_APP
280 Turn on this option to enable a framebuffeer driver when U-Boot is
281 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
282 the graphics device is configured by the EFI BIOS already. This can
283 in principle be used with any platform that has an EFI BIOS.
286 bool "Enable VESA video driver support"
288 Turn on this option to enable a very simple driver which uses vesa
289 to discover the video mode and then provides a frame buffer for use
290 by U-Boot. This can in principle be used with any platform that
291 supports PCI and video cards that support VESA BIOS Extension (VBE).
293 config FRAMEBUFFER_SET_VESA_MODE
294 bool "Set framebuffer graphics resolution"
295 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
297 Set VESA/native framebuffer mode (needed for bootsplash and graphical
301 prompt "framebuffer graphics resolution"
302 default FRAMEBUFFER_VESA_MODE_118
303 depends on FRAMEBUFFER_SET_VESA_MODE
305 This option sets the resolution used for the U-Boot framebuffer (and
308 config FRAMEBUFFER_VESA_MODE_100
309 bool "640x400 256-color"
311 config FRAMEBUFFER_VESA_MODE_101
312 bool "640x480 256-color"
314 config FRAMEBUFFER_VESA_MODE_102
315 bool "800x600 16-color"
317 config FRAMEBUFFER_VESA_MODE_103
318 bool "800x600 256-color"
320 config FRAMEBUFFER_VESA_MODE_104
321 bool "1024x768 16-color"
323 config FRAMEBUFFER_VESA_MODE_105
324 bool "1024x768 256-color"
326 config FRAMEBUFFER_VESA_MODE_106
327 bool "1280x1024 16-color"
329 config FRAMEBUFFER_VESA_MODE_107
330 bool "1280x1024 256-color"
332 config FRAMEBUFFER_VESA_MODE_108
335 config FRAMEBUFFER_VESA_MODE_109
338 config FRAMEBUFFER_VESA_MODE_10A
341 config FRAMEBUFFER_VESA_MODE_10B
344 config FRAMEBUFFER_VESA_MODE_10C
347 config FRAMEBUFFER_VESA_MODE_10D
348 bool "320x200 32k-color (1:5:5:5)"
350 config FRAMEBUFFER_VESA_MODE_10E
351 bool "320x200 64k-color (5:6:5)"
353 config FRAMEBUFFER_VESA_MODE_10F
354 bool "320x200 16.8M-color (8:8:8)"
356 config FRAMEBUFFER_VESA_MODE_110
357 bool "640x480 32k-color (1:5:5:5)"
359 config FRAMEBUFFER_VESA_MODE_111
360 bool "640x480 64k-color (5:6:5)"
362 config FRAMEBUFFER_VESA_MODE_112
363 bool "640x480 16.8M-color (8:8:8)"
365 config FRAMEBUFFER_VESA_MODE_113
366 bool "800x600 32k-color (1:5:5:5)"
368 config FRAMEBUFFER_VESA_MODE_114
369 bool "800x600 64k-color (5:6:5)"
371 config FRAMEBUFFER_VESA_MODE_115
372 bool "800x600 16.8M-color (8:8:8)"
374 config FRAMEBUFFER_VESA_MODE_116
375 bool "1024x768 32k-color (1:5:5:5)"
377 config FRAMEBUFFER_VESA_MODE_117
378 bool "1024x768 64k-color (5:6:5)"
380 config FRAMEBUFFER_VESA_MODE_118
381 bool "1024x768 16.8M-color (8:8:8)"
383 config FRAMEBUFFER_VESA_MODE_119
384 bool "1280x1024 32k-color (1:5:5:5)"
386 config FRAMEBUFFER_VESA_MODE_11A
387 bool "1280x1024 64k-color (5:6:5)"
389 config FRAMEBUFFER_VESA_MODE_11B
390 bool "1280x1024 16.8M-color (8:8:8)"
392 config FRAMEBUFFER_VESA_MODE_USER
393 bool "Manually select VESA mode"
397 # Map the config names to an integer (KB).
398 config FRAMEBUFFER_VESA_MODE
399 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
401 default 0x100 if FRAMEBUFFER_VESA_MODE_100
402 default 0x101 if FRAMEBUFFER_VESA_MODE_101
403 default 0x102 if FRAMEBUFFER_VESA_MODE_102
404 default 0x103 if FRAMEBUFFER_VESA_MODE_103
405 default 0x104 if FRAMEBUFFER_VESA_MODE_104
406 default 0x105 if FRAMEBUFFER_VESA_MODE_105
407 default 0x106 if FRAMEBUFFER_VESA_MODE_106
408 default 0x107 if FRAMEBUFFER_VESA_MODE_107
409 default 0x108 if FRAMEBUFFER_VESA_MODE_108
410 default 0x109 if FRAMEBUFFER_VESA_MODE_109
411 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
412 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
413 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
414 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
415 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
416 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
417 default 0x110 if FRAMEBUFFER_VESA_MODE_110
418 default 0x111 if FRAMEBUFFER_VESA_MODE_111
419 default 0x112 if FRAMEBUFFER_VESA_MODE_112
420 default 0x113 if FRAMEBUFFER_VESA_MODE_113
421 default 0x114 if FRAMEBUFFER_VESA_MODE_114
422 default 0x115 if FRAMEBUFFER_VESA_MODE_115
423 default 0x116 if FRAMEBUFFER_VESA_MODE_116
424 default 0x117 if FRAMEBUFFER_VESA_MODE_117
425 default 0x118 if FRAMEBUFFER_VESA_MODE_118
426 default 0x119 if FRAMEBUFFER_VESA_MODE_119
427 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
428 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
429 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
431 config VIDEO_LCD_ANX9804
432 bool "ANX9804 bridge chip"
434 Support for the ANX9804 bridge chip, which can take pixel data coming
435 from a parallel LCD interface and translate it on the fy into a DP
436 interface for driving eDP TFT displays. It uses I2C for configuration.
439 bool "Atmel LCD panel support"
442 config ATMEL_LCD_BGR555
443 bool "Display in BGR555 mode"
445 Use the BGR555 output mode. Otherwise RGB565 is used.
448 bool "Display support for BCM2835"
450 The graphics processor already sets up the display so this driver
451 simply checks the resolution and then sets up the frame buffer with
452 that same resolution (or as near as possible) and 32bpp depth, so
453 that U-Boot can access it with full colour depth.
455 config VIDEO_LCD_ORISETECH_OTM8009A
456 bool "OTM8009A DSI LCD panel support"
457 select VIDEO_MIPI_DSI
459 Say Y here if you want to enable support for Orise Technology
460 otm8009a 480x800 dsi 2dl panel.
462 config VIDEO_LCD_RAYDIUM_RM68200
463 bool "RM68200 DSI LCD panel support"
464 select VIDEO_MIPI_DSI
466 Say Y here if you want to enable support for Raydium RM68200
467 720x1280 DSI video mode panel.
469 config VIDEO_LCD_SSD2828
470 bool "SSD2828 bridge chip"
472 Support for the SSD2828 bridge chip, which can take pixel data coming
473 from a parallel LCD interface and translate it on the fly into MIPI DSI
474 interface for driving a MIPI compatible LCD panel. It uses SPI for
477 config VIDEO_LCD_SSD2828_TX_CLK
478 int "SSD2828 TX_CLK frequency (in MHz)"
479 depends on VIDEO_LCD_SSD2828
482 The frequency of the crystal, which is clocking SSD2828. It may be
483 anything in the 8MHz-30MHz range and the exact value should be
484 retrieved from the board schematics. Or in the case of Allwinner
485 hardware, it can be usually found as 'lcd_xtal_freq' variable in
486 FEX files. It can be also set to 0 for selecting PCLK from the
487 parallel LCD interface instead of TX_CLK as the PLL clock source.
489 config VIDEO_LCD_SSD2828_RESET
490 string "RESET pin of SSD2828"
491 depends on VIDEO_LCD_SSD2828
494 The reset pin of SSD2828 chip. This takes a string in the format
495 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
497 config VIDEO_LCD_TDO_TL070WSH30
498 bool "TDO TL070WSH30 DSI LCD panel support"
499 select VIDEO_MIPI_DSI
501 Say Y here if you want to enable support for TDO TL070WSH30
502 1024x600 DSI video mode panel.
504 config VIDEO_LCD_HITACHI_TX18D42VM
505 bool "Hitachi tx18d42vm LVDS LCD panel support"
507 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
508 lcd controller which needs to be initialized over SPI, once that is
509 done they work like a regular LVDS panel.
511 config VIDEO_LCD_SPI_CS
512 string "SPI CS pin for LCD related config job"
513 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
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. The option takes a string in the format
519 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
521 config VIDEO_LCD_SPI_SCLK
522 string "SPI SCLK pin for LCD related config job"
523 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
526 This is one of the SPI communication pins, involved in setting up a
527 working LCD configuration. The exact role of SPI may differ for
528 different hardware setups. The option takes a string in the format
529 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
531 config VIDEO_LCD_SPI_MOSI
532 string "SPI MOSI pin for LCD related config job"
533 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
536 This is one of the SPI communication pins, involved in setting up a
537 working LCD configuration. The exact role of SPI may differ for
538 different hardware setups. The option takes a string in the format
539 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
541 config VIDEO_LCD_SPI_MISO
542 string "SPI MISO pin for LCD related config job (optional)"
543 depends on VIDEO_LCD_SSD2828
546 This is one of the SPI communication pins, involved in setting up a
547 working LCD configuration. The exact role of SPI may differ for
548 different hardware setups. If wired up, this pin may provide additional
549 useful functionality. Such as bi-directional communication with the
550 hardware and LCD panel id retrieval (if the panel can report it). The
551 option takes a string in the format understood by 'sunxi_name_to_gpio'
552 function, e.g. PH1 for pin 1 of port H.
554 source "drivers/video/meson/Kconfig"
557 bool "Armada XP LCD controller"
559 Support for the LCD controller integrated in the Marvell
563 bool "Enable OMAP3+ DSS Support"
564 depends on ARCH_OMAP2PLUS
566 This enables the Display subsystem (DSS) on OMAP3+ boards.
569 bool "Enable EDID library"
571 This enables library for accessing EDID data from an LCD panel.
574 bool "Enable Display support"
578 This supports drivers that provide a display, such as eDP (Embedded
579 DisplayPort) and HDMI (High Definition Multimedia Interface).
580 The devices provide a simple interface to start up the display,
581 read display information and enable it.
584 bool "Enable NXP TDA19988 support"
587 This enables support for the NXP TDA19988 HDMI encoder. This encoder
588 will convert RGB data streams into HDMI-encoded signals.
591 bool "Enable ATMEL video support using HLCDC"
593 HLCDC supports video output to an attached LCD panel.
595 source "drivers/video/ti/Kconfig"
597 source "drivers/video/exynos/Kconfig"
599 config LOGICORE_DP_TX
600 bool "Enable Logicore DP TX driver"
603 Enable the driver for the transmitter part of the Xilinx LogiCORE
604 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
605 video interface as defined by VESA DisplayPort v1.2.
607 Note that this is a pure transmitter device, and has no display
608 capabilities by itself.
610 config VIDEO_BROADWELL_IGD
611 bool "Enable Intel Broadwell integrated graphics device"
614 This enables support for integrated graphics on Intel broadwell
615 devices. Initialisation is mostly performed by a VGA boot ROM, with
616 some setup handled by U-Boot itself. The graphics adaptor works as
617 a VESA device and supports LCD panels, eDP and LVDS outputs.
618 Configuration of most aspects of device operation is performed using
619 a special tool which configures the VGA ROM, but the graphics
620 resolution can be selected in U-Boot.
622 config VIDEO_IVYBRIDGE_IGD
623 bool "Enable Intel Ivybridge integration graphics support"
626 This enables support for integrated graphics on Intel ivybridge
627 devices. Initialisation is mostly performed by a VGA boot ROM, with
628 some setup handled by U-Boot itself. The graphics adaptor works as
629 a VESA device and supports LCD panels, eDP and LVDS outputs.
630 Configuration of most aspects of device operation is performed using
631 a special tool which configures the VGA ROM, but the graphics
632 resolution can be selected in U-Boot.
634 source "drivers/video/rockchip/Kconfig"
636 config VIDEO_ARM_MALIDP
637 bool "Enable Arm Mali Display Processor support"
638 depends on OF_CONTROL
641 This enables support for Arm Ltd Mali Display Processors from
642 the DP500, DP550 and DP650 family.
644 config VIDEO_SANDBOX_SDL
645 bool "Enable sandbox video console using SDL"
646 depends on SANDBOX_SDL
648 When using sandbox you can enable an emulated LCD display which
649 appears as an SDL (Simple DirectMedia Layer) window. This is a
650 console device and can display stdout output. Within U-Boot is is
651 a normal bitmap display and can display images as well as text.
653 source "drivers/video/stm32/Kconfig"
655 source "drivers/video/tidss/Kconfig"
658 bool "Enable LCD support on Tegra20"
659 depends on OF_CONTROL
661 Tegra20 supports video output to an attached LCD panel as well as
662 other options such as HDMI. Only the LCD is supported in U-Boot.
663 This option enables this support which can be used on devices which
664 have an LCD display connected.
666 config VIDEO_TEGRA124
667 bool "Enable video support on Tegra124"
669 Tegra124 supports many video output options including eDP and
670 HDMI. At present only eDP is supported by U-Boot. This option
671 enables this support which can be used on devices which
672 have an eDP display connected.
674 source "drivers/video/bridge/Kconfig"
676 source "drivers/video/imx/Kconfig"
679 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
681 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
684 bool "Enable video support on Nexell SoC"
685 depends on ARCH_S5P6818 || ARCH_S5P4418
687 Nexell SoC supports many video output options including eDP and
688 HDMI. This option enables this support which can be used on devices
689 which have an eDP display connected.
692 bool "Enable video support for Seps525"
695 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
696 Currently driver is supporting only SPI interface.
698 config VIDEO_ZYNQMP_DPSUB
699 bool "Enable video support for ZynqMP Display Port"
700 depends on ZYNQMP_POWER_DOMAIN
702 Enable support for Xilinx ZynqMP Display Port. Currently this file
703 is used as placeholder for driver. The main reason is to record
704 compatible string and calling power domain driver.
706 source "drivers/video/nexell/Kconfig"
708 config CONSOLE_SCROLL_LINES
709 int "Number of lines to scroll the console by"
712 When the console need to be scrolled, this is the number of
713 lines to scroll by. It defaults to 1. Increasing this makes the
714 console jump but can help speed up operation when scrolling
720 Enables the common driver code for the Designware HDMI TX
721 block found in SoCs from various vendors.
722 As this does not provide any functionality by itself (but
723 rather requires a SoC-specific glue driver to call it), it
724 can not be enabled from the configuration menu.
726 config VIDEO_DSI_HOST_SANDBOX
727 bool "Enable sandbox for dsi host"
729 select VIDEO_MIPI_DSI
731 Enable support for sandbox dsi host device used for testing
733 Display Serial Interface (DSI) defines a serial bus and
734 a communication protocol between the host and the device
737 config VIDEO_DW_MIPI_DSI
739 select VIDEO_MIPI_DSI
741 Enables the common driver code for the Synopsis Designware
742 MIPI DSI block found in SoCs from various vendors.
743 As this does not provide any functionality by itself (but
744 rather requires a SoC-specific glue driver to call it), it
745 can not be enabled from the configuration menu.
748 bool "Simple display driver for preconfigured display"
750 Enables a simple generic display driver which utilizes the
751 simple-framebuffer devicetree bindings.
753 This driver assumes that the display hardware has been initialized
754 before u-boot starts, and u-boot will simply render to the pre-
755 allocated frame buffer surface.
757 config VIDEO_DT_SIMPLEFB
758 bool "Enable SimpleFB support for passing framebuffer to OS"
760 Enables the code to pass the framebuffer to the kernel as a
761 simple framebuffer in the device tree.
762 The video output is initialized by U-Boot, and kept by the
765 config VIDEO_MCDE_SIMPLE
766 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
768 Enables a simple display driver for ST-Ericsson MCDE
769 (Multichannel Display Engine), which reads the configuration from
772 This driver assumes that the display hardware has been initialized
773 before u-boot starts, and u-boot will simply render to the pre-
774 allocated frame buffer surface.
777 bool "Enable OSD support"
780 This supports drivers that provide a OSD (on-screen display), which
781 is a (usually text-oriented) graphics buffer to show information on
785 bool "Enable sandbox OSD"
788 Enable support for sandbox OSD device used for testing purposes.
791 bool "Enable IHS video out driver"
794 Enable support for the gdsys Integrated Hardware Systems (IHS) video
795 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
796 textual overlays of the display outputs.
799 bool "Show a splash-screen image"
801 If this option is set, the environment is checked for a variable
802 "splashimage". If found, the usual display of logo, copyright and
803 system information on the LCD is suppressed and the BMP image at the
804 address specified in "splashimage" is loaded instead. The console is
805 redirected to the "nulldev", too. This allows for a "silent" boot
806 where a splash screen is loaded very quickly after power-on.
808 The splash_screen_prepare() function is a weak function defined in
809 common/splash.c. It is called as part of the splash screen display
810 sequence. It gives the board an opportunity to prepare the splash
811 image data before it is processed and sent to the frame buffer by
812 U-Boot. Define your own version to use this feature.
816 config SPLASH_SCREEN_ALIGN
817 bool "Allow positioning the splash image anywhere on the display"
819 If this option is set the splash image can be freely positioned
820 on the screen. Environment variable "splashpos" specifies the
821 position as "x,y". If a positive number is given it is used as
822 number of pixel from left/top. If a negative number is given it
823 is used as number of pixel from right/bottom. You can also
824 specify 'm' for centering the image.
828 => image at center of screen
830 setenv splashpos 30,20
831 => image at x = 30 and y = 20
833 setenv splashpos -10,m
834 => vertically centered image
835 at x = dspWidth - bmpWidth - 9
837 config HIDE_LOGO_VERSION
838 bool "Hide the version information on the splash screen"
840 Normally the U-Boot version string is shown on the display when the
841 splash screen is enabled. This information is not otherwise visible
842 since video starts up after U-Boot has displayed the initial banner.
844 Enable this option to hide this information.
847 bool "Control the source of the splash image"
849 Use the splash_source.c library. This library provides facilities to
850 declare board specific splash image locations, routines for loading
851 splash image from supported locations, and a way of controlling the
852 selected splash location using the "splashsource" environment
855 This CONFIG works as follows:
857 - If splashsource is set to a supported location name as defined by
858 board code, use that splash location.
859 - If splashsource is undefined, use the first splash location as
861 - If splashsource is set to an unsupported value, do not load a splash
864 A splash source location can describe either storage with raw data, a
865 storage formatted with a file system or a FIT image. In case of a
866 filesystem, the splash screen data is loaded as a file. The name of
867 the splash screen file can be controlled with the environment variable
870 To enable loading the splash image from a FIT image, CONFIG_FIT must
871 be enabled. The FIT image has to start at the 'offset' field address
872 in the selected splash location. The name of splash image within the
873 FIT shall be specified by the environment variable "splashfile".
875 In case the environment variable "splashfile" is not defined the
876 default name 'splash.bmp' will be used.
878 endif # SPLASH_SCREEN
880 config VIDEO_BMP_GZIP
881 bool "Gzip compressed BMP image support"
882 depends on CMD_BMP || SPLASH_SCREEN
884 If this option is set, additionally to standard BMP
885 images, gzipped BMP images can be displayed via the
886 splashscreen support or the bmp command.
888 config VIDEO_LOGO_MAX_SIZE
889 hex "Maximum size of the bitmap logo in bytes"
892 Sets the maximum uncompressed size of the logo. This is needed when
893 decompressing a BMP file using the gzip algorithm, since it cannot
894 read the size from the bitmap header.
896 config VIDEO_BMP_RLE8
897 bool "Run length encoded BMP image (RLE8) support"
899 If this option is set, the 8-bit RLE compressed BMP images
903 bool "16-bit-per-pixel BMP image support"
905 Support display of bitmaps file with 16-bit-per-pixel
908 bool "24-bit-per-pixel BMP image support"
910 Support display of bitmaps file with 24-bit-per-pixel.
913 bool "32-bit-per-pixel BMP image support"
915 Support display of bitmaps file with 32-bit-per-pixel.