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"
20 default y if !SPLASH_SCREEN
23 This enables showing the U-Boot logo on the display when a video
24 device is probed. It appears at the top right. The logo itself is at
25 tools/logos/u-boot_logo.bmp and looks best when the display has a
29 bool "Enable panel backlight uclass support"
33 This provides backlight uclass driver that enables basic panel
36 config VIDEO_PCI_DEFAULT_FB_SIZE
37 hex "Default framebuffer size to use if no drivers request it"
39 default 0x1000000 if X86 && PCI
40 default 0 if !(X86 && PCI)
42 Generally, video drivers request the amount of memory they need for
43 the frame buffer when they are bound, by setting the size field in
44 struct video_uc_plat. That memory is then reserved for use after
45 relocation. But PCI drivers cannot be bound before relocation unless
46 they are mentioned in the devicetree.
48 With this value set appropriately, it is possible for PCI video
49 devices to have a framebuffer allocated by U-Boot.
51 Note: the framebuffer needs to be large enough to store all pixels at
52 maximum resolution. For example, at 1920 x 1200 with 32 bits per
53 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
56 bool "Enable copying the frame buffer to a hardware copy"
59 On some machines (e.g. x86), reading from the frame buffer is very
60 slow because it is uncached. To improve performance, this feature
61 allows the frame buffer to be kept in cached memory (allocated by
62 U-Boot) and then copied to the hardware frame-buffer as needed.
64 To use this, your video driver must set @copy_base in
68 bool "Generic PWM based Backlight Driver"
69 depends on BACKLIGHT && DM_PWM
72 If you have a LCD backlight adjustable by PWM, say Y to enable
74 This driver can be use with "simple-panel" and
75 it understands the standard device tree
76 (leds/backlight/pwm-backlight.txt)
79 bool "Generic GPIO based Backlight Driver"
82 If you have a LCD backlight adjustable by GPIO, say Y to enable
84 This driver can be used with "simple-panel" and
85 it understands the standard device tree
86 (leds/backlight/gpio-backlight.txt)
89 bool "Support 8-bit-per-pixel displays"
93 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
94 Enabling this will include code to support this display. Without
95 this option, such displays will not be supported and console output
99 bool "Support 16-bit-per-pixel displays"
103 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
104 Enabling this will include code to support this display. Without
105 this option, such displays will not be supported and console output
109 bool "Support 32-bit-per-pixel displays"
113 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
114 Enabling this will include code to support this display. Without
115 this option, such displays will not be supported and console output
119 bool "Support ANSI escape sequences in video console"
123 Enable ANSI escape sequence decoding for a more fully functional
126 config VIDEO_MIPI_DSI
127 bool "Support MIPI DSI interface"
130 Support MIPI DSI interface for driving a MIPI compatible device.
131 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
132 serial interface between a host processor and a display module.
134 config CONSOLE_NORMAL
135 bool "Support a simple text console"
137 default y if DM_VIDEO
139 Support drawing text on the frame buffer console so that it can be
140 used as a console. Rotation is not supported by this driver (see
141 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
144 config CONSOLE_ROTATION
145 bool "Support rotated displays"
148 Sometimes, for example if the display is mounted in portrait
149 mode or even if it's mounted landscape but rotated by 180degree,
150 we need to rotate our content of the display relative to the
151 framebuffer, so that user can read the messages which are
152 printed out. Enable this option to include a text driver which can
153 support this. The rotation is set by the 'rot' parameter in
154 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
155 degrees, 3=270 degrees.
157 config CONSOLE_TRUETYPE
158 bool "Support a console that uses TrueType fonts"
161 TrueTrype fonts can provide outline-drawing capability rather than
162 needing to provide a bitmap for each font and size that is needed.
163 With this option you can adjust the text size and use a variety of
164 fonts. Note that this is noticeably slower than with normal console.
166 config CONSOLE_TRUETYPE_SIZE
167 int "TrueType font size"
168 depends on CONSOLE_TRUETYPE
171 This sets the font size for the console. The size is measured in
172 pixels and is the nominal height of a character. Note that fonts
173 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
174 However that measurement depends on the size of your display and
175 there is no standard display density. At present there is not a
176 method to select the display's physical size, which would allow
177 U-Boot to calculate the correct font size.
179 config CONSOLE_TRUETYPE_MAX_METRICS
180 int "TrueType maximum number of font / size combinations"
181 depends on CONSOLE_TRUETYPE
185 This sets the number of font / size combinations which can be used by
186 the console. For simple console use a single font is enough. When
187 boot menus are in use, this may need to be increased.
189 Note that a separate entry is needed for each font size, even if the
190 font itself is the same. This is because the entry caches various
191 font metrics which are expensive to regenerate each time the font
194 config SYS_WHITE_ON_BLACK
195 bool "Display console as white on a black background"
196 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
198 Normally the display is black on a white background, Enable this
199 option to invert this, i.e. white on a black background. This can be
200 better in low-light situations or to reduce eye strain in some
204 bool "Skip framebuffer clear"
206 If firmware (whatever loads u-boot) has already put a splash image
207 on screen, you might want to preserve it until whatever u-boot
208 loads takes over the screen. This, for example, can be used to
209 keep splash image on screen until grub graphical boot menu starts.
212 bool "Enable panel uclass support"
216 This provides panel uclass driver that enables basic panel support.
219 bool "Enable simple panel support"
220 depends on PANEL && BACKLIGHT && DM_GPIO
223 This turns on a simple panel driver that enables a compatible
227 bool "Enable Himax HX-8238D LCD driver"
230 Support for HX-8238D LCD Panel
231 The HX8238-D is a single chip controller and driver LSI that
232 integrates the power circuit.
233 It can drive a maximum 960x240 dot graphics on a-TFT panel
234 displays in 16M colors with dithering.
236 source "drivers/video/fonts/Kconfig"
238 config VIDCONSOLE_AS_LCD
239 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
242 This is a work-around for boards which have 'lcd' or 'vga' in their
243 stdout environment variable, but have moved to use driver model for
244 video. In this case the console will no-longer work. While it is
245 possible to update the environment, the breakage may be confusing for
246 users. This option will be removed around the end of 2020.
248 config VIDCONSOLE_AS_NAME
249 string "Use 'vidconsole' when string defined here is seen in stdout"
250 depends on VIDCONSOLE_AS_LCD
251 default "lcd" if LCD || TEGRA_COMMON
252 default "vga" if !LCD
254 This is a work-around for boards which have 'lcd' or 'vga' in their
255 stdout environment variable, but have moved to use driver model for
256 video. In this case the console will no-longer work. While it is
257 possible to update the environment, the breakage may be confusing for
258 users. This option will be removed around the end of 2020.
260 config VIDEO_COREBOOT
261 bool "Enable coreboot framebuffer driver support"
264 Turn on this option to enable a framebuffer driver when U-Boot is
265 loaded by coreboot where the graphics device is configured by
266 coreboot already. This can in principle be used with any platform
267 that coreboot supports.
270 bool "Enable EFI framebuffer driver support"
271 depends on EFI_STUB || EFI_APP
273 Turn on this option to enable a framebuffeer driver when U-Boot is
274 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
275 the graphics device is configured by the EFI BIOS already. This can
276 in principle be used with any platform that has an EFI BIOS.
279 bool "Enable VESA video driver support"
281 Turn on this option to enable a very simple driver which uses vesa
282 to discover the video mode and then provides a frame buffer for use
283 by U-Boot. This can in principle be used with any platform that
284 supports PCI and video cards that support VESA BIOS Extension (VBE).
286 config FRAMEBUFFER_SET_VESA_MODE
287 bool "Set framebuffer graphics resolution"
288 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
290 Set VESA/native framebuffer mode (needed for bootsplash and graphical
294 prompt "framebuffer graphics resolution"
295 default FRAMEBUFFER_VESA_MODE_118
296 depends on FRAMEBUFFER_SET_VESA_MODE
298 This option sets the resolution used for the U-Boot framebuffer (and
301 config FRAMEBUFFER_VESA_MODE_100
302 bool "640x400 256-color"
304 config FRAMEBUFFER_VESA_MODE_101
305 bool "640x480 256-color"
307 config FRAMEBUFFER_VESA_MODE_102
308 bool "800x600 16-color"
310 config FRAMEBUFFER_VESA_MODE_103
311 bool "800x600 256-color"
313 config FRAMEBUFFER_VESA_MODE_104
314 bool "1024x768 16-color"
316 config FRAMEBUFFER_VESA_MODE_105
317 bool "1024x768 256-color"
319 config FRAMEBUFFER_VESA_MODE_106
320 bool "1280x1024 16-color"
322 config FRAMEBUFFER_VESA_MODE_107
323 bool "1280x1024 256-color"
325 config FRAMEBUFFER_VESA_MODE_108
328 config FRAMEBUFFER_VESA_MODE_109
331 config FRAMEBUFFER_VESA_MODE_10A
334 config FRAMEBUFFER_VESA_MODE_10B
337 config FRAMEBUFFER_VESA_MODE_10C
340 config FRAMEBUFFER_VESA_MODE_10D
341 bool "320x200 32k-color (1:5:5:5)"
343 config FRAMEBUFFER_VESA_MODE_10E
344 bool "320x200 64k-color (5:6:5)"
346 config FRAMEBUFFER_VESA_MODE_10F
347 bool "320x200 16.8M-color (8:8:8)"
349 config FRAMEBUFFER_VESA_MODE_110
350 bool "640x480 32k-color (1:5:5:5)"
352 config FRAMEBUFFER_VESA_MODE_111
353 bool "640x480 64k-color (5:6:5)"
355 config FRAMEBUFFER_VESA_MODE_112
356 bool "640x480 16.8M-color (8:8:8)"
358 config FRAMEBUFFER_VESA_MODE_113
359 bool "800x600 32k-color (1:5:5:5)"
361 config FRAMEBUFFER_VESA_MODE_114
362 bool "800x600 64k-color (5:6:5)"
364 config FRAMEBUFFER_VESA_MODE_115
365 bool "800x600 16.8M-color (8:8:8)"
367 config FRAMEBUFFER_VESA_MODE_116
368 bool "1024x768 32k-color (1:5:5:5)"
370 config FRAMEBUFFER_VESA_MODE_117
371 bool "1024x768 64k-color (5:6:5)"
373 config FRAMEBUFFER_VESA_MODE_118
374 bool "1024x768 16.8M-color (8:8:8)"
376 config FRAMEBUFFER_VESA_MODE_119
377 bool "1280x1024 32k-color (1:5:5:5)"
379 config FRAMEBUFFER_VESA_MODE_11A
380 bool "1280x1024 64k-color (5:6:5)"
382 config FRAMEBUFFER_VESA_MODE_11B
383 bool "1280x1024 16.8M-color (8:8:8)"
385 config FRAMEBUFFER_VESA_MODE_USER
386 bool "Manually select VESA mode"
390 # Map the config names to an integer (KB).
391 config FRAMEBUFFER_VESA_MODE
392 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
394 default 0x100 if FRAMEBUFFER_VESA_MODE_100
395 default 0x101 if FRAMEBUFFER_VESA_MODE_101
396 default 0x102 if FRAMEBUFFER_VESA_MODE_102
397 default 0x103 if FRAMEBUFFER_VESA_MODE_103
398 default 0x104 if FRAMEBUFFER_VESA_MODE_104
399 default 0x105 if FRAMEBUFFER_VESA_MODE_105
400 default 0x106 if FRAMEBUFFER_VESA_MODE_106
401 default 0x107 if FRAMEBUFFER_VESA_MODE_107
402 default 0x108 if FRAMEBUFFER_VESA_MODE_108
403 default 0x109 if FRAMEBUFFER_VESA_MODE_109
404 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
405 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
406 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
407 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
408 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
409 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
410 default 0x110 if FRAMEBUFFER_VESA_MODE_110
411 default 0x111 if FRAMEBUFFER_VESA_MODE_111
412 default 0x112 if FRAMEBUFFER_VESA_MODE_112
413 default 0x113 if FRAMEBUFFER_VESA_MODE_113
414 default 0x114 if FRAMEBUFFER_VESA_MODE_114
415 default 0x115 if FRAMEBUFFER_VESA_MODE_115
416 default 0x116 if FRAMEBUFFER_VESA_MODE_116
417 default 0x117 if FRAMEBUFFER_VESA_MODE_117
418 default 0x118 if FRAMEBUFFER_VESA_MODE_118
419 default 0x119 if FRAMEBUFFER_VESA_MODE_119
420 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
421 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
422 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
424 config VIDEO_LCD_ANX9804
425 bool "ANX9804 bridge chip"
427 Support for the ANX9804 bridge chip, which can take pixel data coming
428 from a parallel LCD interface and translate it on the fy into a DP
429 interface for driving eDP TFT displays. It uses I2C for configuration.
432 bool "Atmel LCD panel support"
433 depends on LCD && ARCH_AT91
435 config ATMEL_LCD_BGR555
436 bool "Display in BGR555 mode"
438 Use the BGR555 output mode. Otherwise RGB565 is used.
441 bool "Display support for BCM2835"
443 The graphics processor already sets up the display so this driver
444 simply checks the resolution and then sets up the frame buffer with
445 that same resolution (or as near as possible) and 32bpp depth, so
446 that U-Boot can access it with full colour depth.
448 config VIDEO_LCD_ORISETECH_OTM8009A
449 bool "OTM8009A DSI LCD panel support"
451 select VIDEO_MIPI_DSI
453 Say Y here if you want to enable support for Orise Technology
454 otm8009a 480x800 dsi 2dl panel.
456 config VIDEO_LCD_RAYDIUM_RM68200
457 bool "RM68200 DSI LCD panel support"
459 select VIDEO_MIPI_DSI
461 Say Y here if you want to enable support for Raydium RM68200
462 720x1280 DSI video mode panel.
464 config VIDEO_LCD_SSD2828
465 bool "SSD2828 bridge chip"
467 Support for the SSD2828 bridge chip, which can take pixel data coming
468 from a parallel LCD interface and translate it on the fly into MIPI DSI
469 interface for driving a MIPI compatible LCD panel. It uses SPI for
472 config VIDEO_LCD_SSD2828_TX_CLK
473 int "SSD2828 TX_CLK frequency (in MHz)"
474 depends on VIDEO_LCD_SSD2828
477 The frequency of the crystal, which is clocking SSD2828. It may be
478 anything in the 8MHz-30MHz range and the exact value should be
479 retrieved from the board schematics. Or in the case of Allwinner
480 hardware, it can be usually found as 'lcd_xtal_freq' variable in
481 FEX files. It can be also set to 0 for selecting PCLK from the
482 parallel LCD interface instead of TX_CLK as the PLL clock source.
484 config VIDEO_LCD_SSD2828_RESET
485 string "RESET pin of SSD2828"
486 depends on VIDEO_LCD_SSD2828
489 The reset pin of SSD2828 chip. This takes a string in the format
490 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
492 config VIDEO_LCD_TDO_TL070WSH30
493 bool "TDO TL070WSH30 DSI LCD panel support"
495 select VIDEO_MIPI_DSI
497 Say Y here if you want to enable support for TDO TL070WSH30
498 1024x600 DSI video mode panel.
500 config VIDEO_LCD_HITACHI_TX18D42VM
501 bool "Hitachi tx18d42vm LVDS LCD panel support"
503 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
504 lcd controller which needs to be initialized over SPI, once that is
505 done they work like a regular LVDS panel.
507 config VIDEO_LCD_SPI_CS
508 string "SPI CS pin for LCD related config job"
509 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
512 This is one of the SPI communication pins, involved in setting up a
513 working LCD configuration. The exact role of SPI may differ for
514 different hardware setups. The option takes a string in the format
515 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
517 config VIDEO_LCD_SPI_SCLK
518 string "SPI SCLK pin for LCD related config job"
519 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
522 This is one of the SPI communication pins, involved in setting up a
523 working LCD configuration. The exact role of SPI may differ for
524 different hardware setups. The option takes a string in the format
525 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
527 config VIDEO_LCD_SPI_MOSI
528 string "SPI MOSI pin for LCD related config job"
529 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
532 This is one of the SPI communication pins, involved in setting up a
533 working LCD configuration. The exact role of SPI may differ for
534 different hardware setups. The option takes a string in the format
535 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
537 config VIDEO_LCD_SPI_MISO
538 string "SPI MISO pin for LCD related config job (optional)"
539 depends on VIDEO_LCD_SSD2828
542 This is one of the SPI communication pins, involved in setting up a
543 working LCD configuration. The exact role of SPI may differ for
544 different hardware setups. If wired up, this pin may provide additional
545 useful functionality. Such as bi-directional communication with the
546 hardware and LCD panel id retrieval (if the panel can report it). The
547 option takes a string in the format understood by 'sunxi_name_to_gpio'
548 function, e.g. PH1 for pin 1 of port H.
550 source "drivers/video/meson/Kconfig"
553 bool "Armada XP LCD controller"
555 Support for the LCD controller integrated in the Marvell
559 bool "Enable OMAP3+ DSS Support"
560 depends on ARCH_OMAP2PLUS
562 This enables the Display subsystem (DSS) on OMAP3+ boards.
565 bool "Enable EDID library"
567 This enables library for accessing EDID data from an LCD panel.
570 bool "Enable Display support"
574 This supports drivers that provide a display, such as eDP (Embedded
575 DisplayPort) and HDMI (High Definition Multimedia Interface).
576 The devices provide a simple interface to start up the display,
577 read display information and enable it.
580 bool "Enable NXP TDA19988 support"
583 This enables support for the NXP TDA19988 HDMI encoder. This encoder
584 will convert RGB data streams into HDMI-encoded signals.
587 bool "Enable ATMEL video support using HLCDC"
589 HLCDC supports video output to an attached LCD panel.
591 source "drivers/video/ti/Kconfig"
593 source "drivers/video/exynos/Kconfig"
595 config LOGICORE_DP_TX
596 bool "Enable Logicore DP TX driver"
599 Enable the driver for the transmitter part of the Xilinx LogiCORE
600 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
601 video interface as defined by VESA DisplayPort v1.2.
603 Note that this is a pure transmitter device, and has no display
604 capabilities by itself.
606 config VIDEO_BROADWELL_IGD
607 bool "Enable Intel Broadwell integrated graphics device"
610 This enables support for integrated graphics on Intel broadwell
611 devices. Initialisation is mostly performed by a VGA boot ROM, with
612 some setup handled by U-Boot itself. The graphics adaptor works as
613 a VESA device and supports LCD panels, eDP and LVDS outputs.
614 Configuration of most aspects of device operation is performed using
615 a special tool which configures the VGA ROM, but the graphics
616 resolution can be selected in U-Boot.
618 config VIDEO_IVYBRIDGE_IGD
619 bool "Enable Intel Ivybridge integration graphics support"
622 This enables support for integrated graphics on Intel ivybridge
623 devices. Initialisation is mostly performed by a VGA boot ROM, with
624 some setup handled by U-Boot itself. The graphics adaptor works as
625 a VESA device and supports LCD panels, eDP and LVDS outputs.
626 Configuration of most aspects of device operation is performed using
627 a special tool which configures the VGA ROM, but the graphics
628 resolution can be selected in U-Boot.
630 source "drivers/video/rockchip/Kconfig"
632 config VIDEO_ARM_MALIDP
633 bool "Enable Arm Mali Display Processor support"
634 depends on DM_VIDEO && OF_CONTROL
637 This enables support for Arm Ltd Mali Display Processors from
638 the DP500, DP550 and DP650 family.
640 config VIDEO_SANDBOX_SDL
641 bool "Enable sandbox video console using SDL"
644 When using sandbox you can enable an emulated LCD display which
645 appears as an SDL (Simple DirectMedia Layer) window. This is a
646 console device and can display stdout output. Within U-Boot is is
647 a normal bitmap display and can display images as well as text.
649 source "drivers/video/stm32/Kconfig"
652 bool "Enable LCD support on Tegra20"
653 depends on OF_CONTROL
655 Tegra20 supports video output to an attached LCD panel as well as
656 other options such as HDMI. Only the LCD is supported in U-Boot.
657 This option enables this support which can be used on devices which
658 have an LCD display connected.
660 config VIDEO_TEGRA124
661 bool "Enable video support on Tegra124"
664 Tegra124 supports many video output options including eDP and
665 HDMI. At present only eDP is supported by U-Boot. This option
666 enables this support which can be used on devices which
667 have an eDP display connected.
669 source "drivers/video/bridge/Kconfig"
671 source "drivers/video/imx/Kconfig"
674 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
677 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
680 bool "Enable video support on Nexell SoC"
681 depends on ARCH_S5P6818 || ARCH_S5P4418
683 Nexell SoC supports many video output options including eDP and
684 HDMI. This option enables this support which can be used on devices
685 which have an eDP display connected.
688 bool "Enable video support for Seps525"
689 depends on DM_VIDEO && DM_GPIO
691 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
692 Currently driver is supporting only SPI interface.
694 config VIDEO_ZYNQMP_DPSUB
695 bool "Enable video support for ZynqMP Display Port"
696 depends on DM_VIDEO && ZYNQMP_POWER_DOMAIN
698 Enable support for Xilinx ZynqMP Display Port. Currently this file
699 is used as placeholder for driver. The main reason is to record
700 compatible string and calling power domain driver.
702 source "drivers/video/nexell/Kconfig"
705 bool "Enable legacy video support"
708 Define this for video support, without using driver model. Some
709 drivers use this because they are not yet converted to driver
710 model. Video drivers typically provide a colour text console and
713 config CONSOLE_SCROLL_LINES
714 int "Number of lines to scroll the console by"
715 depends on DM_VIDEO || LCD
718 When the console need to be scrolled, this is the number of
719 lines to scroll by. It defaults to 1. Increasing this makes the
720 console jump but can help speed up operation when scrolling
724 bool "Enable legacy LCD support"
726 Define this to enable LCD support (for output to LCD display).
727 You will also need to select an LCD driver using an additional
728 CONFIG option. See the README for details. Drives which have been
729 converted to driver model will instead used CONFIG_DM_VIDEO.
734 Enables the common driver code for the Designware HDMI TX
735 block found in SoCs from various vendors.
736 As this does not provide any functionality by itself (but
737 rather requires a SoC-specific glue driver to call it), it
738 can not be enabled from the configuration menu.
740 config VIDEO_DSI_HOST_SANDBOX
741 bool "Enable sandbox for dsi host"
743 select VIDEO_MIPI_DSI
745 Enable support for sandbox dsi host device used for testing
747 Display Serial Interface (DSI) defines a serial bus and
748 a communication protocol between the host and the device
751 config VIDEO_DW_MIPI_DSI
753 select VIDEO_MIPI_DSI
755 Enables the common driver code for the Synopsis Designware
756 MIPI DSI block found in SoCs from various vendors.
757 As this does not provide any functionality by itself (but
758 rather requires a SoC-specific glue driver to call it), it
759 can not be enabled from the configuration menu.
762 bool "Simple display driver for preconfigured display"
764 Enables a simple generic display driver which utilizes the
765 simple-framebuffer devicetree bindings.
767 This driver assumes that the display hardware has been initialized
768 before u-boot starts, and u-boot will simply render to the pre-
769 allocated frame buffer surface.
771 config VIDEO_DT_SIMPLEFB
772 bool "Enable SimpleFB support for passing framebuffer to OS"
774 Enables the code to pass the framebuffer to the kernel as a
775 simple framebuffer in the device tree.
776 The video output is initialized by U-Boot, and kept by the
779 config VIDEO_MCDE_SIMPLE
780 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
783 Enables a simple display driver for ST-Ericsson MCDE
784 (Multichannel Display Engine), which reads the configuration from
787 This driver assumes that the display hardware has been initialized
788 before u-boot starts, and u-boot will simply render to the pre-
789 allocated frame buffer surface.
792 bool "Enable OSD support"
795 This supports drivers that provide a OSD (on-screen display), which
796 is a (usually text-oriented) graphics buffer to show information on
800 bool "Enable sandbox OSD"
803 Enable support for sandbox OSD device used for testing purposes.
806 bool "Enable IHS video out driver"
809 Enable support for the gdsys Integrated Hardware Systems (IHS) video
810 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
811 textual overlays of the display outputs.
814 bool "Show a splash-screen image"
816 If this option is set, the environment is checked for a variable
817 "splashimage". If found, the usual display of logo, copyright and
818 system information on the LCD is suppressed and the BMP image at the
819 address specified in "splashimage" is loaded instead. The console is
820 redirected to the "nulldev", too. This allows for a "silent" boot
821 where a splash screen is loaded very quickly after power-on.
823 The splash_screen_prepare() function is a weak function defined in
824 common/splash.c. It is called as part of the splash screen display
825 sequence. It gives the board an opportunity to prepare the splash
826 image data before it is processed and sent to the frame buffer by
827 U-Boot. Define your own version to use this feature.
831 config SPLASHIMAGE_GUARD
832 bool "Support unaligned BMP images"
834 If this option is set, then U-Boot will prevent the environment
835 variable "splashimage" from being set to a problematic address
836 (see doc/README.displaying-bmps).
838 This option is useful for targets where, due to alignment
839 restrictions, an improperly aligned BMP image will cause a data
840 abort. If you think you will not have problems with unaligned
841 accesses (for example because your toolchain prevents them)
842 there is no need to set this option.
844 config SPLASH_SCREEN_ALIGN
845 bool "Allow positioning the splash image anywhere on the display"
847 If this option is set the splash image can be freely positioned
848 on the screen. Environment variable "splashpos" specifies the
849 position as "x,y". If a positive number is given it is used as
850 number of pixel from left/top. If a negative number is given it
851 is used as number of pixel from right/bottom. You can also
852 specify 'm' for centering the image.
856 => image at center of screen
858 setenv splashpos 30,20
859 => image at x = 30 and y = 20
861 setenv splashpos -10,m
862 => vertically centered image
863 at x = dspWidth - bmpWidth - 9
865 config HIDE_LOGO_VERSION
866 bool "Hide the version information on the splash screen"
868 Normally the U-Boot version string is shown on the display when the
869 splash screen is enabled. This information is not otherwise visible
870 since video starts up after U-Boot has displayed the initial banner.
872 Enable this option to hide this information.
875 bool "Control the source of the splash image"
877 Use the splash_source.c library. This library provides facilities to
878 declare board specific splash image locations, routines for loading
879 splash image from supported locations, and a way of controlling the
880 selected splash location using the "splashsource" environment
883 This CONFIG works as follows:
885 - If splashsource is set to a supported location name as defined by
886 board code, use that splash location.
887 - If splashsource is undefined, use the first splash location as
889 - If splashsource is set to an unsupported value, do not load a splash
892 A splash source location can describe either storage with raw data, a
893 storage formatted with a file system or a FIT image. In case of a
894 filesystem, the splash screen data is loaded as a file. The name of
895 the splash screen file can be controlled with the environment variable
898 To enable loading the splash image from a FIT image, CONFIG_FIT must
899 be enabled. The FIT image has to start at the 'offset' field address
900 in the selected splash location. The name of splash image within the
901 FIT shall be specified by the environment variable "splashfile".
903 In case the environment variable "splashfile" is not defined the
904 default name 'splash.bmp' will be used.
906 endif # SPLASH_SCREEN
908 config VIDEO_BMP_GZIP
909 bool "Gzip compressed BMP image support"
910 depends on CMD_BMP || SPLASH_SCREEN
912 If this option is set, additionally to standard BMP
913 images, gzipped BMP images can be displayed via the
914 splashscreen support or the bmp command.
916 config VIDEO_LOGO_MAX_SIZE
917 hex "Maximum size of the bitmap logo in bytes"
920 Sets the maximum uncompressed size of the logo. This is needed when
921 decompressing a BMP file using the gzip algorithm, since it cannot
922 read the size from the bitmap header.
924 config VIDEO_BMP_RLE8
925 bool "Run length encoded BMP image (RLE8) support"
928 If this option is set, the 8-bit RLE compressed BMP images
932 bool "16-bit-per-pixel BMP image support"
933 depends on DM_VIDEO || LCD
935 Support display of bitmaps file with 16-bit-per-pixel
938 bool "24-bit-per-pixel BMP image support"
939 depends on DM_VIDEO || LCD
941 Support display of bitmaps file with 24-bit-per-pixel.
944 bool "32-bit-per-pixel BMP image support"
945 depends on DM_VIDEO || LCD
947 Support display of bitmaps file with 32-bit-per-pixel.