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 "Support 8-bit-per-pixel displays"
33 Support drawing text and bitmaps onto a 8-bit-per-pixel display.
34 Enabling this will include code to support this display. Without
35 this option, such displays will not be supported and console output
39 bool "Support 16-bit-per-pixel displays"
43 Support drawing text and bitmaps onto a 16-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 32-bit-per-pixel displays"
53 Support drawing text and bitmaps onto a 32-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 a simple text console"
63 Support drawing text on the frame buffer console so that it can be
64 used as a console. Rotation is not supported by this driver (see
65 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used
68 config CONSOLE_ROTATION
69 bool "Support rotated displays"
72 Sometimes, for example if the display is mounted in portrait
73 mode or even if it's mounted landscape but rotated by 180degree,
74 we need to rotate our content of the display relative to the
75 framebuffer, so that user can read the messages which are
76 printed out. Enable this option to include a text driver which can
77 support this. The rotation is set by the 'rot' parameter in
78 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180
79 degrees, 3=270 degrees.
81 config CONSOLE_TRUETYPE
82 bool "Support a console that uses TrueType fonts"
85 TrueTrype fonts can provide outline-drawing capability rather than
86 needing to provide a bitmap for each font and size that is needed.
87 With this option you can adjust the text size and use a variety of
88 fonts. Note that this is noticeably slower than with normal console.
90 config CONSOLE_TRUETYPE_SIZE
91 int "TrueType font size"
92 depends on CONSOLE_TRUETYPE
95 This sets the font size for the console. The size is measured in
96 pixels and is the nominal height of a character. Note that fonts
97 are commonly measured in 'points', being 1/72 inch (about 3.52mm).
98 However that measurement depends on the size of your display and
99 there is no standard display density. At present there is not a
100 method to select the display's physical size, which would allow
101 U-Boot to calculate the correct font size.
103 config SYS_WHITE_ON_BLACK
104 bool "Display console as white on a black background"
105 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || TEGRA || X86
107 Normally the display is black on a white background, Enable this
108 option to invert this, i.e. white on a black background. This can be
109 better in low-light situations or to reduce eye strain in some
112 source "drivers/video/fonts/Kconfig"
114 config VIDCONSOLE_AS_LCD
115 bool "Use 'vidconsole' when 'lcd' is seen in stdout"
118 This is a work-around for boards which have 'lcd' in their stdout
119 environment variable, but have moved to use driver model for video.
120 In this case the console will no-longer work. While it is possible
121 to update the environment, the breakage may be confusing for users.
122 This option will be removed around the end of 2016.
124 config VIDEO_COREBOOT
125 bool "Enable coreboot framebuffer driver support"
126 depends on X86 && SYS_COREBOOT
128 Turn on this option to enable a framebuffer driver when U-Boot is
129 loaded by coreboot where the graphics device is configured by
130 coreboot already. This can in principle be used with any platform
131 that coreboot supports.
134 bool "Enable VESA video driver support"
137 Turn on this option to enable a very simple driver which uses vesa
138 to discover the video mode and then provides a frame buffer for use
139 by U-Boot. This can in principle be used with any platform that
140 supports PCI and video cards that support VESA BIOS Extension (VBE).
142 config FRAMEBUFFER_SET_VESA_MODE
143 bool "Set framebuffer graphics resolution"
144 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD
146 Set VESA/native framebuffer mode (needed for bootsplash and graphical
150 prompt "framebuffer graphics resolution"
151 default FRAMEBUFFER_VESA_MODE_117
152 depends on FRAMEBUFFER_SET_VESA_MODE
154 This option sets the resolution used for the U-Boot framebuffer (and
157 config FRAMEBUFFER_VESA_MODE_100
158 bool "640x400 256-color"
160 config FRAMEBUFFER_VESA_MODE_101
161 bool "640x480 256-color"
163 config FRAMEBUFFER_VESA_MODE_102
164 bool "800x600 16-color"
166 config FRAMEBUFFER_VESA_MODE_103
167 bool "800x600 256-color"
169 config FRAMEBUFFER_VESA_MODE_104
170 bool "1024x768 16-color"
172 config FRAMEBUFFER_VESA_MODE_105
173 bool "1024x768 256-color"
175 config FRAMEBUFFER_VESA_MODE_106
176 bool "1280x1024 16-color"
178 config FRAMEBUFFER_VESA_MODE_107
179 bool "1280x1024 256-color"
181 config FRAMEBUFFER_VESA_MODE_108
184 config FRAMEBUFFER_VESA_MODE_109
187 config FRAMEBUFFER_VESA_MODE_10A
190 config FRAMEBUFFER_VESA_MODE_10B
193 config FRAMEBUFFER_VESA_MODE_10C
196 config FRAMEBUFFER_VESA_MODE_10D
197 bool "320x200 32k-color (1:5:5:5)"
199 config FRAMEBUFFER_VESA_MODE_10E
200 bool "320x200 64k-color (5:6:5)"
202 config FRAMEBUFFER_VESA_MODE_10F
203 bool "320x200 16.8M-color (8:8:8)"
205 config FRAMEBUFFER_VESA_MODE_110
206 bool "640x480 32k-color (1:5:5:5)"
208 config FRAMEBUFFER_VESA_MODE_111
209 bool "640x480 64k-color (5:6:5)"
211 config FRAMEBUFFER_VESA_MODE_112
212 bool "640x480 16.8M-color (8:8:8)"
214 config FRAMEBUFFER_VESA_MODE_113
215 bool "800x600 32k-color (1:5:5:5)"
217 config FRAMEBUFFER_VESA_MODE_114
218 bool "800x600 64k-color (5:6:5)"
220 config FRAMEBUFFER_VESA_MODE_115
221 bool "800x600 16.8M-color (8:8:8)"
223 config FRAMEBUFFER_VESA_MODE_116
224 bool "1024x768 32k-color (1:5:5:5)"
226 config FRAMEBUFFER_VESA_MODE_117
227 bool "1024x768 64k-color (5:6:5)"
229 config FRAMEBUFFER_VESA_MODE_118
230 bool "1024x768 16.8M-color (8:8:8)"
232 config FRAMEBUFFER_VESA_MODE_119
233 bool "1280x1024 32k-color (1:5:5:5)"
235 config FRAMEBUFFER_VESA_MODE_11A
236 bool "1280x1024 64k-color (5:6:5)"
238 config FRAMEBUFFER_VESA_MODE_11B
239 bool "1280x1024 16.8M-color (8:8:8)"
241 config FRAMEBUFFER_VESA_MODE_USER
242 bool "Manually select VESA mode"
246 # Map the config names to an integer (KB).
247 config FRAMEBUFFER_VESA_MODE
248 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER
250 default 0x100 if FRAMEBUFFER_VESA_MODE_100
251 default 0x101 if FRAMEBUFFER_VESA_MODE_101
252 default 0x102 if FRAMEBUFFER_VESA_MODE_102
253 default 0x103 if FRAMEBUFFER_VESA_MODE_103
254 default 0x104 if FRAMEBUFFER_VESA_MODE_104
255 default 0x105 if FRAMEBUFFER_VESA_MODE_105
256 default 0x106 if FRAMEBUFFER_VESA_MODE_106
257 default 0x107 if FRAMEBUFFER_VESA_MODE_107
258 default 0x108 if FRAMEBUFFER_VESA_MODE_108
259 default 0x109 if FRAMEBUFFER_VESA_MODE_109
260 default 0x10A if FRAMEBUFFER_VESA_MODE_10A
261 default 0x10B if FRAMEBUFFER_VESA_MODE_10B
262 default 0x10C if FRAMEBUFFER_VESA_MODE_10C
263 default 0x10D if FRAMEBUFFER_VESA_MODE_10D
264 default 0x10E if FRAMEBUFFER_VESA_MODE_10E
265 default 0x10F if FRAMEBUFFER_VESA_MODE_10F
266 default 0x110 if FRAMEBUFFER_VESA_MODE_110
267 default 0x111 if FRAMEBUFFER_VESA_MODE_111
268 default 0x112 if FRAMEBUFFER_VESA_MODE_112
269 default 0x113 if FRAMEBUFFER_VESA_MODE_113
270 default 0x114 if FRAMEBUFFER_VESA_MODE_114
271 default 0x115 if FRAMEBUFFER_VESA_MODE_115
272 default 0x116 if FRAMEBUFFER_VESA_MODE_116
273 default 0x117 if FRAMEBUFFER_VESA_MODE_117
274 default 0x118 if FRAMEBUFFER_VESA_MODE_118
275 default 0x119 if FRAMEBUFFER_VESA_MODE_119
276 default 0x11A if FRAMEBUFFER_VESA_MODE_11A
277 default 0x11B if FRAMEBUFFER_VESA_MODE_11B
278 default 0x117 if FRAMEBUFFER_VESA_MODE_USER
280 config VIDEO_LCD_ANX9804
281 bool "ANX9804 bridge chip"
284 Support for the ANX9804 bridge chip, which can take pixel data coming
285 from a parallel LCD interface and translate it on the fy into a DP
286 interface for driving eDP TFT displays. It uses I2C for configuration.
288 config VIDEO_LCD_SSD2828
289 bool "SSD2828 bridge chip"
292 Support for the SSD2828 bridge chip, which can take pixel data coming
293 from a parallel LCD interface and translate it on the fly into MIPI DSI
294 interface for driving a MIPI compatible LCD panel. It uses SPI for
297 config VIDEO_LCD_SSD2828_TX_CLK
298 int "SSD2828 TX_CLK frequency (in MHz)"
299 depends on VIDEO_LCD_SSD2828
302 The frequency of the crystal, which is clocking SSD2828. It may be
303 anything in the 8MHz-30MHz range and the exact value should be
304 retrieved from the board schematics. Or in the case of Allwinner
305 hardware, it can be usually found as 'lcd_xtal_freq' variable in
306 FEX files. It can be also set to 0 for selecting PCLK from the
307 parallel LCD interface instead of TX_CLK as the PLL clock source.
309 config VIDEO_LCD_SSD2828_RESET
310 string "RESET pin of SSD2828"
311 depends on VIDEO_LCD_SSD2828
314 The reset pin of SSD2828 chip. This takes a string in the format
315 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
317 config VIDEO_LCD_HITACHI_TX18D42VM
318 bool "Hitachi tx18d42vm LVDS LCD panel support"
322 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a
323 lcd controller which needs to be initialized over SPI, once that is
324 done they work like a regular LVDS panel.
326 config VIDEO_LCD_SPI_CS
327 string "SPI CS pin for LCD related config job"
328 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
331 This is one of the SPI communication pins, involved in setting up a
332 working LCD configuration. The exact role of SPI may differ for
333 different hardware setups. The option takes a string in the format
334 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
336 config VIDEO_LCD_SPI_SCLK
337 string "SPI SCLK pin for LCD related config job"
338 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
341 This is one of the SPI communication pins, involved in setting up a
342 working LCD configuration. The exact role of SPI may differ for
343 different hardware setups. The option takes a string in the format
344 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
346 config VIDEO_LCD_SPI_MOSI
347 string "SPI MOSI pin for LCD related config job"
348 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM
351 This is one of the SPI communication pins, involved in setting up a
352 working LCD configuration. The exact role of SPI may differ for
353 different hardware setups. The option takes a string in the format
354 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H.
356 config VIDEO_LCD_SPI_MISO
357 string "SPI MISO pin for LCD related config job (optional)"
358 depends on VIDEO_LCD_SSD2828
361 This is one of the SPI communication pins, involved in setting up a
362 working LCD configuration. The exact role of SPI may differ for
363 different hardware setups. If wired up, this pin may provide additional
364 useful functionality. Such as bi-directional communication with the
365 hardware and LCD panel id retrieval (if the panel can report it). The
366 option takes a string in the format understood by 'name_to_gpio'
367 function, e.g. PH1 for pin 1 of port H.
370 bool "Armada XP LCD controller"
373 Support for the LCD controller integrated in the Marvell
377 bool "Enable EDID library"
381 This enables library for accessing EDID data from an LCD panel.
384 bool "Enable Display support"
389 This supports drivers that provide a display, such as eDP (Embedded
390 DisplayPort) and HDMI (High Definition Multimedia Interface).
391 The devices provide a simple interface to start up the display,
392 read display information and enable it.
395 bool "Enable ATMEL video support using HLCDC"
398 HLCDC supports video output to an attached LCD panel.
400 config VIDEO_BROADWELL_IGD
401 bool "Enable Intel Broadwell integrated graphics device"
404 This enables support for integrated graphics on Intel broadwell
405 devices. Initialisation is mostly performed by a VGA boot ROM, with
406 some setup handled by U-Boot itself. The graphics adaptor works as
407 a VESA device and supports LCD panels, eDP and LVDS outputs.
408 Configuration of most aspects of device operation is performed using
409 a special tool which configures the VGA ROM, but the graphics
410 resolution can be selected in U-Boot.
412 config VIDEO_IVYBRIDGE_IGD
413 bool "Enable Intel Ivybridge integration graphics support"
416 This enables support for integrated graphics on Intel ivybridge
417 devices. Initialisation is mostly performed by a VGA boot ROM, with
418 some setup handled by U-Boot itself. The graphics adaptor works as
419 a VESA device and supports LCD panels, eDP and LVDS outputs.
420 Configuration of most aspects of device operation is performed using
421 a special tool which configures the VGA ROM, but the graphics
422 resolution can be selected in U-Boot.
424 config VIDEO_FSL_DCU_FB
425 bool "Enable Freescale Display Control Unit"
428 This enables support for Freescale Display Control Unit (DCU4)
429 module found on Freescale Vybrid and QorIQ family of SoCs.
431 config VIDEO_FSL_DCU_MAX_FB_SIZE_MB
432 int "Freescale DCU framebuffer size"
433 depends on VIDEO_FSL_DCU_FB
436 Set maximum framebuffer size to be used for Freescale Display
437 Controller Unit (DCU4).
439 source "drivers/video/rockchip/Kconfig"
441 config VIDEO_SANDBOX_SDL
442 bool "Enable sandbox video console using SDL"
445 When using sandbox you can enable an emulated LCD display which
446 appears as an SDL (Simple DirectMedia Layer) window. This is a
447 console device and can display stdout output. Within U-Boot is is
448 a normal bitmap display and can display images as well as text.
451 bool "Enable LCD support on Tegra20"
452 depends on OF_CONTROL
454 Tegra20 supports video output to an attached LCD panel as well as
455 other options such as HDMI. Only the LCD is supported in U-Boot.
456 This option enables this support which can be used on devices which
457 have an LCD display connected.
459 config VIDEO_TEGRA124
460 bool "Enable video support on Tegra124"
463 Tegra124 supports many video output options including eDP and
464 HDMI. At present only eDP is supported by U-Boot. This option
465 enables this support which can be used on devices which
466 have an eDP display connected.
468 source "drivers/video/bridge/Kconfig"
471 bool "Enable legacy video support"
474 Define this for video support, without using driver model. Some
475 drivers use this because they are not yet converted to driver
476 model. Video drivers typically provide a colour text console and
480 bool "i.MX IPUv3 Core video support"
481 depends on VIDEO && MX6
483 This enables framebuffer driver for i.MX processors working
484 on the IPUv3(Image Processing Unit) internal graphic processor.
487 bool "Enable colour frame buffer console"
491 Enables the colour frame buffer driver. This supports colour
492 output on a bitmap display from an in-memory frame buffer.
493 Several colour devices are supported along with various options to
494 adjust the supported features. The driver is implemented in
497 The following defines are needed (cf. smiLynxEM, i8042)
498 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
500 VIDEO_HW_RECTFILL graphic chip supports
501 rectangle fill (cf. smiLynxEM)
502 VIDEO_HW_BITBLT graphic chip supports
503 bit-blit (cf. smiLynxEM)
504 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch)
505 VIDEO_VISIBLE_ROWS visible pixel rows
506 VIDEO_PIXEL_SIZE bytes per pixel
507 VIDEO_DATA_FORMAT graphic data format
508 (0-5, cf. cfb_console.c)
509 VIDEO_FB_ADRS framebuffer address
510 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init())
511 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc)
512 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc)
513 CONFIG_VIDEO_LOGO display Linux logo in upper left corner
514 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h
515 for logo. Requires CONFIG_VIDEO_LOGO
516 CONFIG_CONSOLE_EXTRA_INFO
517 additional board info beside
519 CONFIG_HIDE_LOGO_VERSION
520 do not display bootloader
523 When CONFIG_CFB_CONSOLE is defined, the video console is the
524 default console. The serial console can be forced by setting the
525 environment 'console=serial'.
527 config CFB_CONSOLE_ANSI
528 bool "Support ANSI escape sequences"
529 depends on CFB_CONSOLE
531 This allows the colour buffer frame buffer driver to support
532 a limited number of ANSI escape sequences (cursor control,
533 erase functions and limited graphics rendition control). Normal
534 output from U-Boot will pass through this filter.
536 config VGA_AS_SINGLE_DEVICE
537 bool "Set the video as an output-only device"
538 depends on CFB_CONSOLE
541 If enable the framebuffer device will be initialized as an
542 output-only device. The Keyboard driver will not be set up. This
543 may be used if you have no keyboard device, or more than one
544 (USB Keyboard, AT Keyboard).
546 config VIDEO_SW_CURSOR
547 bool "Enable a software cursor"
548 depends on CFB_CONSOLE
549 default y if CFB_CONSOLE
551 This draws a cursor after the last character. No blinking is
552 provided. This makes it possible to see the current cursor
553 position when entering text on the console. It is recommended to
556 config CONSOLE_EXTRA_INFO
557 bool "Display additional board information"
558 depends on CFB_CONSOLE
560 Display additional board information strings that normally go to
561 the serial port. When this option is enabled, a board-specific
562 function video_get_info_str() is called to get the string for
563 each line of the display. The function should return the string,
564 which can be empty if there is nothing to display for that line.
566 config CONSOLE_SCROLL_LINES
567 int "Number of lines to scroll the console by"
568 depends on CFB_CONSOLE || DM_VIDEO || LCD
571 When the console need to be scrolled, this is the number of
572 lines to scroll by. It defaults to 1. Increasing this makes the
573 console jump but can help speed up operation when scrolling
576 config SYS_CONSOLE_BG_COL
577 hex "Background colour"
578 depends on CFB_CONSOLE
581 Defines the background colour for the console. The value is from
582 0x00 to 0xff and the meaning depends on the graphics card.
583 Typically, 0x00 means black and 0xff means white. Do not set
584 the background and foreground to the same colour or you will see
587 config SYS_CONSOLE_FG_COL
588 hex "Foreground colour"
589 depends on CFB_CONSOLE
592 Defines the foreground colour for the console. The value is from
593 0x00 to 0xff and the meaning depends on the graphics card.
594 Typically, 0x00 means black and 0xff means white. Do not set
595 the background and foreground to the same colour or you will see
599 bool "Enable legacy LCD support"
601 Define this to enable LCD support (for output to LCD display).
602 You will also need to select an LCD driver using an additional
603 CONFIG option. See the README for details. Drives which have been
604 converted to driver model will instead used CONFIG_DM_VIDEO.
609 Enables the common driver code for the Designware HDMI TX
610 block found in SoCs from various vendors.
611 As this does not provide any functionality by itself (but
612 rather requires a SoC-specific glue driver to call it), it
613 can not be enabled from the configuration menu.