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 "Enable panel backlight uclass support"
22 This provides backlight uclass driver that enables basic panel
26 bool "Generic PWM based Backlight Driver"
27 depends on BACKLIGHT && DM_PWM
30 If you have a LCD backlight adjustable by PWM, say Y to enable
32 This driver can be use with "simple-panel" and
33 it understands the standard device tree
34 (leds/backlight/pwm-backlight.txt)
37 bool "Generic GPIO based Backlight Driver"
40 If you have a LCD backlight adjustable by GPIO, say Y to enable
42 This driver can be used with "simple-panel" and
43 it understands the standard device tree
44 (leds/backlight/gpio-backlight.txt)
47 bool "Enable vidconsole commands lcdputs and setcurs"
51 Enabling this will provide 'setcurs' and 'lcdputs' commands which
52 support cursor positioning and drawing strings on video framebuffer.
55 bool "Support 8-bit-per-pixel displays"
59 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
60 Enabling this will include code to support this display. Without
61 this option, such displays will not be supported and console output
65 bool "Support 16-bit-per-pixel displays"
69 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
70 Enabling this will include code to support this display. Without
71 this option, such displays will not be supported and console output
75 bool "Support 32-bit-per-pixel displays"
79 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
80 Enabling this will include code to support this display. Without
81 this option, such displays will not be supported and console output
85 bool "Support ANSI escape sequences in video console"
89 Enable ANSI escape sequence decoding for a more fully functional
93 bool "Support MIPI DSI interface"
96 Support MIPI DSI interface for driving a MIPI compatible device.
97 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed
98 serial interface between a host processor and a display module.
100 config CONSOLE_NORMAL
101 bool "Support a simple text console"
103 default y if DM_VIDEO
105 Support drawing text on the frame buffer console so that it can be
106 used as a console. Rotation is not supported by this driver (see
107 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
110 config CONSOLE_ROTATION
111 bool "Support rotated displays"
114 Sometimes, for example if the display is mounted in portrait
115 mode or even if it's mounted landscape but rotated by 180degree,
116 we need to rotate our content of the display relative to the
117 framebuffer, so that user can read the messages which are
118 printed out. Enable this option to include a text driver which can
119 support this. The rotation is set by the 'rot' parameter in
120 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
121 degrees, 3=270 degrees.
123 config CONSOLE_TRUETYPE
124 bool "Support a console that uses TrueType fonts"
127 TrueTrype fonts can provide outline-drawing capability rather than
128 needing to provide a bitmap for each font and size that is needed.
129 With this option you can adjust the text size and use a variety of
130 fonts. Note that this is noticeably slower than with normal console.
132 config CONSOLE_TRUETYPE_SIZE
133 int "TrueType font size"
134 depends on CONSOLE_TRUETYPE
137 This sets the font size for the console. The size is measured in
138 pixels and is the nominal height of a character. Note that fonts
139 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
140 However that measurement depends on the size of your display and
141 there is no standard display density. At present there is not a
142 method to select the display's physical size, which would allow
143 U-Boot to calculate the correct font size.
145 config SYS_WHITE_ON_BLACK
146 bool "Display console as white on a black background"
147 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI
149 Normally the display is black on a white background, Enable this
150 option to invert this, i.e. white on a black background. This can be
151 better in low-light situations or to reduce eye strain in some
155 bool "Skip framebuffer clear"
157 If firmware (whatever loads u-boot) has already put a splash image
158 on screen, you might want to preserve it until whatever u-boot
159 loads takes over the screen. This, for example, can be used to
160 keep splash image on screen until grub graphical boot menu starts.
163 bool "Enable panel uclass support"
167 This provides panel uclass driver that enables basic panel support.
170 bool "Enable simple panel support"
174 This turns on a simple panel driver that enables a compatible
177 source "drivers/video/fonts/Kconfig"
179 config VIDCONSOLE_AS_LCD
180 string "Use 'vidconsole' when string defined here is seen in stdout"
182 default "lcd" if LCD || TEGRA_COMMON
183 default "vga" if !LCD
185 This is a work-around for boards which have 'lcd' or 'vga' in their
186 stdout environment variable, but have moved to use driver model for
187 video. In this case the console will no-longer work. While it is
188 possible to update the environment, the breakage may be confusing for
189 users. This option will be removed around the end of 2020.
191 config VIDEO_COREBOOT
192 bool "Enable coreboot framebuffer driver support"
193 depends on X86 && SYS_COREBOOT
195 Turn on this option to enable a framebuffer driver when U-Boot is
196 loaded by coreboot where the graphics device is configured by
197 coreboot already. This can in principle be used with any platform
198 that coreboot supports.
201 bool "Enable EFI framebuffer driver support"
204 Turn on this option to enable a framebuffeer driver when U-Boot is
205 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where
206 the graphics device is configured by the EFI BIOS already. This can
207 in principle be used with any platform that has an EFI BIOS.
210 bool "Enable VESA video driver support"
213 Turn on this option to enable a very simple driver which uses vesa
214 to discover the video mode and then provides a frame buffer for use
215 by U-Boot. This can in principle be used with any platform that
216 supports PCI and video cards that support VESA BIOS Extension (VBE).
218 config FRAMEBUFFER_SET_VESA_MODE
219 bool "Set framebuffer graphics resolution"
220 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
222 Set VESA/native framebuffer mode (needed for bootsplash and graphical
226 prompt "framebuffer graphics resolution"
227 default FRAMEBUFFER_VESA_MODE_118
228 depends on FRAMEBUFFER_SET_VESA_MODE
230 This option sets the resolution used for the U-Boot framebuffer (and
233 config FRAMEBUFFER_VESA_MODE_100
234 bool "640x400 256-color"
236 config FRAMEBUFFER_VESA_MODE_101
237 bool "640x480 256-color"
239 config FRAMEBUFFER_VESA_MODE_102
240 bool "800x600 16-color"
242 config FRAMEBUFFER_VESA_MODE_103
243 bool "800x600 256-color"
245 config FRAMEBUFFER_VESA_MODE_104
246 bool "1024x768 16-color"
248 config FRAMEBUFFER_VESA_MODE_105
249 bool "1024x768 256-color"
251 config FRAMEBUFFER_VESA_MODE_106
252 bool "1280x1024 16-color"
254 config FRAMEBUFFER_VESA_MODE_107
255 bool "1280x1024 256-color"
257 config FRAMEBUFFER_VESA_MODE_108
260 config FRAMEBUFFER_VESA_MODE_109
263 config FRAMEBUFFER_VESA_MODE_10A
266 config FRAMEBUFFER_VESA_MODE_10B
269 config FRAMEBUFFER_VESA_MODE_10C
272 config FRAMEBUFFER_VESA_MODE_10D
273 bool "320x200 32k-color (1:5:5:5)"
275 config FRAMEBUFFER_VESA_MODE_10E
276 bool "320x200 64k-color (5:6:5)"
278 config FRAMEBUFFER_VESA_MODE_10F
279 bool "320x200 16.8M-color (8:8:8)"
281 config FRAMEBUFFER_VESA_MODE_110
282 bool "640x480 32k-color (1:5:5:5)"
284 config FRAMEBUFFER_VESA_MODE_111
285 bool "640x480 64k-color (5:6:5)"
287 config FRAMEBUFFER_VESA_MODE_112
288 bool "640x480 16.8M-color (8:8:8)"
290 config FRAMEBUFFER_VESA_MODE_113
291 bool "800x600 32k-color (1:5:5:5)"
293 config FRAMEBUFFER_VESA_MODE_114
294 bool "800x600 64k-color (5:6:5)"
296 config FRAMEBUFFER_VESA_MODE_115
297 bool "800x600 16.8M-color (8:8:8)"
299 config FRAMEBUFFER_VESA_MODE_116
300 bool "1024x768 32k-color (1:5:5:5)"
302 config FRAMEBUFFER_VESA_MODE_117
303 bool "1024x768 64k-color (5:6:5)"
305 config FRAMEBUFFER_VESA_MODE_118
306 bool "1024x768 16.8M-color (8:8:8)"
308 config FRAMEBUFFER_VESA_MODE_119
309 bool "1280x1024 32k-color (1:5:5:5)"
311 config FRAMEBUFFER_VESA_MODE_11A
312 bool "1280x1024 64k-color (5:6:5)"
314 config FRAMEBUFFER_VESA_MODE_11B
315 bool "1280x1024 16.8M-color (8:8:8)"
317 config FRAMEBUFFER_VESA_MODE_USER
318 bool "Manually select VESA mode"
322 # Map the config names to an integer (KB).
323 config FRAMEBUFFER_VESA_MODE
324 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
326 default 0x100 if FRAMEBUFFER_VESA_MODE_100
327 default 0x101 if FRAMEBUFFER_VESA_MODE_101
328 default 0x102 if FRAMEBUFFER_VESA_MODE_102
329 default 0x103 if FRAMEBUFFER_VESA_MODE_103
330 default 0x104 if FRAMEBUFFER_VESA_MODE_104
331 default 0x105 if FRAMEBUFFER_VESA_MODE_105
332 default 0x106 if FRAMEBUFFER_VESA_MODE_106
333 default 0x107 if FRAMEBUFFER_VESA_MODE_107
334 default 0x108 if FRAMEBUFFER_VESA_MODE_108
335 default 0x109 if FRAMEBUFFER_VESA_MODE_109
336 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
337 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
338 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
339 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
340 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
341 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
342 default 0x110 if FRAMEBUFFER_VESA_MODE_110
343 default 0x111 if FRAMEBUFFER_VESA_MODE_111
344 default 0x112 if FRAMEBUFFER_VESA_MODE_112
345 default 0x113 if FRAMEBUFFER_VESA_MODE_113
346 default 0x114 if FRAMEBUFFER_VESA_MODE_114
347 default 0x115 if FRAMEBUFFER_VESA_MODE_115
348 default 0x116 if FRAMEBUFFER_VESA_MODE_116
349 default 0x117 if FRAMEBUFFER_VESA_MODE_117
350 default 0x118 if FRAMEBUFFER_VESA_MODE_118
351 default 0x119 if FRAMEBUFFER_VESA_MODE_119
352 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
353 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
354 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
356 config VIDEO_LCD_ANX9804
357 bool "ANX9804 bridge chip"
360 Support for the ANX9804 bridge chip, which can take pixel data coming
361 from a parallel LCD interface and translate it on the fy into a DP
362 interface for driving eDP TFT displays. It uses I2C for configuration.
364 config VIDEO_LCD_ORISETECH_OTM8009A
365 bool "OTM8009A DSI LCD panel support"
367 select VIDEO_MIPI_DSI
370 Say Y here if you want to enable support for Orise Technology
371 otm8009a 480x800 dsi 2dl panel.
373 config VIDEO_LCD_RAYDIUM_RM68200
374 bool "RM68200 DSI LCD panel support"
376 select VIDEO_MIPI_DSI
379 Say Y here if you want to enable support for Raydium RM68200
380 720x1280 DSI video mode panel.
382 config VIDEO_LCD_SSD2828
383 bool "SSD2828 bridge chip"
386 Support for the SSD2828 bridge chip, which can take pixel data coming
387 from a parallel LCD interface and translate it on the fly into MIPI DSI
388 interface for driving a MIPI compatible LCD panel. It uses SPI for
391 config VIDEO_LCD_SSD2828_TX_CLK
392 int "SSD2828 TX_CLK frequency (in MHz)"
393 depends on VIDEO_LCD_SSD2828
396 The frequency of the crystal, which is clocking SSD2828. It may be
397 anything in the 8MHz-30MHz range and the exact value should be
398 retrieved from the board schematics. Or in the case of Allwinner
399 hardware, it can be usually found as 'lcd_xtal_freq' variable in
400 FEX files. It can be also set to 0 for selecting PCLK from the
401 parallel LCD interface instead of TX_CLK as the PLL clock source.
403 config VIDEO_LCD_SSD2828_RESET
404 string "RESET pin of SSD2828"
405 depends on VIDEO_LCD_SSD2828
408 The reset pin of SSD2828 chip. This takes a string in the format
409 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
411 config VIDEO_LCD_HITACHI_TX18D42VM
412 bool "Hitachi tx18d42vm LVDS LCD panel support"
416 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
417 lcd controller which needs to be initialized over SPI, once that is
418 done they work like a regular LVDS panel.
420 config VIDEO_LCD_SPI_CS
421 string "SPI CS pin for LCD related config job"
422 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
425 This is one of the SPI communication pins, involved in setting up a
426 working LCD configuration. The exact role of SPI may differ for
427 different hardware setups. The option takes a string in the format
428 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
430 config VIDEO_LCD_SPI_SCLK
431 string "SPI SCLK pin for LCD related config job"
432 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
435 This is one of the SPI communication pins, involved in setting up a
436 working LCD configuration. The exact role of SPI may differ for
437 different hardware setups. The option takes a string in the format
438 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
440 config VIDEO_LCD_SPI_MOSI
441 string "SPI MOSI pin for LCD related config job"
442 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
445 This is one of the SPI communication pins, involved in setting up a
446 working LCD configuration. The exact role of SPI may differ for
447 different hardware setups. The option takes a string in the format
448 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
450 config VIDEO_LCD_SPI_MISO
451 string "SPI MISO pin for LCD related config job (optional)"
452 depends on VIDEO_LCD_SSD2828
455 This is one of the SPI communication pins, involved in setting up a
456 working LCD configuration. The exact role of SPI may differ for
457 different hardware setups. If wired up, this pin may provide additional
458 useful functionality. Such as bi-directional communication with the
459 hardware and LCD panel id retrieval (if the panel can report it). The
460 option takes a string in the format understood by 'name_to_gpio'
461 function, e.g. PH1 for pin 1 of port H.
463 source "drivers/video/meson/Kconfig"
466 bool "Armada XP LCD controller"
469 Support for the LCD controller integrated in the Marvell
473 bool "Enable OMAP3+ DSS Support"
474 depends on ARCH_OMAP2PLUS
476 This enables the Display subsystem (DSS) on OMAP3+ boards.
479 bool "Enable EDID library"
482 This enables library for accessing EDID data from an LCD panel.
485 bool "Enable Display support"
490 This supports drivers that provide a display, such as eDP (Embedded
491 DisplayPort) and HDMI (High Definition Multimedia Interface).
492 The devices provide a simple interface to start up the display,
493 read display information and enable it.
496 bool "Enable NXP TDA19988 support"
500 This enables support for the NXP TDA19988 HDMI encoder. This encoder
501 will convert RGB data streams into HDMI-encoded signals.
504 bool "Enable ATMEL video support using HLCDC"
507 HLCDC supports video output to an attached LCD panel.
510 bool "Enable AM335x video support"
512 Supports video output to an attached LCD panel.
514 config LOGICORE_DP_TX
515 bool "Enable Logicore DP TX driver"
518 Enable the driver for the transmitter part of the Xilinx LogiCORE
519 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort
520 video interface as defined by VESA DisplayPort v1.2.
522 Note that this is a pure transmitter device, and has no display
523 capabilities by itself.
525 config VIDEO_BROADWELL_IGD
526 bool "Enable Intel Broadwell integrated graphics device"
529 This enables support for integrated graphics on Intel broadwell
530 devices. Initialisation is mostly performed by a VGA boot ROM, with
531 some setup handled by U-Boot itself. The graphics adaptor works as
532 a VESA device and supports LCD panels, eDP and LVDS outputs.
533 Configuration of most aspects of device operation is performed using
534 a special tool which configures the VGA ROM, but the graphics
535 resolution can be selected in U-Boot.
537 config VIDEO_IVYBRIDGE_IGD
538 bool "Enable Intel Ivybridge integration graphics support"
541 This enables support for integrated graphics on Intel ivybridge
542 devices. Initialisation is mostly performed by a VGA boot ROM, with
543 some setup handled by U-Boot itself. The graphics adaptor works as
544 a VESA device and supports LCD panels, eDP and LVDS outputs.
545 Configuration of most aspects of device operation is performed using
546 a special tool which configures the VGA ROM, but the graphics
547 resolution can be selected in U-Boot.
549 config VIDEO_FSL_DCU_FB
550 bool "Enable Freescale Display Control Unit"
551 depends on VIDEO || DM_VIDEO
553 This enables support for Freescale Display Control Unit (DCU4)
554 module found on Freescale Vybrid and QorIQ family of SoCs.
556 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
557 int "Freescale DCU framebuffer size"
558 depends on VIDEO_FSL_DCU_FB
561 Set maximum framebuffer size to be used for Freescale Display
562 Controller Unit (DCU4).
564 source "drivers/video/rockchip/Kconfig"
566 config VIDEO_ARM_MALIDP
567 bool "Enable Arm Mali Display Processor support"
568 depends on DM_VIDEO && OF_CONTROL
571 This enables support for Arm Ltd Mali Display Processors from
572 the DP500, DP550 and DP650 family.
574 config VIDEO_SANDBOX_SDL
575 bool "Enable sandbox video console using SDL"
578 When using sandbox you can enable an emulated LCD display which
579 appears as an SDL (Simple DirectMedia Layer) window. This is a
580 console device and can display stdout output. Within U-Boot is is
581 a normal bitmap display and can display images as well as text.
583 source "drivers/video/stm32/Kconfig"
586 bool "Enable LCD support on Tegra20"
587 depends on OF_CONTROL
589 Tegra20 supports video output to an attached LCD panel as well as
590 other options such as HDMI. Only the LCD is supported in U-Boot.
591 This option enables this support which can be used on devices which
592 have an LCD display connected.
594 config VIDEO_TEGRA124
595 bool "Enable video support on Tegra124"
598 Tegra124 supports many video output options including eDP and
599 HDMI. At present only eDP is supported by U-Boot. This option
600 enables this support which can be used on devices which
601 have an eDP display connected.
603 source "drivers/video/bridge/Kconfig"
605 source "drivers/video/imx/Kconfig"
608 bool "Enable legacy video support"
611 Define this for video support, without using driver model. Some
612 drivers use this because they are not yet converted to driver
613 model. Video drivers typically provide a colour text console and
617 bool "Enable colour frame buffer console"
621 Enables the colour frame buffer driver. This supports colour
622 output on a bitmap display from an in-memory frame buffer.
623 Several colour devices are supported along with various options to
624 adjust the supported features. The driver is implemented in
627 The following defines are needed (cf. smiLynxEM, i8042)
628 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
630 VIDEO_HW_RECTFILL graphic chip supports
631 rectangle fill (cf. smiLynxEM)
632 VIDEO_HW_BITBLT graphic chip supports
633 bit-blit (cf. smiLynxEM)
634 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
635 VIDEO_VISIBLE_ROWS visible pixel rows
636 VIDEO_PIXEL_SIZE bytes per pixel
637 VIDEO_DATA_FORMAT graphic data format
638 (0-5, cf. cfb_console.c)
639 VIDEO_FB_ADRS framebuffer address
640 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
641 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
642 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
643 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
644 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
645 for logo. Requires CONFIG_VIDEO_LOGO
646 CONFIG_CONSOLE_EXTRA_INFO
647 additional board info beside
649 CONFIG_HIDE_LOGO_VERSION
650 do not display bootloader
653 When CONFIG_CFB_CONSOLE is defined, the video console is the
654 default console. The serial console can be forced by setting the
655 environment 'console=serial'.
657 config CFB_CONSOLE_ANSI
658 bool "Support ANSI escape sequences"
659 depends on CFB_CONSOLE
661 This allows the colour buffer frame buffer driver to support
662 a limited number of ANSI escape sequences (cursor control,
663 erase functions and limited graphics rendition control). Normal
664 output from U-Boot will pass through this filter.
666 config VGA_AS_SINGLE_DEVICE
667 bool "Set the video as an output-only device"
668 depends on CFB_CONSOLE
671 If enable the framebuffer device will be initialized as an
672 output-only device. The Keyboard driver will not be set up. This
673 may be used if you have no keyboard device, or more than one
674 (USB Keyboard, AT Keyboard).
676 config VIDEO_SW_CURSOR
677 bool "Enable a software cursor"
678 depends on CFB_CONSOLE
679 default y if CFB_CONSOLE
681 This draws a cursor after the last character. No blinking is
682 provided. This makes it possible to see the current cursor
683 position when entering text on the console. It is recommended to
686 config CONSOLE_EXTRA_INFO
687 bool "Display additional board information"
688 depends on CFB_CONSOLE
690 Display additional board information strings that normally go to
691 the serial port. When this option is enabled, a board-specific
692 function video_get_info_str() is called to get the string for
693 each line of the display. The function should return the string,
694 which can be empty if there is nothing to display for that line.
696 config CONSOLE_SCROLL_LINES
697 int "Number of lines to scroll the console by"
698 depends on CFB_CONSOLE || DM_VIDEO || LCD
701 When the console need to be scrolled, this is the number of
702 lines to scroll by. It defaults to 1. Increasing this makes the
703 console jump but can help speed up operation when scrolling
706 config SYS_CONSOLE_BG_COL
707 hex "Background colour"
708 depends on CFB_CONSOLE
711 Defines the background colour for the console. The value is from
712 0x00 to 0xff and the meaning depends on the graphics card.
713 Typically, 0x00 means black and 0xff means white. Do not set
714 the background and foreground to the same colour or you will see
717 config SYS_CONSOLE_FG_COL
718 hex "Foreground colour"
719 depends on CFB_CONSOLE
722 Defines the foreground colour for the console. The value is from
723 0x00 to 0xff and the meaning depends on the graphics card.
724 Typically, 0x00 means black and 0xff means white. Do not set
725 the background and foreground to the same colour or you will see
729 bool "Enable legacy LCD support"
731 Define this to enable LCD support (for output to LCD display).
732 You will also need to select an LCD driver using an additional
733 CONFIG option. See the README for details. Drives which have been
734 converted to driver model will instead used CONFIG_DM_VIDEO.
739 Enables the common driver code for the Designware HDMI TX
740 block found in SoCs from various vendors.
741 As this does not provide any functionality by itself (but
742 rather requires a SoC-specific glue driver to call it), it
743 can not be enabled from the configuration menu.
745 config VIDEO_DSI_HOST_SANDBOX
746 bool "Enable sandbox for dsi host"
748 select VIDEO_MIPI_DSI
750 Enable support for sandbox dsi host device used for testing
752 Display Serial Interface (DSI) defines a serial bus and
753 a communication protocol between the host and the device
756 config VIDEO_DW_MIPI_DSI
758 select VIDEO_MIPI_DSI
760 Enables the common driver code for the Synopsis Designware
761 MIPI DSI block found in SoCs from various vendors.
762 As this does not provide any functionality by itself (but
763 rather requires a SoC-specific glue driver to call it), it
764 can not be enabled from the configuration menu.
767 bool "Simple display driver for preconfigured display"
769 Enables a simple generic display driver which utilizes the
770 simple-framebuffer devicetree bindings.
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.
776 config VIDEO_DT_SIMPLEFB
777 bool "Enable SimpleFB support for passing framebuffer to OS"
779 Enables the code to pass the framebuffer to the kernel as a
780 simple framebuffer in the device tree.
781 The video output is initialized by U-Boot, and kept by the
785 bool "Enable OSD support"
789 This supports drivers that provide a OSD (on-screen display), which
790 is a (usually text-oriented) graphics buffer to show information on
794 bool "Enable sandbox OSD"
797 Enable support for sandbox OSD device used for testing purposes.
800 bool "Enable IHS video out driver"
803 Enable support for the gdsys Integrated Hardware Systems (IHS) video
804 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic
805 textual overlays of the display outputs.