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