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.
34 config VIDEO_FONT_SUN12X22
35 bool "12 x 22 font size"
37 Font for video console driver, 12 x 22 pixels
38 Provides character bitmap data in header file.
39 When selecting multiple fonts, you may want to enable CMD_SELECT_FONT too.
41 config VIDEO_FONT_16X32
42 bool "16 x 32 font size"
44 Font for video console driver, 16 x 32 pixels
45 Provides character bitmap data in header file.
46 When selecting multiple fonts, you may want to enable CMD_SELECT_FONT too.
49 bool "Show the U-Boot logo on the display"
50 default y if !SPLASH_SCREEN
53 This enables showing the U-Boot logo on the display when a video
54 device is probed. It appears at the top right. The logo itself is at
55 tools/logos/u-boot_logo.bmp and looks best when the display has a
59 bool "Enable panel backlight uclass support"
62 This provides backlight uclass driver that enables basic panel
65 config VIDEO_PCI_DEFAULT_FB_SIZE
66 hex "Default framebuffer size to use if no drivers request it"
67 default 0x1000000 if X86 && PCI
68 default 0 if !(X86 && PCI)
70 Generally, video drivers request the amount of memory they need for
71 the frame buffer when they are bound, by setting the size field in
72 struct video_uc_plat. That memory is then reserved for use after
73 relocation. But PCI drivers cannot be bound before relocation unless
74 they are mentioned in the devicetree.
76 With this value set appropriately, it is possible for PCI video
77 devices to have a framebuffer allocated by U-Boot.
79 Note: the framebuffer needs to be large enough to store all pixels at
80 maximum resolution. For example, at 1920 x 1200 with 32 bits per
81 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed.
84 bool "Enable copying the frame buffer to a hardware copy"
86 On some machines (e.g. x86), reading from the frame buffer is very
87 slow because it is uncached. To improve performance, this feature
88 allows the frame buffer to be kept in cached memory (allocated by
89 U-Boot) and then copied to the hardware frame-buffer as needed.
91 To use this, your video driver must set @copy_base in
95 bool "Generic PWM based Backlight Driver"
96 depends on BACKLIGHT && DM_PWM
99 If you have a LCD backlight adjustable by PWM, say Y to enable
101 This driver can be use with "simple-panel" and
102 it understands the standard device tree
103 (leds/backlight/pwm-backlight.txt)
105 config BACKLIGHT_GPIO
106 bool "Generic GPIO based Backlight Driver"
109 If you have a LCD backlight adjustable by GPIO, say Y to enable
111 This driver can be used with "simple-panel" and
112 it understands the standard device tree
113 (leds/backlight/gpio-backlight.txt)
116 bool "Support 8-bit-per-pixel displays"
119 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
120 Enabling this will include code to support this display. Without
121 this option, such displays will not be supported and console output
125 bool "Support 16-bit-per-pixel displays"
128 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
129 Enabling this will include code to support this display. Without
130 this option, such displays will not be supported and console output
134 bool "Support 32-bit-per-pixel displays"
137 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
138 Enabling this will include code to support this display. Without
139 this option, such displays will not be supported and console output
143 bool "Support ANSI escape sequences in video console"
144 default y if EFI_LOADER
146 Enable ANSI escape sequence decoding for a more fully functional
147 console. Functionality includes changing the text colour and moving
148 the cursor. These date from the 1970s and are still widely used today
149 to control a text terminal. U-Boot implements these by decoding the
150 sequences and performing the appropriate operation.
152 config VIDEO_MIPI_DSI
153 bool "Support MIPI DSI interface"
155 Support MIPI DSI interface for driving a MIPI compatible device.
156 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
157 serial interface between a host processor and a display module.
159 config CONSOLE_NORMAL
160 bool "Support a simple text console"
163 Support drawing text on the frame buffer console so that it can be
164 used as a console. Rotation is not supported by this driver (see
165 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
168 config CONSOLE_ROTATION
169 bool "Support rotated displays"
171 Sometimes, for example if the display is mounted in portrait
172 mode or even if it's mounted landscape but rotated by 180degree,
173 we need to rotate our content of the display relative to the
174 framebuffer, so that user can read the messages which are
175 printed out. Enable this option to include a text driver which can
176 support this. The rotation is set by the 'rot' parameter in
177 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
178 degrees, 3=270 degrees.
180 config CONSOLE_TRUETYPE
181 bool "Support a console that uses TrueType fonts"
182 select CMD_SELECT_FONT
184 TrueTrype fonts can provide outline-drawing capability rather than
185 needing to provide a bitmap for each font and size that is needed.
186 With this option you can adjust the text size and use a variety of
187 fonts. Note that this is noticeably slower than with normal console.
189 config CONSOLE_TRUETYPE_SIZE
190 int "TrueType font size"
191 depends on CONSOLE_TRUETYPE
194 This sets the font size for the console. The size is measured in
195 pixels and is the nominal height of a character. Note that fonts
196 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
197 However that measurement depends on the size of your display and
198 there is no standard display density. At present there is not a
199 method to select the display's physical size, which would allow
200 U-Boot to calculate the correct font size.
202 config CONSOLE_TRUETYPE_MAX_METRICS
203 int "TrueType maximum number of font / size combinations"
204 depends on CONSOLE_TRUETYPE
208 This sets the number of font / size combinations which can be used by
209 the console. For simple console use a single font is enough. When
210 boot menus are in use, this may need to be increased.
212 Note that a separate entry is needed for each font size, even if the
213 font itself is the same. This is because the entry caches various
214 font metrics which are expensive to regenerate each time the font
217 config SYS_WHITE_ON_BLACK
218 bool "Display console as white on a black background"
219 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
221 Normally the display is black on a white background, Enable this
222 option to invert this, i.e. white on a black background. This can be
223 better in low-light situations or to reduce eye strain in some
227 bool "Skip framebuffer clear"
229 If firmware (whatever loads u-boot) has already put a splash image
230 on screen, you might want to preserve it until whatever u-boot
231 loads takes over the screen. This, for example, can be used to
232 keep splash image on screen until grub graphical boot menu starts.
235 bool "Enable panel uclass support"
238 This provides panel uclass driver that enables basic panel support.
241 bool "Enable simple panel support"
242 depends on PANEL && BACKLIGHT && DM_GPIO
245 This turns on a simple panel driver that enables a compatible
249 bool "Enable Himax HX-8238D LCD driver"
252 Support for HX-8238D LCD Panel
253 The HX8238-D is a single chip controller and driver LSI that
254 integrates the power circuit.
255 It can drive a maximum 960x240 dot graphics on a-TFT panel
256 displays in 16M colors with dithering.
258 source "drivers/video/fonts/Kconfig"
260 config VIDCONSOLE_AS_LCD
261 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout"
263 This is a work-around for boards which have 'lcd' or 'vga' in their
264 stdout environment variable, but have moved to use driver model for
265 video. In this case the console will no-longer work. While it is
266 possible to update the environment, the breakage may be confusing for
267 users. This option will be removed around the end of 2020.
269 config VIDCONSOLE_AS_NAME
270 string "Use 'vidconsole' when string defined here is seen in stdout"
271 depends on VIDCONSOLE_AS_LCD
272 default "lcd" if LCD || TEGRA_COMMON
273 default "vga" if !LCD
275 This is a work-around for boards which have 'lcd' or 'vga' in their
276 stdout environment variable, but have moved to use driver model for
277 video. In this case the console will no-longer work. While it is
278 possible to update the environment, the breakage may be confusing for
279 users. This option will be removed around the end of 2020.
281 config VIDEO_COREBOOT
282 bool "Enable coreboot framebuffer driver support"
285 Turn on this option to enable a framebuffer driver when U-Boot is
286 loaded by coreboot where the graphics device is configured by
287 coreboot already. This can in principle be used with any platform
288 that coreboot supports.
291 bool "Enable EFI framebuffer driver support"
292 depends on EFI_STUB || EFI_APP
294 Turn on this option to enable a framebuffeer driver when U-Boot is
295 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
296 the graphics device is configured by the EFI BIOS already. This can
297 in principle be used with any platform that has an EFI BIOS.
300 bool "Enable VESA video driver support"
302 Turn on this option to enable a very simple driver which uses vesa
303 to discover the video mode and then provides a frame buffer for use
304 by U-Boot. This can in principle be used with any platform that
305 supports PCI and video cards that support VESA BIOS Extension (VBE).
307 config FRAMEBUFFER_SET_VESA_MODE
308 bool "Set framebuffer graphics resolution"
309 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
311 Set VESA/native framebuffer mode (needed for bootsplash and graphical
315 prompt "framebuffer graphics resolution"
316 default FRAMEBUFFER_VESA_MODE_118
317 depends on FRAMEBUFFER_SET_VESA_MODE
319 This option sets the resolution used for the U-Boot framebuffer (and
322 config FRAMEBUFFER_VESA_MODE_100
323 bool "640x400 256-color"
325 config FRAMEBUFFER_VESA_MODE_101
326 bool "640x480 256-color"
328 config FRAMEBUFFER_VESA_MODE_102
329 bool "800x600 16-color"
331 config FRAMEBUFFER_VESA_MODE_103
332 bool "800x600 256-color"
334 config FRAMEBUFFER_VESA_MODE_104
335 bool "1024x768 16-color"
337 config FRAMEBUFFER_VESA_MODE_105
338 bool "1024x768 256-color"
340 config FRAMEBUFFER_VESA_MODE_106
341 bool "1280x1024 16-color"
343 config FRAMEBUFFER_VESA_MODE_107
344 bool "1280x1024 256-color"
346 config FRAMEBUFFER_VESA_MODE_108
349 config FRAMEBUFFER_VESA_MODE_109
352 config FRAMEBUFFER_VESA_MODE_10A
355 config FRAMEBUFFER_VESA_MODE_10B
358 config FRAMEBUFFER_VESA_MODE_10C
361 config FRAMEBUFFER_VESA_MODE_10D
362 bool "320x200 32k-color (1:5:5:5)"
364 config FRAMEBUFFER_VESA_MODE_10E
365 bool "320x200 64k-color (5:6:5)"
367 config FRAMEBUFFER_VESA_MODE_10F
368 bool "320x200 16.8M-color (8:8:8)"
370 config FRAMEBUFFER_VESA_MODE_110
371 bool "640x480 32k-color (1:5:5:5)"
373 config FRAMEBUFFER_VESA_MODE_111
374 bool "640x480 64k-color (5:6:5)"
376 config FRAMEBUFFER_VESA_MODE_112
377 bool "640x480 16.8M-color (8:8:8)"
379 config FRAMEBUFFER_VESA_MODE_113
380 bool "800x600 32k-color (1:5:5:5)"
382 config FRAMEBUFFER_VESA_MODE_114
383 bool "800x600 64k-color (5:6:5)"
385 config FRAMEBUFFER_VESA_MODE_115
386 bool "800x600 16.8M-color (8:8:8)"
388 config FRAMEBUFFER_VESA_MODE_116
389 bool "1024x768 32k-color (1:5:5:5)"
391 config FRAMEBUFFER_VESA_MODE_117
392 bool "1024x768 64k-color (5:6:5)"
394 config FRAMEBUFFER_VESA_MODE_118
395 bool "1024x768 16.8M-color (8:8:8)"
397 config FRAMEBUFFER_VESA_MODE_119
398 bool "1280x1024 32k-color (1:5:5:5)"
400 config FRAMEBUFFER_VESA_MODE_11A
401 bool "1280x1024 64k-color (5:6:5)"
403 config FRAMEBUFFER_VESA_MODE_11B
404 bool "1280x1024 16.8M-color (8:8:8)"
406 config FRAMEBUFFER_VESA_MODE_USER
407 bool "Manually select VESA mode"
411 # Map the config names to an integer (KB).
412 config FRAMEBUFFER_VESA_MODE
413 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
415 default 0x100 if FRAMEBUFFER_VESA_MODE_100
416 default 0x101 if FRAMEBUFFER_VESA_MODE_101
417 default 0x102 if FRAMEBUFFER_VESA_MODE_102
418 default 0x103 if FRAMEBUFFER_VESA_MODE_103
419 default 0x104 if FRAMEBUFFER_VESA_MODE_104
420 default 0x105 if FRAMEBUFFER_VESA_MODE_105
421 default 0x106 if FRAMEBUFFER_VESA_MODE_106
422 default 0x107 if FRAMEBUFFER_VESA_MODE_107
423 default 0x108 if FRAMEBUFFER_VESA_MODE_108
424 default 0x109 if FRAMEBUFFER_VESA_MODE_109
425 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
426 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
427 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
428 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
429 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
430 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
431 default 0x110 if FRAMEBUFFER_VESA_MODE_110
432 default 0x111 if FRAMEBUFFER_VESA_MODE_111
433 default 0x112 if FRAMEBUFFER_VESA_MODE_112
434 default 0x113 if FRAMEBUFFER_VESA_MODE_113
435 default 0x114 if FRAMEBUFFER_VESA_MODE_114
436 default 0x115 if FRAMEBUFFER_VESA_MODE_115
437 default 0x116 if FRAMEBUFFER_VESA_MODE_116
438 default 0x117 if FRAMEBUFFER_VESA_MODE_117
439 default 0x118 if FRAMEBUFFER_VESA_MODE_118
440 default 0x119 if FRAMEBUFFER_VESA_MODE_119
441 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
442 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
443 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
445 config VIDEO_LCD_ANX9804
446 bool "ANX9804 bridge chip"
448 Support for the ANX9804 bridge chip, which can take pixel data coming
449 from a parallel LCD interface and translate it on the fy into a DP
450 interface for driving eDP TFT displays. It uses I2C for configuration.
453 bool "Atmel LCD panel support"
456 config ATMEL_LCD_BGR555
457 bool "Display in BGR555 mode"
459 Use the BGR555 output mode. Otherwise RGB565 is used.
462 bool "Display support for BCM2835"
464 The graphics processor already sets up the display so this driver
465 simply checks the resolution and then sets up the frame buffer with
466 that same resolution (or as near as possible) and 32bpp depth, so
467 that U-Boot can access it with full colour depth.
469 config VIDEO_LCD_ORISETECH_OTM8009A
470 bool "OTM8009A DSI LCD panel support"
471 select VIDEO_MIPI_DSI
473 Say Y here if you want to enable support for Orise Technology
474 otm8009a 480x800 dsi 2dl panel.
476 config VIDEO_LCD_RAYDIUM_RM68200
477 bool "RM68200 DSI LCD panel support"
478 select VIDEO_MIPI_DSI
480 Say Y here if you want to enable support for Raydium RM68200
481 720x1280 DSI video mode panel.
483 config VIDEO_LCD_SSD2828
484 bool "SSD2828 bridge chip"
486 Support for the SSD2828 bridge chip, which can take pixel data coming
487 from a parallel LCD interface and translate it on the fly into MIPI DSI
488 interface for driving a MIPI compatible LCD panel. It uses SPI for
491 config VIDEO_LCD_SSD2828_TX_CLK
492 int "SSD2828 TX_CLK frequency (in MHz)"
493 depends on VIDEO_LCD_SSD2828
496 The frequency of the crystal, which is clocking SSD2828. It may be
497 anything in the 8MHz-30MHz range and the exact value should be
498 retrieved from the board schematics. Or in the case of Allwinner
499 hardware, it can be usually found as 'lcd_xtal_freq' variable in
500 FEX files. It can be also set to 0 for selecting PCLK from the
501 parallel LCD interface instead of TX_CLK as the PLL clock source.
503 config VIDEO_LCD_SSD2828_RESET
504 string "RESET pin of SSD2828"
505 depends on VIDEO_LCD_SSD2828
508 The reset pin of SSD2828 chip. This takes a string in the format
509 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
511 config VIDEO_LCD_TDO_TL070WSH30
512 bool "TDO TL070WSH30 DSI LCD panel support"
513 select VIDEO_MIPI_DSI
515 Say Y here if you want to enable support for TDO TL070WSH30
516 1024x600 DSI video mode panel.
518 config VIDEO_LCD_HITACHI_TX18D42VM
519 bool "Hitachi tx18d42vm LVDS LCD panel support"
521 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
522 lcd controller which needs to be initialized over SPI, once that is
523 done they work like a regular LVDS panel.
525 config VIDEO_LCD_SPI_CS
526 string "SPI CS pin for LCD related config job"
527 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
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. The option takes a string in the format
533 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
535 config VIDEO_LCD_SPI_SCLK
536 string "SPI SCLK pin for LCD related config job"
537 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
540 This is one of the SPI communication pins, involved in setting up a
541 working LCD configuration. The exact role of SPI may differ for
542 different hardware setups. The option takes a string in the format
543 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
545 config VIDEO_LCD_SPI_MOSI
546 string "SPI MOSI pin for LCD related config job"
547 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
550 This is one of the SPI communication pins, involved in setting up a
551 working LCD configuration. The exact role of SPI may differ for
552 different hardware setups. The option takes a string in the format
553 understood by 'sunxi_name_to_gpio' function, e.g. PH1 for pin 1 of port H.
555 config VIDEO_LCD_SPI_MISO
556 string "SPI MISO pin for LCD related config job (optional)"
557 depends on VIDEO_LCD_SSD2828
560 This is one of the SPI communication pins, involved in setting up a
561 working LCD configuration. The exact role of SPI may differ for
562 different hardware setups. If wired up, this pin may provide additional
563 useful functionality. Such as bi-directional communication with the
564 hardware and LCD panel id retrieval (if the panel can report it). The
565 option takes a string in the format understood by 'sunxi_name_to_gpio'
566 function, e.g. PH1 for pin 1 of port H.
568 source "drivers/video/meson/Kconfig"
571 bool "Armada XP LCD controller"
573 Support for the LCD controller integrated in the Marvell
577 bool "Enable OMAP3+ DSS Support"
578 depends on ARCH_OMAP2PLUS
580 This enables the Display subsystem (DSS) on OMAP3+ boards.
583 bool "Enable EDID library"
585 This enables library for accessing EDID data from an LCD panel.
588 bool "Enable Display support"
592 This supports drivers that provide a display, such as eDP (Embedded
593 DisplayPort) and HDMI (High Definition Multimedia Interface).
594 The devices provide a simple interface to start up the display,
595 read display information and enable it.
598 bool "Enable NXP TDA19988 support"
601 This enables support for the NXP TDA19988 HDMI encoder. This encoder
602 will convert RGB data streams into HDMI-encoded signals.
605 bool "Enable ATMEL video support using HLCDC"
607 HLCDC supports video output to an attached LCD panel.
609 source "drivers/video/ti/Kconfig"
611 source "drivers/video/exynos/Kconfig"
613 config LOGICORE_DP_TX
614 bool "Enable Logicore DP TX driver"
617 Enable the driver for the transmitter part of the Xilinx LogiCORE
618 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
619 video interface as defined by VESA DisplayPort v1.2.
621 Note that this is a pure transmitter device, and has no display
622 capabilities by itself.
624 config VIDEO_BROADWELL_IGD
625 bool "Enable Intel Broadwell integrated graphics device"
628 This enables support for integrated graphics on Intel broadwell
629 devices. Initialisation is mostly performed by a VGA boot ROM, with
630 some setup handled by U-Boot itself. The graphics adaptor works as
631 a VESA device and supports LCD panels, eDP and LVDS outputs.
632 Configuration of most aspects of device operation is performed using
633 a special tool which configures the VGA ROM, but the graphics
634 resolution can be selected in U-Boot.
636 config VIDEO_IVYBRIDGE_IGD
637 bool "Enable Intel Ivybridge integration graphics support"
640 This enables support for integrated graphics on Intel ivybridge
641 devices. Initialisation is mostly performed by a VGA boot ROM, with
642 some setup handled by U-Boot itself. The graphics adaptor works as
643 a VESA device and supports LCD panels, eDP and LVDS outputs.
644 Configuration of most aspects of device operation is performed using
645 a special tool which configures the VGA ROM, but the graphics
646 resolution can be selected in U-Boot.
648 source "drivers/video/rockchip/Kconfig"
650 config VIDEO_ARM_MALIDP
651 bool "Enable Arm Mali Display Processor support"
652 depends on OF_CONTROL
655 This enables support for Arm Ltd Mali Display Processors from
656 the DP500, DP550 and DP650 family.
658 config VIDEO_SANDBOX_SDL
659 bool "Enable sandbox video console using SDL"
660 depends on SANDBOX_SDL
662 When using sandbox you can enable an emulated LCD display which
663 appears as an SDL (Simple DirectMedia Layer) window. This is a
664 console device and can display stdout output. Within U-Boot is is
665 a normal bitmap display and can display images as well as text.
667 source "drivers/video/stm32/Kconfig"
669 source "drivers/video/tidss/Kconfig"
671 config VIDEO_TEGRA124
672 bool "Enable video support on Tegra124"
674 Tegra124 supports many video output options including eDP and
675 HDMI. At present only eDP is supported by U-Boot. This option
676 enables this support which can be used on devices which
677 have an eDP display connected.
679 source "drivers/video/bridge/Kconfig"
681 source "drivers/video/tegra20/Kconfig"
683 source "drivers/video/imx/Kconfig"
686 bool "Enable video support on i.MX28/i.MX6UL/i.MX7 SoCs"
688 Enable framebuffer driver for i.MX28/i.MX6UL/i.MX7 processors
691 bool "Enable video support on Nexell SoC"
692 depends on ARCH_S5P6818 || ARCH_S5P4418
694 Nexell SoC supports many video output options including eDP and
695 HDMI. This option enables this support which can be used on devices
696 which have an eDP display connected.
699 bool "Enable video support for Seps525"
702 Enable support for the Syncoam PM-OLED display driver (RGB 160x128).
703 Currently driver is supporting only SPI interface.
705 config VIDEO_ZYNQMP_DPSUB
706 bool "Enable video support for ZynqMP Display Port"
707 depends on ZYNQMP_POWER_DOMAIN
709 Enable support for Xilinx ZynqMP Display Port. Currently this file
710 is used as placeholder for driver. The main reason is to record
711 compatible string and calling power domain driver.
713 source "drivers/video/nexell/Kconfig"
715 config CONSOLE_SCROLL_LINES
716 int "Number of lines to scroll the console by"
719 When the console need to be scrolled, this is the number of
720 lines to scroll by. It defaults to 1. Increasing this makes the
721 console jump but can help speed up operation when scrolling
727 Enables the common driver code for the Designware HDMI TX
728 block found in SoCs from various vendors.
729 As this does not provide any functionality by itself (but
730 rather requires a SoC-specific glue driver to call it), it
731 can not be enabled from the configuration menu.
733 config VIDEO_DSI_HOST_SANDBOX
734 bool "Enable sandbox for dsi host"
736 select VIDEO_MIPI_DSI
738 Enable support for sandbox dsi host device used for testing
740 Display Serial Interface (DSI) defines a serial bus and
741 a communication protocol between the host and the device
744 config VIDEO_DW_MIPI_DSI
746 select VIDEO_MIPI_DSI
748 Enables the common driver code for the Synopsis Designware
749 MIPI DSI block found in SoCs from various vendors.
750 As this does not provide any functionality by itself (but
751 rather requires a SoC-specific glue driver to call it), it
752 can not be enabled from the configuration menu.
755 bool "Simple display driver for preconfigured display"
757 Enables a simple generic display driver which utilizes the
758 simple-framebuffer devicetree bindings.
760 This driver assumes that the display hardware has been initialized
761 before u-boot starts, and u-boot will simply render to the pre-
762 allocated frame buffer surface.
764 config VIDEO_DT_SIMPLEFB
765 bool "Enable SimpleFB support for passing framebuffer to OS"
767 Enables the code to pass the framebuffer to the kernel as a
768 simple framebuffer in the device tree.
769 The video output is initialized by U-Boot, and kept by the
772 config VIDEO_MCDE_SIMPLE
773 bool "Simple driver for ST-Ericsson MCDE with preconfigured display"
775 Enables a simple display driver for ST-Ericsson MCDE
776 (Multichannel Display Engine), which reads the configuration from
779 This driver assumes that the display hardware has been initialized
780 before u-boot starts, and u-boot will simply render to the pre-
781 allocated frame buffer surface.
784 bool "Enable OSD support"
787 This supports drivers that provide a OSD (on-screen display), which
788 is a (usually text-oriented) graphics buffer to show information on
792 bool "Enable sandbox OSD"
795 Enable support for sandbox OSD device used for testing purposes.
798 bool "Enable IHS video out driver"
801 Enable support for the gdsys Integrated Hardware Systems (IHS) video
802 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
803 textual overlays of the display outputs.
806 bool "Show a splash-screen image"
808 If this option is set, the environment is checked for a variable
809 "splashimage". If found, the usual display of logo, copyright and
810 system information on the LCD is suppressed and the BMP image at the
811 address specified in "splashimage" is loaded instead. The console is
812 redirected to the "nulldev", too. This allows for a "silent" boot
813 where a splash screen is loaded very quickly after power-on.
815 The splash_screen_prepare() function is a weak function defined in
816 common/splash.c. It is called as part of the splash screen display
817 sequence. It gives the board an opportunity to prepare the splash
818 image data before it is processed and sent to the frame buffer by
819 U-Boot. Define your own version to use this feature.
823 config SPLASH_SCREEN_ALIGN
824 bool "Allow positioning the splash image anywhere on the display"
826 If this option is set the splash image can be freely positioned
827 on the screen. Environment variable "splashpos" specifies the
828 position as "x,y". If a positive number is given it is used as
829 number of pixel from left/top. If a negative number is given it
830 is used as number of pixel from right/bottom. You can also
831 specify 'm' for centering the image.
835 => image at center of screen
837 setenv splashpos 30,20
838 => image at x = 30 and y = 20
840 setenv splashpos -10,m
841 => vertically centered image
842 at x = dspWidth - bmpWidth - 9
844 config HIDE_LOGO_VERSION
845 bool "Hide the version information on the splash screen"
847 Normally the U-Boot version string is shown on the display when the
848 splash screen is enabled. This information is not otherwise visible
849 since video starts up after U-Boot has displayed the initial banner.
851 Enable this option to hide this information.
854 bool "Control the source of the splash image"
856 Use the splash_source.c library. This library provides facilities to
857 declare board specific splash image locations, routines for loading
858 splash image from supported locations, and a way of controlling the
859 selected splash location using the "splashsource" environment
862 This CONFIG works as follows:
864 - If splashsource is set to a supported location name as defined by
865 board code, use that splash location.
866 - If splashsource is undefined, use the first splash location as
868 - If splashsource is set to an unsupported value, do not load a splash
871 A splash source location can describe either storage with raw data, a
872 storage formatted with a file system or a FIT image. In case of a
873 filesystem, the splash screen data is loaded as a file. The name of
874 the splash screen file can be controlled with the environment variable
877 To enable loading the splash image from a FIT image, CONFIG_FIT must
878 be enabled. The FIT image has to start at the 'offset' field address
879 in the selected splash location. The name of splash image within the
880 FIT shall be specified by the environment variable "splashfile".
882 In case the environment variable "splashfile" is not defined the
883 default name 'splash.bmp' will be used.
885 endif # SPLASH_SCREEN
887 config VIDEO_BMP_GZIP
888 bool "Gzip compressed BMP image support"
889 depends on CMD_BMP || SPLASH_SCREEN
891 If this option is set, additionally to standard BMP
892 images, gzipped BMP images can be displayed via the
893 splashscreen support or the bmp command.
895 config VIDEO_LOGO_MAX_SIZE
896 hex "Maximum size of the bitmap logo in bytes"
899 Sets the maximum uncompressed size of the logo. This is needed when
900 decompressing a BMP file using the gzip algorithm, since it cannot
901 read the size from the bitmap header.
903 config VIDEO_BMP_RLE8
904 bool "Run length encoded BMP image (RLE8) support"
906 If this option is set, the 8-bit RLE compressed BMP images
910 bool "16-bit-per-pixel BMP image support"
912 Support display of bitmaps file with 16-bit-per-pixel
915 bool "24-bit-per-pixel BMP image support"
917 Support display of bitmaps file with 24-bit-per-pixel.
920 bool "32-bit-per-pixel BMP image support"
922 Support display of bitmaps file with 32-bit-per-pixel.