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 "Generic PWM based Backlight Driver"
19 depends on DM_VIDEO && DM_PWM
22 If you have a LCD backlight adjustable by PWM, say Y to enable
24 This driver can be use with "simple-panel" and
25 it understands the standard device tree
26 (leds/backlight/pwm-backlight.txt)
29 bool "Generic GPIO based Backlight Driver"
32 If you have a LCD backlight adjustable by GPIO, say Y to enable
34 This driver can be used with "simple-panel" and
35 it understands the standard device tree
36 (leds/backlight/gpio-backlight.txt)
39 bool "Support 8-bit-per-pixel displays"
41 default n if ARCH_SUNXI
44 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
45 Enabling this will include code to support this display. Without
46 this option, such displays will not be supported and console output
50 bool "Support 16-bit-per-pixel displays"
52 default n if ARCH_SUNXI
55 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
56 Enabling this will include code to support this display. Without
57 this option, such displays will not be supported and console output
61 bool "Support 32-bit-per-pixel displays"
65 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
66 Enabling this will include code to support this display. Without
67 this option, such displays will not be supported and console output
71 bool "Support ANSI escape sequences in video console"
75 Enable ANSI escape sequence decoding for a more fully functional
79 bool "Support a simple text console"
83 Support drawing text on the frame buffer console so that it can be
84 used as a console. Rotation is not supported by this driver (see
85 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
88 config CONSOLE_ROTATION
89 bool "Support rotated displays"
92 Sometimes, for example if the display is mounted in portrait
93 mode or even if it's mounted landscape but rotated by 180degree,
94 we need to rotate our content of the display relative to the
95 framebuffer, so that user can read the messages which are
96 printed out. Enable this option to include a text driver which can
97 support this. The rotation is set by the 'rot' parameter in
98 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
99 degrees, 3=270 degrees.
101 config CONSOLE_TRUETYPE
102 bool "Support a console that uses TrueType fonts"
105 TrueTrype fonts can provide outline-drawing capability rather than
106 needing to provide a bitmap for each font and size that is needed.
107 With this option you can adjust the text size and use a variety of
108 fonts. Note that this is noticeably slower than with normal console.
110 config CONSOLE_TRUETYPE_SIZE
111 int "TrueType font size"
112 depends on CONSOLE_TRUETYPE
115 This sets the font size for the console. The size is measured in
116 pixels and is the nominal height of a character. Note that fonts
117 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
118 However that measurement depends on the size of your display and
119 there is no standard display density. At present there is not a
120 method to select the display's physical size, which would allow
121 U-Boot to calculate the correct font size.
123 config SYS_WHITE_ON_BLACK
124 bool "Display console as white on a black background"
125 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86
127 Normally the display is black on a white background, Enable this
128 option to invert this, i.e. white on a black background. This can be
129 better in low-light situations or to reduce eye strain in some
133 bool "Skip framebuffer clear"
135 If firmware (whatever loads u-boot) has already put a splash image
136 on screen, you might want to preserve it until whatever u-boot
137 loads takes over the screen. This, for example, can be used to
138 keep splash image on screen until grub graphical boot menu starts.
140 source "drivers/video/fonts/Kconfig"
142 config VIDCONSOLE_AS_LCD
143 bool "Use 'vidconsole' when 'lcd' is seen in stdout"
146 This is a work-around for boards which have 'lcd' in their stdout
147 environment variable, but have moved to use driver model for video.
148 In this case the console will no-longer work. While it is possible
149 to update the environment, the breakage may be confusing for users.
150 This option will be removed around the end of 2016.
152 config VIDEO_COREBOOT
153 bool "Enable coreboot framebuffer driver support"
154 depends on X86 && SYS_COREBOOT
156 Turn on this option to enable a framebuffer driver when U-Boot is
157 loaded by coreboot where the graphics device is configured by
158 coreboot already. This can in principle be used with any platform
159 that coreboot supports.
162 bool "Enable VESA video driver support"
165 Turn on this option to enable a very simple driver which uses vesa
166 to discover the video mode and then provides a frame buffer for use
167 by U-Boot. This can in principle be used with any platform that
168 supports PCI and video cards that support VESA BIOS Extension (VBE).
170 config FRAMEBUFFER_SET_VESA_MODE
171 bool "Set framebuffer graphics resolution"
172 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
174 Set VESA/native framebuffer mode (needed for bootsplash and graphical
178 prompt "framebuffer graphics resolution"
179 default FRAMEBUFFER_VESA_MODE_117
180 depends on FRAMEBUFFER_SET_VESA_MODE
182 This option sets the resolution used for the U-Boot framebuffer (and
185 config FRAMEBUFFER_VESA_MODE_100
186 bool "640x400 256-color"
188 config FRAMEBUFFER_VESA_MODE_101
189 bool "640x480 256-color"
191 config FRAMEBUFFER_VESA_MODE_102
192 bool "800x600 16-color"
194 config FRAMEBUFFER_VESA_MODE_103
195 bool "800x600 256-color"
197 config FRAMEBUFFER_VESA_MODE_104
198 bool "1024x768 16-color"
200 config FRAMEBUFFER_VESA_MODE_105
201 bool "1024x768 256-color"
203 config FRAMEBUFFER_VESA_MODE_106
204 bool "1280x1024 16-color"
206 config FRAMEBUFFER_VESA_MODE_107
207 bool "1280x1024 256-color"
209 config FRAMEBUFFER_VESA_MODE_108
212 config FRAMEBUFFER_VESA_MODE_109
215 config FRAMEBUFFER_VESA_MODE_10A
218 config FRAMEBUFFER_VESA_MODE_10B
221 config FRAMEBUFFER_VESA_MODE_10C
224 config FRAMEBUFFER_VESA_MODE_10D
225 bool "320x200 32k-color (1:5:5:5)"
227 config FRAMEBUFFER_VESA_MODE_10E
228 bool "320x200 64k-color (5:6:5)"
230 config FRAMEBUFFER_VESA_MODE_10F
231 bool "320x200 16.8M-color (8:8:8)"
233 config FRAMEBUFFER_VESA_MODE_110
234 bool "640x480 32k-color (1:5:5:5)"
236 config FRAMEBUFFER_VESA_MODE_111
237 bool "640x480 64k-color (5:6:5)"
239 config FRAMEBUFFER_VESA_MODE_112
240 bool "640x480 16.8M-color (8:8:8)"
242 config FRAMEBUFFER_VESA_MODE_113
243 bool "800x600 32k-color (1:5:5:5)"
245 config FRAMEBUFFER_VESA_MODE_114
246 bool "800x600 64k-color (5:6:5)"
248 config FRAMEBUFFER_VESA_MODE_115
249 bool "800x600 16.8M-color (8:8:8)"
251 config FRAMEBUFFER_VESA_MODE_116
252 bool "1024x768 32k-color (1:5:5:5)"
254 config FRAMEBUFFER_VESA_MODE_117
255 bool "1024x768 64k-color (5:6:5)"
257 config FRAMEBUFFER_VESA_MODE_118
258 bool "1024x768 16.8M-color (8:8:8)"
260 config FRAMEBUFFER_VESA_MODE_119
261 bool "1280x1024 32k-color (1:5:5:5)"
263 config FRAMEBUFFER_VESA_MODE_11A
264 bool "1280x1024 64k-color (5:6:5)"
266 config FRAMEBUFFER_VESA_MODE_11B
267 bool "1280x1024 16.8M-color (8:8:8)"
269 config FRAMEBUFFER_VESA_MODE_USER
270 bool "Manually select VESA mode"
274 # Map the config names to an integer (KB).
275 config FRAMEBUFFER_VESA_MODE
276 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
278 default 0x100 if FRAMEBUFFER_VESA_MODE_100
279 default 0x101 if FRAMEBUFFER_VESA_MODE_101
280 default 0x102 if FRAMEBUFFER_VESA_MODE_102
281 default 0x103 if FRAMEBUFFER_VESA_MODE_103
282 default 0x104 if FRAMEBUFFER_VESA_MODE_104
283 default 0x105 if FRAMEBUFFER_VESA_MODE_105
284 default 0x106 if FRAMEBUFFER_VESA_MODE_106
285 default 0x107 if FRAMEBUFFER_VESA_MODE_107
286 default 0x108 if FRAMEBUFFER_VESA_MODE_108
287 default 0x109 if FRAMEBUFFER_VESA_MODE_109
288 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
289 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
290 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
291 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
292 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
293 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
294 default 0x110 if FRAMEBUFFER_VESA_MODE_110
295 default 0x111 if FRAMEBUFFER_VESA_MODE_111
296 default 0x112 if FRAMEBUFFER_VESA_MODE_112
297 default 0x113 if FRAMEBUFFER_VESA_MODE_113
298 default 0x114 if FRAMEBUFFER_VESA_MODE_114
299 default 0x115 if FRAMEBUFFER_VESA_MODE_115
300 default 0x116 if FRAMEBUFFER_VESA_MODE_116
301 default 0x117 if FRAMEBUFFER_VESA_MODE_117
302 default 0x118 if FRAMEBUFFER_VESA_MODE_118
303 default 0x119 if FRAMEBUFFER_VESA_MODE_119
304 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
305 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
306 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
308 config VIDEO_LCD_ANX9804
309 bool "ANX9804 bridge chip"
312 Support for the ANX9804 bridge chip, which can take pixel data coming
313 from a parallel LCD interface and translate it on the fy into a DP
314 interface for driving eDP TFT displays. It uses I2C for configuration.
316 config VIDEO_LCD_SSD2828
317 bool "SSD2828 bridge chip"
320 Support for the SSD2828 bridge chip, which can take pixel data coming
321 from a parallel LCD interface and translate it on the fly into MIPI DSI
322 interface for driving a MIPI compatible LCD panel. It uses SPI for
325 config VIDEO_LCD_SSD2828_TX_CLK
326 int "SSD2828 TX_CLK frequency (in MHz)"
327 depends on VIDEO_LCD_SSD2828
330 The frequency of the crystal, which is clocking SSD2828. It may be
331 anything in the 8MHz-30MHz range and the exact value should be
332 retrieved from the board schematics. Or in the case of Allwinner
333 hardware, it can be usually found as 'lcd_xtal_freq' variable in
334 FEX files. It can be also set to 0 for selecting PCLK from the
335 parallel LCD interface instead of TX_CLK as the PLL clock source.
337 config VIDEO_LCD_SSD2828_RESET
338 string "RESET pin of SSD2828"
339 depends on VIDEO_LCD_SSD2828
342 The reset pin of SSD2828 chip. This takes a string in the format
343 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
345 config VIDEO_LCD_HITACHI_TX18D42VM
346 bool "Hitachi tx18d42vm LVDS LCD panel support"
350 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
351 lcd controller which needs to be initialized over SPI, once that is
352 done they work like a regular LVDS panel.
354 config VIDEO_LCD_SPI_CS
355 string "SPI CS pin for LCD related config job"
356 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
359 This is one of the SPI communication pins, involved in setting up a
360 working LCD configuration. The exact role of SPI may differ for
361 different hardware setups. The option takes a string in the format
362 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
364 config VIDEO_LCD_SPI_SCLK
365 string "SPI SCLK pin for LCD related config job"
366 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
369 This is one of the SPI communication pins, involved in setting up a
370 working LCD configuration. The exact role of SPI may differ for
371 different hardware setups. The option takes a string in the format
372 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
374 config VIDEO_LCD_SPI_MOSI
375 string "SPI MOSI pin for LCD related config job"
376 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
379 This is one of the SPI communication pins, involved in setting up a
380 working LCD configuration. The exact role of SPI may differ for
381 different hardware setups. The option takes a string in the format
382 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
384 config VIDEO_LCD_SPI_MISO
385 string "SPI MISO pin for LCD related config job (optional)"
386 depends on VIDEO_LCD_SSD2828
389 This is one of the SPI communication pins, involved in setting up a
390 working LCD configuration. The exact role of SPI may differ for
391 different hardware setups. If wired up, this pin may provide additional
392 useful functionality. Such as bi-directional communication with the
393 hardware and LCD panel id retrieval (if the panel can report it). The
394 option takes a string in the format understood by 'name_to_gpio'
395 function, e.g. PH1 for pin 1 of port H.
398 bool "Armada XP LCD controller"
401 Support for the LCD controller integrated in the Marvell
405 bool "Enable EDID library"
409 This enables library for accessing EDID data from an LCD panel.
412 bool "Enable Display support"
417 This supports drivers that provide a display, such as eDP (Embedded
418 DisplayPort) and HDMI (High Definition Multimedia Interface).
419 The devices provide a simple interface to start up the display,
420 read display information and enable it.
423 bool "Enable ATMEL video support using HLCDC"
426 HLCDC supports video output to an attached LCD panel.
428 config VIDEO_BROADWELL_IGD
429 bool "Enable Intel Broadwell integrated graphics device"
432 This enables support for integrated graphics on Intel broadwell
433 devices. Initialisation is mostly performed by a VGA boot ROM, with
434 some setup handled by U-Boot itself. The graphics adaptor works as
435 a VESA device and supports LCD panels, eDP and LVDS outputs.
436 Configuration of most aspects of device operation is performed using
437 a special tool which configures the VGA ROM, but the graphics
438 resolution can be selected in U-Boot.
440 config VIDEO_IVYBRIDGE_IGD
441 bool "Enable Intel Ivybridge integration graphics support"
444 This enables support for integrated graphics on Intel ivybridge
445 devices. Initialisation is mostly performed by a VGA boot ROM, with
446 some setup handled by U-Boot itself. The graphics adaptor works as
447 a VESA device and supports LCD panels, eDP and LVDS outputs.
448 Configuration of most aspects of device operation is performed using
449 a special tool which configures the VGA ROM, but the graphics
450 resolution can be selected in U-Boot.
452 config VIDEO_FSL_DCU_FB
453 bool "Enable Freescale Display Control Unit"
456 This enables support for Freescale Display Control Unit (DCU4)
457 module found on Freescale Vybrid and QorIQ family of SoCs.
459 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
460 int "Freescale DCU framebuffer size"
461 depends on VIDEO_FSL_DCU_FB
464 Set maximum framebuffer size to be used for Freescale Display
465 Controller Unit (DCU4).
467 source "drivers/video/rockchip/Kconfig"
469 config VIDEO_SANDBOX_SDL
470 bool "Enable sandbox video console using SDL"
473 When using sandbox you can enable an emulated LCD display which
474 appears as an SDL (Simple DirectMedia Layer) window. This is a
475 console device and can display stdout output. Within U-Boot is is
476 a normal bitmap display and can display images as well as text.
478 source "drivers/video/stm32/Kconfig"
481 bool "Enable LCD support on Tegra20"
482 depends on OF_CONTROL
484 Tegra20 supports video output to an attached LCD panel as well as
485 other options such as HDMI. Only the LCD is supported in U-Boot.
486 This option enables this support which can be used on devices which
487 have an LCD display connected.
489 config VIDEO_TEGRA124
490 bool "Enable video support on Tegra124"
493 Tegra124 supports many video output options including eDP and
494 HDMI. At present only eDP is supported by U-Boot. This option
495 enables this support which can be used on devices which
496 have an eDP display connected.
498 source "drivers/video/bridge/Kconfig"
501 bool "Enable legacy video support"
504 Define this for video support, without using driver model. Some
505 drivers use this because they are not yet converted to driver
506 model. Video drivers typically provide a colour text console and
510 bool "i.MX IPUv3 Core video support"
511 depends on VIDEO && MX6
513 This enables framebuffer driver for i.MX processors working
514 on the IPUv3(Image Processing Unit) internal graphic processor.
517 bool "Enable colour frame buffer console"
521 Enables the colour frame buffer driver. This supports colour
522 output on a bitmap display from an in-memory frame buffer.
523 Several colour devices are supported along with various options to
524 adjust the supported features. The driver is implemented in
527 The following defines are needed (cf. smiLynxEM, i8042)
528 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
530 VIDEO_HW_RECTFILL graphic chip supports
531 rectangle fill (cf. smiLynxEM)
532 VIDEO_HW_BITBLT graphic chip supports
533 bit-blit (cf. smiLynxEM)
534 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
535 VIDEO_VISIBLE_ROWS visible pixel rows
536 VIDEO_PIXEL_SIZE bytes per pixel
537 VIDEO_DATA_FORMAT graphic data format
538 (0-5, cf. cfb_console.c)
539 VIDEO_FB_ADRS framebuffer address
540 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
541 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
542 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
543 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
544 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
545 for logo. Requires CONFIG_VIDEO_LOGO
546 CONFIG_CONSOLE_EXTRA_INFO
547 additional board info beside
549 CONFIG_HIDE_LOGO_VERSION
550 do not display bootloader
553 When CONFIG_CFB_CONSOLE is defined, the video console is the
554 default console. The serial console can be forced by setting the
555 environment 'console=serial'.
557 config CFB_CONSOLE_ANSI
558 bool "Support ANSI escape sequences"
559 depends on CFB_CONSOLE
561 This allows the colour buffer frame buffer driver to support
562 a limited number of ANSI escape sequences (cursor control,
563 erase functions and limited graphics rendition control). Normal
564 output from U-Boot will pass through this filter.
566 config VGA_AS_SINGLE_DEVICE
567 bool "Set the video as an output-only device"
568 depends on CFB_CONSOLE
571 If enable the framebuffer device will be initialized as an
572 output-only device. The Keyboard driver will not be set up. This
573 may be used if you have no keyboard device, or more than one
574 (USB Keyboard, AT Keyboard).
576 config VIDEO_SW_CURSOR
577 bool "Enable a software cursor"
578 depends on CFB_CONSOLE
579 default y if CFB_CONSOLE
581 This draws a cursor after the last character. No blinking is
582 provided. This makes it possible to see the current cursor
583 position when entering text on the console. It is recommended to
586 config CONSOLE_EXTRA_INFO
587 bool "Display additional board information"
588 depends on CFB_CONSOLE
590 Display additional board information strings that normally go to
591 the serial port. When this option is enabled, a board-specific
592 function video_get_info_str() is called to get the string for
593 each line of the display. The function should return the string,
594 which can be empty if there is nothing to display for that line.
596 config CONSOLE_SCROLL_LINES
597 int "Number of lines to scroll the console by"
598 depends on CFB_CONSOLE || DM_VIDEO || LCD
601 When the console need to be scrolled, this is the number of
602 lines to scroll by. It defaults to 1. Increasing this makes the
603 console jump but can help speed up operation when scrolling
606 config SYS_CONSOLE_BG_COL
607 hex "Background colour"
608 depends on CFB_CONSOLE
611 Defines the background colour for the console. The value is from
612 0x00 to 0xff and the meaning depends on the graphics card.
613 Typically, 0x00 means black and 0xff means white. Do not set
614 the background and foreground to the same colour or you will see
617 config SYS_CONSOLE_FG_COL
618 hex "Foreground colour"
619 depends on CFB_CONSOLE
622 Defines the foreground colour for the console. The value is from
623 0x00 to 0xff and the meaning depends on the graphics card.
624 Typically, 0x00 means black and 0xff means white. Do not set
625 the background and foreground to the same colour or you will see
629 bool "Enable legacy LCD support"
631 Define this to enable LCD support (for output to LCD display).
632 You will also need to select an LCD driver using an additional
633 CONFIG option. See the README for details. Drives which have been
634 converted to driver model will instead used CONFIG_DM_VIDEO.
639 Enables the common driver code for the Designware HDMI TX
640 block found in SoCs from various vendors.
641 As this does not provide any functionality by itself (but
642 rather requires a SoC-specific glue driver to call it), it
643 can not be enabled from the configuration menu.
646 bool "Simple display driver for preconfigured display"
648 Enables a simple generic display driver which utilizes the
649 simple-framebuffer devicetree bindings.
651 This driver assumes that the display hardware has been initialized
652 before u-boot starts, and u-boot will simply render to the pre-
653 allocated frame buffer surface.
655 config VIDEO_DT_SIMPLEFB
656 bool "Enable SimpleFB support for passing framebuffer to OS"
658 Enables the code to pass the framebuffer to the kernel as a
659 simple framebuffer in the device tree.
660 The video output is initialized by U-Boot, and kept by the