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"
43 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
44 Enabling this will include code to support this display. Without
45 this option, such displays will not be supported and console output
49 bool "Support 16-bit-per-pixel displays"
53 Support drawing text and bitmaps onto a 16-bit-per-pixel display.
54 Enabling this will include code to support this display. Without
55 this option, such displays will not be supported and console output
59 bool "Support 32-bit-per-pixel displays"
63 Support drawing text and bitmaps onto a 32-bit-per-pixel display.
64 Enabling this will include code to support this display. Without
65 this option, such displays will not be supported and console output
69 bool "Support a simple text console"
73 Support drawing text on the frame buffer console so that it can be
74 used as a console. Rotation is not supported by this driver (see
75 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
78 config CONSOLE_ROTATION
79 bool "Support rotated displays"
82 Sometimes, for example if the display is mounted in portrait
83 mode or even if it's mounted landscape but rotated by 180degree,
84 we need to rotate our content of the display relative to the
85 framebuffer, so that user can read the messages which are
86 printed out. Enable this option to include a text driver which can
87 support this. The rotation is set by the 'rot' parameter in
88 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
89 degrees, 3=270 degrees.
91 config CONSOLE_TRUETYPE
92 bool "Support a console that uses TrueType fonts"
95 TrueTrype fonts can provide outline-drawing capability rather than
96 needing to provide a bitmap for each font and size that is needed.
97 With this option you can adjust the text size and use a variety of
98 fonts. Note that this is noticeably slower than with normal console.
100 config CONSOLE_TRUETYPE_SIZE
101 int "TrueType font size"
102 depends on CONSOLE_TRUETYPE
105 This sets the font size for the console. The size is measured in
106 pixels and is the nominal height of a character. Note that fonts
107 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
108 However that measurement depends on the size of your display and
109 there is no standard display density. At present there is not a
110 method to select the display's physical size, which would allow
111 U-Boot to calculate the correct font size.
113 config SYS_WHITE_ON_BLACK
114 bool "Display console as white on a black background"
115 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86
117 Normally the display is black on a white background, Enable this
118 option to invert this, i.e. white on a black background. This can be
119 better in low-light situations or to reduce eye strain in some
123 bool "Skip framebuffer clear"
125 If firmware (whatever loads u-boot) has already put a splash image
126 on screen, you might want to preserve it until whatever u-boot
127 loads takes over the screen. This, for example, can be used to
128 keep splash image on screen until grub graphical boot menu starts.
130 source "drivers/video/fonts/Kconfig"
132 config VIDCONSOLE_AS_LCD
133 bool "Use 'vidconsole' when 'lcd' is seen in stdout"
136 This is a work-around for boards which have 'lcd' in their stdout
137 environment variable, but have moved to use driver model for video.
138 In this case the console will no-longer work. While it is possible
139 to update the environment, the breakage may be confusing for users.
140 This option will be removed around the end of 2016.
142 config VIDEO_COREBOOT
143 bool "Enable coreboot framebuffer driver support"
144 depends on X86 && SYS_COREBOOT
146 Turn on this option to enable a framebuffer driver when U-Boot is
147 loaded by coreboot where the graphics device is configured by
148 coreboot already. This can in principle be used with any platform
149 that coreboot supports.
152 bool "Enable VESA video driver support"
155 Turn on this option to enable a very simple driver which uses vesa
156 to discover the video mode and then provides a frame buffer for use
157 by U-Boot. This can in principle be used with any platform that
158 supports PCI and video cards that support VESA BIOS Extension (VBE).
160 config FRAMEBUFFER_SET_VESA_MODE
161 bool "Set framebuffer graphics resolution"
162 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
164 Set VESA/native framebuffer mode (needed for bootsplash and graphical
168 prompt "framebuffer graphics resolution"
169 default FRAMEBUFFER_VESA_MODE_117
170 depends on FRAMEBUFFER_SET_VESA_MODE
172 This option sets the resolution used for the U-Boot framebuffer (and
175 config FRAMEBUFFER_VESA_MODE_100
176 bool "640x400 256-color"
178 config FRAMEBUFFER_VESA_MODE_101
179 bool "640x480 256-color"
181 config FRAMEBUFFER_VESA_MODE_102
182 bool "800x600 16-color"
184 config FRAMEBUFFER_VESA_MODE_103
185 bool "800x600 256-color"
187 config FRAMEBUFFER_VESA_MODE_104
188 bool "1024x768 16-color"
190 config FRAMEBUFFER_VESA_MODE_105
191 bool "1024x768 256-color"
193 config FRAMEBUFFER_VESA_MODE_106
194 bool "1280x1024 16-color"
196 config FRAMEBUFFER_VESA_MODE_107
197 bool "1280x1024 256-color"
199 config FRAMEBUFFER_VESA_MODE_108
202 config FRAMEBUFFER_VESA_MODE_109
205 config FRAMEBUFFER_VESA_MODE_10A
208 config FRAMEBUFFER_VESA_MODE_10B
211 config FRAMEBUFFER_VESA_MODE_10C
214 config FRAMEBUFFER_VESA_MODE_10D
215 bool "320x200 32k-color (1:5:5:5)"
217 config FRAMEBUFFER_VESA_MODE_10E
218 bool "320x200 64k-color (5:6:5)"
220 config FRAMEBUFFER_VESA_MODE_10F
221 bool "320x200 16.8M-color (8:8:8)"
223 config FRAMEBUFFER_VESA_MODE_110
224 bool "640x480 32k-color (1:5:5:5)"
226 config FRAMEBUFFER_VESA_MODE_111
227 bool "640x480 64k-color (5:6:5)"
229 config FRAMEBUFFER_VESA_MODE_112
230 bool "640x480 16.8M-color (8:8:8)"
232 config FRAMEBUFFER_VESA_MODE_113
233 bool "800x600 32k-color (1:5:5:5)"
235 config FRAMEBUFFER_VESA_MODE_114
236 bool "800x600 64k-color (5:6:5)"
238 config FRAMEBUFFER_VESA_MODE_115
239 bool "800x600 16.8M-color (8:8:8)"
241 config FRAMEBUFFER_VESA_MODE_116
242 bool "1024x768 32k-color (1:5:5:5)"
244 config FRAMEBUFFER_VESA_MODE_117
245 bool "1024x768 64k-color (5:6:5)"
247 config FRAMEBUFFER_VESA_MODE_118
248 bool "1024x768 16.8M-color (8:8:8)"
250 config FRAMEBUFFER_VESA_MODE_119
251 bool "1280x1024 32k-color (1:5:5:5)"
253 config FRAMEBUFFER_VESA_MODE_11A
254 bool "1280x1024 64k-color (5:6:5)"
256 config FRAMEBUFFER_VESA_MODE_11B
257 bool "1280x1024 16.8M-color (8:8:8)"
259 config FRAMEBUFFER_VESA_MODE_USER
260 bool "Manually select VESA mode"
264 # Map the config names to an integer (KB).
265 config FRAMEBUFFER_VESA_MODE
266 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
268 default 0x100 if FRAMEBUFFER_VESA_MODE_100
269 default 0x101 if FRAMEBUFFER_VESA_MODE_101
270 default 0x102 if FRAMEBUFFER_VESA_MODE_102
271 default 0x103 if FRAMEBUFFER_VESA_MODE_103
272 default 0x104 if FRAMEBUFFER_VESA_MODE_104
273 default 0x105 if FRAMEBUFFER_VESA_MODE_105
274 default 0x106 if FRAMEBUFFER_VESA_MODE_106
275 default 0x107 if FRAMEBUFFER_VESA_MODE_107
276 default 0x108 if FRAMEBUFFER_VESA_MODE_108
277 default 0x109 if FRAMEBUFFER_VESA_MODE_109
278 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
279 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
280 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
281 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
282 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
283 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
284 default 0x110 if FRAMEBUFFER_VESA_MODE_110
285 default 0x111 if FRAMEBUFFER_VESA_MODE_111
286 default 0x112 if FRAMEBUFFER_VESA_MODE_112
287 default 0x113 if FRAMEBUFFER_VESA_MODE_113
288 default 0x114 if FRAMEBUFFER_VESA_MODE_114
289 default 0x115 if FRAMEBUFFER_VESA_MODE_115
290 default 0x116 if FRAMEBUFFER_VESA_MODE_116
291 default 0x117 if FRAMEBUFFER_VESA_MODE_117
292 default 0x118 if FRAMEBUFFER_VESA_MODE_118
293 default 0x119 if FRAMEBUFFER_VESA_MODE_119
294 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
295 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
296 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
298 config VIDEO_LCD_ANX9804
299 bool "ANX9804 bridge chip"
302 Support for the ANX9804 bridge chip, which can take pixel data coming
303 from a parallel LCD interface and translate it on the fy into a DP
304 interface for driving eDP TFT displays. It uses I2C for configuration.
306 config VIDEO_LCD_SSD2828
307 bool "SSD2828 bridge chip"
310 Support for the SSD2828 bridge chip, which can take pixel data coming
311 from a parallel LCD interface and translate it on the fly into MIPI DSI
312 interface for driving a MIPI compatible LCD panel. It uses SPI for
315 config VIDEO_LCD_SSD2828_TX_CLK
316 int "SSD2828 TX_CLK frequency (in MHz)"
317 depends on VIDEO_LCD_SSD2828
320 The frequency of the crystal, which is clocking SSD2828. It may be
321 anything in the 8MHz-30MHz range and the exact value should be
322 retrieved from the board schematics. Or in the case of Allwinner
323 hardware, it can be usually found as 'lcd_xtal_freq' variable in
324 FEX files. It can be also set to 0 for selecting PCLK from the
325 parallel LCD interface instead of TX_CLK as the PLL clock source.
327 config VIDEO_LCD_SSD2828_RESET
328 string "RESET pin of SSD2828"
329 depends on VIDEO_LCD_SSD2828
332 The reset pin of SSD2828 chip. This takes a string in the format
333 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
335 config VIDEO_LCD_HITACHI_TX18D42VM
336 bool "Hitachi tx18d42vm LVDS LCD panel support"
340 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
341 lcd controller which needs to be initialized over SPI, once that is
342 done they work like a regular LVDS panel.
344 config VIDEO_LCD_SPI_CS
345 string "SPI CS pin for LCD related config job"
346 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
349 This is one of the SPI communication pins, involved in setting up a
350 working LCD configuration. The exact role of SPI may differ for
351 different hardware setups. The option takes a string in the format
352 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
354 config VIDEO_LCD_SPI_SCLK
355 string "SPI SCLK 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_MOSI
365 string "SPI MOSI 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_MISO
375 string "SPI MISO pin for LCD related config job (optional)"
376 depends on VIDEO_LCD_SSD2828
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. If wired up, this pin may provide additional
382 useful functionality. Such as bi-directional communication with the
383 hardware and LCD panel id retrieval (if the panel can report it). The
384 option takes a string in the format understood by 'name_to_gpio'
385 function, e.g. PH1 for pin 1 of port H.
388 bool "Armada XP LCD controller"
391 Support for the LCD controller integrated in the Marvell
395 bool "Enable EDID library"
399 This enables library for accessing EDID data from an LCD panel.
402 bool "Enable Display support"
407 This supports drivers that provide a display, such as eDP (Embedded
408 DisplayPort) and HDMI (High Definition Multimedia Interface).
409 The devices provide a simple interface to start up the display,
410 read display information and enable it.
413 bool "Enable ATMEL video support using HLCDC"
416 HLCDC supports video output to an attached LCD panel.
418 config VIDEO_BROADWELL_IGD
419 bool "Enable Intel Broadwell integrated graphics device"
422 This enables support for integrated graphics on Intel broadwell
423 devices. Initialisation is mostly performed by a VGA boot ROM, with
424 some setup handled by U-Boot itself. The graphics adaptor works as
425 a VESA device and supports LCD panels, eDP and LVDS outputs.
426 Configuration of most aspects of device operation is performed using
427 a special tool which configures the VGA ROM, but the graphics
428 resolution can be selected in U-Boot.
430 config VIDEO_IVYBRIDGE_IGD
431 bool "Enable Intel Ivybridge integration graphics support"
434 This enables support for integrated graphics on Intel ivybridge
435 devices. Initialisation is mostly performed by a VGA boot ROM, with
436 some setup handled by U-Boot itself. The graphics adaptor works as
437 a VESA device and supports LCD panels, eDP and LVDS outputs.
438 Configuration of most aspects of device operation is performed using
439 a special tool which configures the VGA ROM, but the graphics
440 resolution can be selected in U-Boot.
442 config VIDEO_FSL_DCU_FB
443 bool "Enable Freescale Display Control Unit"
446 This enables support for Freescale Display Control Unit (DCU4)
447 module found on Freescale Vybrid and QorIQ family of SoCs.
449 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
450 int "Freescale DCU framebuffer size"
451 depends on VIDEO_FSL_DCU_FB
454 Set maximum framebuffer size to be used for Freescale Display
455 Controller Unit (DCU4).
457 source "drivers/video/rockchip/Kconfig"
459 config VIDEO_SANDBOX_SDL
460 bool "Enable sandbox video console using SDL"
463 When using sandbox you can enable an emulated LCD display which
464 appears as an SDL (Simple DirectMedia Layer) window. This is a
465 console device and can display stdout output. Within U-Boot is is
466 a normal bitmap display and can display images as well as text.
468 source "drivers/video/stm32/Kconfig"
471 bool "Enable LCD support on Tegra20"
472 depends on OF_CONTROL
474 Tegra20 supports video output to an attached LCD panel as well as
475 other options such as HDMI. Only the LCD is supported in U-Boot.
476 This option enables this support which can be used on devices which
477 have an LCD display connected.
479 config VIDEO_TEGRA124
480 bool "Enable video support on Tegra124"
483 Tegra124 supports many video output options including eDP and
484 HDMI. At present only eDP is supported by U-Boot. This option
485 enables this support which can be used on devices which
486 have an eDP display connected.
488 source "drivers/video/bridge/Kconfig"
491 bool "Enable legacy video support"
494 Define this for video support, without using driver model. Some
495 drivers use this because they are not yet converted to driver
496 model. Video drivers typically provide a colour text console and
500 bool "i.MX IPUv3 Core video support"
501 depends on VIDEO && MX6
503 This enables framebuffer driver for i.MX processors working
504 on the IPUv3(Image Processing Unit) internal graphic processor.
507 bool "Enable colour frame buffer console"
511 Enables the colour frame buffer driver. This supports colour
512 output on a bitmap display from an in-memory frame buffer.
513 Several colour devices are supported along with various options to
514 adjust the supported features. The driver is implemented in
517 The following defines are needed (cf. smiLynxEM, i8042)
518 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
520 VIDEO_HW_RECTFILL graphic chip supports
521 rectangle fill (cf. smiLynxEM)
522 VIDEO_HW_BITBLT graphic chip supports
523 bit-blit (cf. smiLynxEM)
524 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
525 VIDEO_VISIBLE_ROWS visible pixel rows
526 VIDEO_PIXEL_SIZE bytes per pixel
527 VIDEO_DATA_FORMAT graphic data format
528 (0-5, cf. cfb_console.c)
529 VIDEO_FB_ADRS framebuffer address
530 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
531 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
532 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
533 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
534 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
535 for logo. Requires CONFIG_VIDEO_LOGO
536 CONFIG_CONSOLE_EXTRA_INFO
537 additional board info beside
539 CONFIG_HIDE_LOGO_VERSION
540 do not display bootloader
543 When CONFIG_CFB_CONSOLE is defined, the video console is the
544 default console. The serial console can be forced by setting the
545 environment 'console=serial'.
547 config CFB_CONSOLE_ANSI
548 bool "Support ANSI escape sequences"
549 depends on CFB_CONSOLE
551 This allows the colour buffer frame buffer driver to support
552 a limited number of ANSI escape sequences (cursor control,
553 erase functions and limited graphics rendition control). Normal
554 output from U-Boot will pass through this filter.
556 config VGA_AS_SINGLE_DEVICE
557 bool "Set the video as an output-only device"
558 depends on CFB_CONSOLE
561 If enable the framebuffer device will be initialized as an
562 output-only device. The Keyboard driver will not be set up. This
563 may be used if you have no keyboard device, or more than one
564 (USB Keyboard, AT Keyboard).
566 config VIDEO_SW_CURSOR
567 bool "Enable a software cursor"
568 depends on CFB_CONSOLE
569 default y if CFB_CONSOLE
571 This draws a cursor after the last character. No blinking is
572 provided. This makes it possible to see the current cursor
573 position when entering text on the console. It is recommended to
576 config CONSOLE_EXTRA_INFO
577 bool "Display additional board information"
578 depends on CFB_CONSOLE
580 Display additional board information strings that normally go to
581 the serial port. When this option is enabled, a board-specific
582 function video_get_info_str() is called to get the string for
583 each line of the display. The function should return the string,
584 which can be empty if there is nothing to display for that line.
586 config CONSOLE_SCROLL_LINES
587 int "Number of lines to scroll the console by"
588 depends on CFB_CONSOLE || DM_VIDEO || LCD
591 When the console need to be scrolled, this is the number of
592 lines to scroll by. It defaults to 1. Increasing this makes the
593 console jump but can help speed up operation when scrolling
596 config SYS_CONSOLE_BG_COL
597 hex "Background colour"
598 depends on CFB_CONSOLE
601 Defines the background colour for the console. The value is from
602 0x00 to 0xff and the meaning depends on the graphics card.
603 Typically, 0x00 means black and 0xff means white. Do not set
604 the background and foreground to the same colour or you will see
607 config SYS_CONSOLE_FG_COL
608 hex "Foreground colour"
609 depends on CFB_CONSOLE
612 Defines the foreground colour for the console. The value is from
613 0x00 to 0xff and the meaning depends on the graphics card.
614 Typically, 0x00 means black and 0xff means white. Do not set
615 the background and foreground to the same colour or you will see
619 bool "Enable legacy LCD support"
621 Define this to enable LCD support (for output to LCD display).
622 You will also need to select an LCD driver using an additional
623 CONFIG option. See the README for details. Drives which have been
624 converted to driver model will instead used CONFIG_DM_VIDEO.
629 Enables the common driver code for the Designware HDMI TX
630 block found in SoCs from various vendors.
631 As this does not provide any functionality by itself (but
632 rather requires a SoC-specific glue driver to call it), it
633 can not be enabled from the configuration menu.
636 bool "Simple display driver for preconfigured display"
638 Enables a simple generic display driver which utilizes the
639 simple-framebuffer devicetree bindings.
641 This driver assumes that the display hardware has been initialized
642 before u-boot starts, and u-boot will simply render to the pre-
643 allocated frame buffer surface.