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 "Show the U-Boot logo on the display"
21 default y if !SPLASH_SCREEN
24 This enables showing the U-Boot logo on the display when a video
25 device is probed. It appears at the top right. The logo itself is at
26 tools/logos/u-boot_logo.bmp and looks best when the display has a
30 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"
38 default 0x1000000 if X86 && PCI
39 default 0 if !(X86 && PCI)
41 Generally, video drivers request the amount of memory they need for
42 the frame buffer when they are bound, by setting the size field in
43 struct video_uc_plat. That memory is then reserved for use after
44 relocation. But PCI drivers cannot be bound before relocation unless
45 they are mentioned in the devicetree.
47 With this value set appropriately, it is possible for PCI video
48 devices to have a framebuffer allocated by U-Boot.
50 Note: the framebuffer needs to be large enough to store all pixels at
51 maximum resolution. For example, at 1920 x 1200 with 32 bits per
52 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
55 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 "Support 8-bit-per-pixel displays"
90 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
91 Enabling this will include code to support this display. Without
92 this option, such displays will not be supported and console output
96 bool "Support 16-bit-per-pixel displays"
99 Support drawing text and bitmaps onto a 16-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 32-bit-per-pixel displays"
108 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
109 Enabling this will include code to support this display. Without
110 this option, such displays will not be supported and console output
114 bool "Support ANSI escape sequences in video console"
115 default y if EFI_LOADER
117 Enable ANSI escape sequence decoding for a more fully functional
118 console. Functionality includes changing the text colour and moving
119 the cursor. These date from the 1970s and are still widely used today
120 to control a text terminal. U-Boot implements these by decoding the
121 sequences and performing the appropriate operation.
123 config VIDEO_MIPI_DSI
124 bool "Support MIPI DSI interface"
126 Support MIPI DSI interface for driving a MIPI compatible device.
127 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
128 serial interface between a host processor and a display module.
130 config CONSOLE_NORMAL
131 bool "Support a simple text console"
134 Support drawing text on the frame buffer console so that it can be
135 used as a console. Rotation is not supported by this driver (see
136 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
139 config CONSOLE_ROTATION
140 bool "Support rotated displays"
142 Sometimes, for example if the display is mounted in portrait
143 mode or even if it's mounted landscape but rotated by 180degree,
144 we need to rotate our content of the display relative to the
145 framebuffer, so that user can read the messages which are
146 printed out. Enable this option to include a text driver which can
147 support this. The rotation is set by the 'rot' parameter in
148 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
149 degrees, 3=270 degrees.
151 config CONSOLE_TRUETYPE
152 bool "Support a console that uses TrueType fonts"
154 TrueTrype fonts can provide outline-drawing capability rather than
155 needing to provide a bitmap for each font and size that is needed.
156 With this option you can adjust the text size and use a variety of
157 fonts. Note that this is noticeably slower than with normal console.
159 config CONSOLE_TRUETYPE_SIZE
160 int "TrueType font size"
161 depends on CONSOLE_TRUETYPE
164 This sets the font size for the console. The size is measured in
165 pixels and is the nominal height of a character. Note that fonts
166 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
167 However that measurement depends on the size of your display and
168 there is no standard display density. At present there is not a
169 method to select the display's physical size, which would allow
170 U-Boot to calculate the correct font size.
172 config CONSOLE_TRUETYPE_MAX_METRICS
173 int "TrueType maximum number of font / size combinations"
174 depends on CONSOLE_TRUETYPE
178 This sets the number of font / size combinations which can be used by
179 the console. For simple console use a single font is enough. When
180 boot menus are in use, this may need to be increased.
182 Note that a separate entry is needed for each font size, even if the
183 font itself is the same. This is because the entry caches various
184 font metrics which are expensive to regenerate each time the font
187 config SYS_WHITE_ON_BLACK
188 bool "Display console as white on a black background"
189 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
191 Normally the display is black on a white background, Enable this
192 option to invert this, i.e. white on a black background. This can be
193 better in low-light situations or to reduce eye strain in some
197 bool "Skip framebuffer clear"
199 If firmware (whatever loads u-boot) has already put a splash image
200 on screen, you might want to preserve it until whatever u-boot
201 loads takes over the screen. This, for example, can be used to
202 keep splash image on screen until grub graphical boot menu starts.
205 bool "Enable panel uclass support"
208 This provides panel uclass driver that enables basic panel support.
211 bool "Enable simple panel support"
212 depends on PANEL && BACKLIGHT && DM_GPIO
215 This turns on a simple panel driver that enables a compatible
219 bool "Enable Himax HX-8238D LCD driver"
222 Support for HX-8238D LCD Panel
223 The HX8238-D is a single chip controller and driver LSI that
224 integrates the power circuit.
225 It can drive a maximum 960x240 dot graphics on a-TFT panel
226 displays in 16M colors with dithering.
228 source "drivers/video/fonts/Kconfig"
230 config VIDCONSOLE_AS_LCD
231 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.
423 bool "Atmel LCD panel support"
426 config ATMEL_LCD_BGR555
427 bool "Display in BGR555 mode"
429 Use the BGR555 output mode. Otherwise RGB565 is used.
432 bool "Display support for BCM2835"
434 The graphics processor already sets up the display so this driver
435 simply checks the resolution and then sets up the frame buffer with
436 that same resolution (or as near as possible) and 32bpp depth, so
437 that U-Boot can access it with full colour depth.
439 config VIDEO_LCD_ORISETECH_OTM8009A
440 bool "OTM8009A DSI LCD panel support"
441 select VIDEO_MIPI_DSI
443 Say Y here if you want to enable support for Orise Technology
444 otm8009a 480x800 dsi 2dl panel.
446 config VIDEO_LCD_RAYDIUM_RM68200
447 bool "RM68200 DSI LCD panel support"
448 select VIDEO_MIPI_DSI
450 Say Y here if you want to enable support for Raydium RM68200
451 720x1280 DSI video mode panel.
453 config VIDEO_LCD_SSD2828
454 bool "SSD2828 bridge chip"
456 Support for the SSD2828 bridge chip, which can take pixel data coming
457 from a parallel LCD interface and translate it on the fly into MIPI DSI
458 interface for driving a MIPI compatible LCD panel. It uses SPI for
461 config VIDEO_LCD_SSD2828_TX_CLK
462 int "SSD2828 TX_CLK frequency (in MHz)"
463 depends on VIDEO_LCD_SSD2828
466 The frequency of the crystal, which is clocking SSD2828. It may be
467 anything in the 8MHz-30MHz range and the exact value should be
468 retrieved from the board schematics. Or in the case of Allwinner
469 hardware, it can be usually found as 'lcd_xtal_freq' variable in
470 FEX files. It can be also set to 0 for selecting PCLK from the
471 parallel LCD interface instead of TX_CLK as the PLL clock source.
473 config VIDEO_LCD_SSD2828_RESET
474 string "RESET pin of SSD2828"
475 depends on VIDEO_LCD_SSD2828
478 The reset pin of SSD2828 chip. This takes a string in the format
479 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
481 config VIDEO_LCD_TDO_TL070WSH30
482 bool "TDO TL070WSH30 DSI LCD panel support"
483 select VIDEO_MIPI_DSI
485 Say Y here if you want to enable support for TDO TL070WSH30
486 1024x600 DSI video mode panel.
488 config VIDEO_LCD_HITACHI_TX18D42VM
489 bool "Hitachi tx18d42vm LVDS LCD panel support"
491 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
492 lcd controller which needs to be initialized over SPI, once that is
493 done they work like a regular LVDS panel.
495 config VIDEO_LCD_SPI_CS
496 string "SPI CS pin for LCD related config job"
497 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
500 This is one of the SPI communication pins, involved in setting up a
501 working LCD configuration. The exact role of SPI may differ for
502 different hardware setups. The option takes a string in the format
503 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
505 config VIDEO_LCD_SPI_SCLK
506 string "SPI SCLK pin for LCD related config job"
507 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
510 This is one of the SPI communication pins, involved in setting up a
511 working LCD configuration. The exact role of SPI may differ for
512 different hardware setups. The option takes a string in the format
513 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
515 config VIDEO_LCD_SPI_MOSI
516 string "SPI MOSI pin for LCD related config job"
517 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
520 This is one of the SPI communication pins, involved in setting up a
521 working LCD configuration. The exact role of SPI may differ for
522 different hardware setups. The option takes a string in the format
523 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
525 config VIDEO_LCD_SPI_MISO
526 string "SPI MISO pin for LCD related config job (optional)"
527 depends on VIDEO_LCD_SSD2828
530 This is one of the SPI communication pins, involved in setting up a
531 working LCD configuration. The exact role of SPI may differ for
532 different hardware setups. If wired up, this pin may provide additional
533 useful functionality. Such as bi-directional communication with the
534 hardware and LCD panel id retrieval (if the panel can report it). The
535 option takes a string in the format understood by 'sunxi_name_to_gpio'
536 function, e.g. PH1 for pin 1 of port H.
538 source "drivers/video/meson/Kconfig"
541 bool "Armada XP LCD controller"
543 Support for the LCD controller integrated in the Marvell
547 bool "Enable OMAP3+ DSS Support"
548 depends on ARCH_OMAP2PLUS
550 This enables the Display subsystem (DSS) on OMAP3+ boards.
553 bool "Enable EDID library"
555 This enables library for accessing EDID data from an LCD panel.
558 bool "Enable Display support"
562 This supports drivers that provide a display, such as eDP (Embedded
563 DisplayPort) and HDMI (High Definition Multimedia Interface).
564 The devices provide a simple interface to start up the display,
565 read display information and enable it.
568 bool "Enable NXP TDA19988 support"
571 This enables support for the NXP TDA19988 HDMI encoder. This encoder
572 will convert RGB data streams into HDMI-encoded signals.
575 bool "Enable ATMEL video support using HLCDC"
577 HLCDC supports video output to an attached LCD panel.
579 source "drivers/video/ti/Kconfig"
581 source "drivers/video/exynos/Kconfig"
583 config LOGICORE_DP_TX
584 bool "Enable Logicore DP TX driver"
587 Enable the driver for the transmitter part of the Xilinx LogiCORE
588 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
589 video interface as defined by VESA DisplayPort v1.2.
591 Note that this is a pure transmitter device, and has no display
592 capabilities by itself.
594 config VIDEO_BROADWELL_IGD
595 bool "Enable Intel Broadwell integrated graphics device"
598 This enables support for integrated graphics on Intel broadwell
599 devices. Initialisation is mostly performed by a VGA boot ROM, with
600 some setup handled by U-Boot itself. The graphics adaptor works as
601 a VESA device and supports LCD panels, eDP and LVDS outputs.
602 Configuration of most aspects of device operation is performed using
603 a special tool which configures the VGA ROM, but the graphics
604 resolution can be selected in U-Boot.
606 config VIDEO_IVYBRIDGE_IGD
607 bool "Enable Intel Ivybridge integration graphics support"
610 This enables support for integrated graphics on Intel ivybridge
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 source "drivers/video/rockchip/Kconfig"
620 config VIDEO_ARM_MALIDP
621 bool "Enable Arm Mali Display Processor support"
622 depends on OF_CONTROL
625 This enables support for Arm Ltd Mali Display Processors from
626 the DP500, DP550 and DP650 family.
628 config VIDEO_SANDBOX_SDL
629 bool "Enable sandbox video console using SDL"
630 depends on SANDBOX_SDL
632 When using sandbox you can enable an emulated LCD display which
633 appears as an SDL (Simple DirectMedia Layer) window. This is a
634 console device and can display stdout output. Within U-Boot is is
635 a normal bitmap display and can display images as well as text.
637 source "drivers/video/stm32/Kconfig"
639 source "drivers/video/tidss/Kconfig"
642 bool "Enable LCD support on Tegra20"
643 depends on OF_CONTROL
645 Tegra20 supports video output to an attached LCD panel as well as
646 other options such as HDMI. Only the LCD is supported in U-Boot.
647 This option enables this support which can be used on devices which
648 have an LCD display connected.
650 config VIDEO_TEGRA124
651 bool "Enable video support on Tegra124"
653 Tegra124 supports many video output options including eDP and
654 HDMI. At present only eDP is supported by U-Boot. This option
655 enables this support which can be used on devices which
656 have an eDP display connected.
658 source "drivers/video/bridge/Kconfig"
660 source "drivers/video/imx/Kconfig"
663 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
665 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
668 bool "Enable video support on Nexell SoC"
669 depends on ARCH_S5P6818 || ARCH_S5P4418
671 Nexell SoC supports many video output options including eDP and
672 HDMI. This option enables this support which can be used on devices
673 which have an eDP display connected.
676 bool "Enable video support for Seps525"
679 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
680 Currently driver is supporting only SPI interface.
682 config VIDEO_ZYNQMP_DPSUB
683 bool "Enable video support for ZynqMP Display Port"
684 depends on ZYNQMP_POWER_DOMAIN
686 Enable support for Xilinx ZynqMP Display Port. Currently this file
687 is used as placeholder for driver. The main reason is to record
688 compatible string and calling power domain driver.
690 source "drivers/video/nexell/Kconfig"
692 config CONSOLE_SCROLL_LINES
693 int "Number of lines to scroll the console by"
696 When the console need to be scrolled, this is the number of
697 lines to scroll by. It defaults to 1. Increasing this makes the
698 console jump but can help speed up operation when scrolling
704 Enables the common driver code for the Designware HDMI TX
705 block found in SoCs from various vendors.
706 As this does not provide any functionality by itself (but
707 rather requires a SoC-specific glue driver to call it), it
708 can not be enabled from the configuration menu.
710 config VIDEO_DSI_HOST_SANDBOX
711 bool "Enable sandbox for dsi host"
713 select VIDEO_MIPI_DSI
715 Enable support for sandbox dsi host device used for testing
717 Display Serial Interface (DSI) defines a serial bus and
718 a communication protocol between the host and the device
721 config VIDEO_DW_MIPI_DSI
723 select VIDEO_MIPI_DSI
725 Enables the common driver code for the Synopsis Designware
726 MIPI DSI block found in SoCs from various vendors.
727 As this does not provide any functionality by itself (but
728 rather requires a SoC-specific glue driver to call it), it
729 can not be enabled from the configuration menu.
732 bool "Simple display driver for preconfigured display"
734 Enables a simple generic display driver which utilizes the
735 simple-framebuffer devicetree bindings.
737 This driver assumes that the display hardware has been initialized
738 before u-boot starts, and u-boot will simply render to the pre-
739 allocated frame buffer surface.
741 config VIDEO_DT_SIMPLEFB
742 bool "Enable SimpleFB support for passing framebuffer to OS"
744 Enables the code to pass the framebuffer to the kernel as a
745 simple framebuffer in the device tree.
746 The video output is initialized by U-Boot, and kept by the
749 config VIDEO_MCDE_SIMPLE
750 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
752 Enables a simple display driver for ST-Ericsson MCDE
753 (Multichannel Display Engine), which reads the configuration from
756 This driver assumes that the display hardware has been initialized
757 before u-boot starts, and u-boot will simply render to the pre-
758 allocated frame buffer surface.
761 bool "Enable OSD support"
764 This supports drivers that provide a OSD (on-screen display), which
765 is a (usually text-oriented) graphics buffer to show information on
769 bool "Enable sandbox OSD"
772 Enable support for sandbox OSD device used for testing purposes.
775 bool "Enable IHS video out driver"
778 Enable support for the gdsys Integrated Hardware Systems (IHS) video
779 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
780 textual overlays of the display outputs.
783 bool "Show a splash-screen image"
785 If this option is set, the environment is checked for a variable
786 "splashimage". If found, the usual display of logo, copyright and
787 system information on the LCD is suppressed and the BMP image at the
788 address specified in "splashimage" is loaded instead. The console is
789 redirected to the "nulldev", too. This allows for a "silent" boot
790 where a splash screen is loaded very quickly after power-on.
792 The splash_screen_prepare() function is a weak function defined in
793 common/splash.c. It is called as part of the splash screen display
794 sequence. It gives the board an opportunity to prepare the splash
795 image data before it is processed and sent to the frame buffer by
796 U-Boot. Define your own version to use this feature.
800 config SPLASH_SCREEN_ALIGN
801 bool "Allow positioning the splash image anywhere on the display"
803 If this option is set the splash image can be freely positioned
804 on the screen. Environment variable "splashpos" specifies the
805 position as "x,y". If a positive number is given it is used as
806 number of pixel from left/top. If a negative number is given it
807 is used as number of pixel from right/bottom. You can also
808 specify 'm' for centering the image.
812 => image at center of screen
814 setenv splashpos 30,20
815 => image at x = 30 and y = 20
817 setenv splashpos -10,m
818 => vertically centered image
819 at x = dspWidth - bmpWidth - 9
821 config HIDE_LOGO_VERSION
822 bool "Hide the version information on the splash screen"
824 Normally the U-Boot version string is shown on the display when the
825 splash screen is enabled. This information is not otherwise visible
826 since video starts up after U-Boot has displayed the initial banner.
828 Enable this option to hide this information.
831 bool "Control the source of the splash image"
833 Use the splash_source.c library. This library provides facilities to
834 declare board specific splash image locations, routines for loading
835 splash image from supported locations, and a way of controlling the
836 selected splash location using the "splashsource" environment
839 This CONFIG works as follows:
841 - If splashsource is set to a supported location name as defined by
842 board code, use that splash location.
843 - If splashsource is undefined, use the first splash location as
845 - If splashsource is set to an unsupported value, do not load a splash
848 A splash source location can describe either storage with raw data, a
849 storage formatted with a file system or a FIT image. In case of a
850 filesystem, the splash screen data is loaded as a file. The name of
851 the splash screen file can be controlled with the environment variable
854 To enable loading the splash image from a FIT image, CONFIG_FIT must
855 be enabled. The FIT image has to start at the 'offset' field address
856 in the selected splash location. The name of splash image within the
857 FIT shall be specified by the environment variable "splashfile".
859 In case the environment variable "splashfile" is not defined the
860 default name 'splash.bmp' will be used.
862 endif # SPLASH_SCREEN
864 config VIDEO_BMP_GZIP
865 bool "Gzip compressed BMP image support"
866 depends on CMD_BMP || SPLASH_SCREEN
868 If this option is set, additionally to standard BMP
869 images, gzipped BMP images can be displayed via the
870 splashscreen support or the bmp command.
872 config VIDEO_LOGO_MAX_SIZE
873 hex "Maximum size of the bitmap logo in bytes"
876 Sets the maximum uncompressed size of the logo. This is needed when
877 decompressing a BMP file using the gzip algorithm, since it cannot
878 read the size from the bitmap header.
880 config VIDEO_BMP_RLE8
881 bool "Run length encoded BMP image (RLE8) support"
883 If this option is set, the 8-bit RLE compressed BMP images
887 bool "16-bit-per-pixel BMP image support"
889 Support display of bitmaps file with 16-bit-per-pixel
892 bool "24-bit-per-pixel BMP image support"
894 Support display of bitmaps file with 24-bit-per-pixel.
897 bool "32-bit-per-pixel BMP image support"
899 Support display of bitmaps file with 32-bit-per-pixel.