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 18 bool "Enable panel backlight uclass support" 19 depends on DM_VIDEO 20 default y 21 help 22 This provides backlight uclass driver that enables basic panel 23 backlight support. 24 25config VIDEO_PCI_DEFAULT_FB_SIZE 26 hex "Default framebuffer size to use if no drivers request it" 27 depends on DM_VIDEO 28 default 0x1000000 if X86 && PCI 29 default 0 if !(X86 && PCI) 30 help 31 Generally, video drivers request the amount of memory they need for 32 the frame buffer when they are bound, by setting the size field in 33 struct video_uc_plat. That memory is then reserved for use after 34 relocation. But PCI drivers cannot be bound before relocation unless 35 they are mentioned in the devicetree. 36 37 With this value set appropriately, it is possible for PCI video 38 devices to have a framebuffer allocated by U-Boot. 39 40 Note: the framebuffer needs to be large enough to store all pixels at 41 maximum resolution. For example, at 1920 x 1200 with 32 bits per 42 pixel, 2560 * 1600 * 32 / 8 = 0xfa0000 bytes are needed. 43 44config VIDEO_COPY 45 bool "Enable copying the frame buffer to a hardware copy" 46 depends on DM_VIDEO 47 help 48 On some machines (e.g. x86), reading from the frame buffer is very 49 slow because it is uncached. To improve performance, this feature 50 allows the frame buffer to be kept in cached memory (allocated by 51 U-Boot) and then copied to the hardware frame-buffer as needed. 52 53 To use this, your video driver must set @copy_base in 54 struct video_uc_plat. 55 56config BACKLIGHT_PWM 57 bool "Generic PWM based Backlight Driver" 58 depends on BACKLIGHT && DM_PWM 59 default y 60 help 61 If you have a LCD backlight adjustable by PWM, say Y to enable 62 this driver. 63 This driver can be use with "simple-panel" and 64 it understands the standard device tree 65 (leds/backlight/pwm-backlight.txt) 66 67config BACKLIGHT_GPIO 68 bool "Generic GPIO based Backlight Driver" 69 depends on BACKLIGHT 70 help 71 If you have a LCD backlight adjustable by GPIO, say Y to enable 72 this driver. 73 This driver can be used with "simple-panel" and 74 it understands the standard device tree 75 (leds/backlight/gpio-backlight.txt) 76 77config CMD_VIDCONSOLE 78 bool "Enable vidconsole commands lcdputs and setcurs" 79 depends on DM_VIDEO 80 default y 81 help 82 Enabling this will provide 'setcurs' and 'lcdputs' commands which 83 support cursor positioning and drawing strings on video framebuffer. 84 85config VIDEO_BPP8 86 bool "Support 8-bit-per-pixel displays" 87 depends on DM_VIDEO 88 default y 89 help 90 Support drawing text and bitmaps onto a 8-bit-per-pixel display. 91 Enabling this will include code to support this display. Without 92 this option, such displays will not be supported and console output 93 will be empty. 94 95config VIDEO_BPP16 96 bool "Support 16-bit-per-pixel displays" 97 depends on DM_VIDEO 98 default y 99 help 100 Support drawing text and bitmaps onto a 16-bit-per-pixel display. 101 Enabling this will include code to support this display. Without 102 this option, such displays will not be supported and console output 103 will be empty. 104 105config VIDEO_BPP32 106 bool "Support 32-bit-per-pixel displays" 107 depends on DM_VIDEO 108 default y 109 help 110 Support drawing text and bitmaps onto a 32-bit-per-pixel display. 111 Enabling this will include code to support this display. Without 112 this option, such displays will not be supported and console output 113 will be empty. 114 115config VIDEO_ANSI 116 bool "Support ANSI escape sequences in video console" 117 depends on DM_VIDEO 118 default y 119 help 120 Enable ANSI escape sequence decoding for a more fully functional 121 console. 122 123config VIDEO_MIPI_DSI 124 bool "Support MIPI DSI interface" 125 depends on DM_VIDEO 126 help 127 Support MIPI DSI interface for driving a MIPI compatible device. 128 The MIPI Display Serial Interface (MIPI DSI) defines a high-speed 129 serial interface between a host processor and a display module. 130 131config CONSOLE_NORMAL 132 bool "Support a simple text console" 133 depends on DM_VIDEO 134 default y if DM_VIDEO 135 help 136 Support drawing text on the frame buffer console so that it can be 137 used as a console. Rotation is not supported by this driver (see 138 CONFIG_CONSOLE_ROTATION for that). A built-in 8x16 font is used 139 for the display. 140 141config CONSOLE_ROTATION 142 bool "Support rotated displays" 143 depends on DM_VIDEO 144 help 145 Sometimes, for example if the display is mounted in portrait 146 mode or even if it's mounted landscape but rotated by 180degree, 147 we need to rotate our content of the display relative to the 148 framebuffer, so that user can read the messages which are 149 printed out. Enable this option to include a text driver which can 150 support this. The rotation is set by the 'rot' parameter in 151 struct video_priv: 0=unrotated, 1=90 degrees clockwise, 2=180 152 degrees, 3=270 degrees. 153 154config CONSOLE_TRUETYPE 155 bool "Support a console that uses TrueType fonts" 156 depends on DM_VIDEO 157 help 158 TrueTrype fonts can provide outline-drawing capability rather than 159 needing to provide a bitmap for each font and size that is needed. 160 With this option you can adjust the text size and use a variety of 161 fonts. Note that this is noticeably slower than with normal console. 162 163config DM_PANEL_HX8238D 164 bool "Enable Himax HX-8238D LCD driver" 165 depends on DM_VIDEO 166 help 167 Support for HX-8238D LCD Panel 168 The HX8238-D is a single chip controller and driver LSI that 169 integrates the power circuit. 170 It can drive a maximum 960x240 dot graphics on a-TFT panel 171 displays in 16M colors with dithering. 172 173config CONSOLE_TRUETYPE_SIZE 174 int "TrueType font size" 175 depends on CONSOLE_TRUETYPE 176 default 18 177 help 178 This sets the font size for the console. The size is measured in 179 pixels and is the nominal height of a character. Note that fonts 180 are commonly measured in 'points', being 1/72 inch (about 3.52mm). 181 However that measurement depends on the size of your display and 182 there is no standard display density. At present there is not a 183 method to select the display's physical size, which would allow 184 U-Boot to calculate the correct font size. 185 186config SYS_WHITE_ON_BLACK 187 bool "Display console as white on a black background" 188 default y if ARCH_AT91 || ARCH_EXYNOS || ARCH_ROCKCHIP || ARCH_TEGRA || X86 || ARCH_SUNXI 189 help 190 Normally the display is black on a white background, Enable this 191 option to invert this, i.e. white on a black background. This can be 192 better in low-light situations or to reduce eye strain in some 193 cases. 194 195config NO_FB_CLEAR 196 bool "Skip framebuffer clear" 197 help 198 If firmware (whatever loads u-boot) has already put a splash image 199 on screen, you might want to preserve it until whatever u-boot 200 loads takes over the screen. This, for example, can be used to 201 keep splash image on screen until grub graphical boot menu starts. 202 203config PANEL 204 bool "Enable panel uclass support" 205 depends on DM_VIDEO 206 default y 207 help 208 This provides panel uclass driver that enables basic panel support. 209 210config SIMPLE_PANEL 211 bool "Enable simple panel support" 212 depends on PANEL && BACKLIGHT 213 default y 214 help 215 This turns on a simple panel driver that enables a compatible 216 video panel. 217 218source "drivers/video/fonts/Kconfig" 219 220config VIDCONSOLE_AS_LCD 221 bool "Use 'vidconsole' when CONFIG_VIDCONSOLE_AS_NAME string is seen in stdout" 222 depends on DM_VIDEO 223 help 224 This is a work-around for boards which have 'lcd' or 'vga' in their 225 stdout environment variable, but have moved to use driver model for 226 video. In this case the console will no-longer work. While it is 227 possible to update the environment, the breakage may be confusing for 228 users. This option will be removed around the end of 2020. 229 230config VIDCONSOLE_AS_NAME 231 string "Use 'vidconsole' when string defined here is seen in stdout" 232 depends on VIDCONSOLE_AS_LCD 233 default "lcd" if LCD || TEGRA_COMMON 234 default "vga" if !LCD 235 help 236 This is a work-around for boards which have 'lcd' or 'vga' in their 237 stdout environment variable, but have moved to use driver model for 238 video. In this case the console will no-longer work. While it is 239 possible to update the environment, the breakage may be confusing for 240 users. This option will be removed around the end of 2020. 241 242config VIDEO_COREBOOT 243 bool "Enable coreboot framebuffer driver support" 244 depends on X86 && SYS_COREBOOT 245 help 246 Turn on this option to enable a framebuffer driver when U-Boot is 247 loaded by coreboot where the graphics device is configured by 248 coreboot already. This can in principle be used with any platform 249 that coreboot supports. 250 251config VIDEO_EFI 252 bool "Enable EFI framebuffer driver support" 253 depends on EFI_STUB 254 help 255 Turn on this option to enable a framebuffeer driver when U-Boot is 256 loaded as a payload (see README.u-boot_on_efi) by an EFI BIOS where 257 the graphics device is configured by the EFI BIOS already. This can 258 in principle be used with any platform that has an EFI BIOS. 259 260config VIDEO_VESA 261 bool "Enable VESA video driver support" 262 default n 263 help 264 Turn on this option to enable a very simple driver which uses vesa 265 to discover the video mode and then provides a frame buffer for use 266 by U-Boot. This can in principle be used with any platform that 267 supports PCI and video cards that support VESA BIOS Extension (VBE). 268 269config FRAMEBUFFER_SET_VESA_MODE 270 bool "Set framebuffer graphics resolution" 271 depends on VIDEO_VESA || VIDEO_BROADWELL_IGD 272 help 273 Set VESA/native framebuffer mode (needed for bootsplash and graphical 274 framebuffer console) 275 276choice 277 prompt "framebuffer graphics resolution" 278 default FRAMEBUFFER_VESA_MODE_118 279 depends on FRAMEBUFFER_SET_VESA_MODE 280 help 281 This option sets the resolution used for the U-Boot framebuffer (and 282 bootsplash screen). 283 284config FRAMEBUFFER_VESA_MODE_100 285 bool "640x400 256-color" 286 287config FRAMEBUFFER_VESA_MODE_101 288 bool "640x480 256-color" 289 290config FRAMEBUFFER_VESA_MODE_102 291 bool "800x600 16-color" 292 293config FRAMEBUFFER_VESA_MODE_103 294 bool "800x600 256-color" 295 296config FRAMEBUFFER_VESA_MODE_104 297 bool "1024x768 16-color" 298 299config FRAMEBUFFER_VESA_MODE_105 300 bool "1024x768 256-color" 301 302config FRAMEBUFFER_VESA_MODE_106 303 bool "1280x1024 16-color" 304 305config FRAMEBUFFER_VESA_MODE_107 306 bool "1280x1024 256-color" 307 308config FRAMEBUFFER_VESA_MODE_108 309 bool "80x60 text" 310 311config FRAMEBUFFER_VESA_MODE_109 312 bool "132x25 text" 313 314config FRAMEBUFFER_VESA_MODE_10A 315 bool "132x43 text" 316 317config FRAMEBUFFER_VESA_MODE_10B 318 bool "132x50 text" 319 320config FRAMEBUFFER_VESA_MODE_10C 321 bool "132x60 text" 322 323config FRAMEBUFFER_VESA_MODE_10D 324 bool "320x200 32k-color (1:5:5:5)" 325 326config FRAMEBUFFER_VESA_MODE_10E 327 bool "320x200 64k-color (5:6:5)" 328 329config FRAMEBUFFER_VESA_MODE_10F 330 bool "320x200 16.8M-color (8:8:8)" 331 332config FRAMEBUFFER_VESA_MODE_110 333 bool "640x480 32k-color (1:5:5:5)" 334 335config FRAMEBUFFER_VESA_MODE_111 336 bool "640x480 64k-color (5:6:5)" 337 338config FRAMEBUFFER_VESA_MODE_112 339 bool "640x480 16.8M-color (8:8:8)" 340 341config FRAMEBUFFER_VESA_MODE_113 342 bool "800x600 32k-color (1:5:5:5)" 343 344config FRAMEBUFFER_VESA_MODE_114 345 bool "800x600 64k-color (5:6:5)" 346 347config FRAMEBUFFER_VESA_MODE_115 348 bool "800x600 16.8M-color (8:8:8)" 349 350config FRAMEBUFFER_VESA_MODE_116 351 bool "1024x768 32k-color (1:5:5:5)" 352 353config FRAMEBUFFER_VESA_MODE_117 354 bool "1024x768 64k-color (5:6:5)" 355 356config FRAMEBUFFER_VESA_MODE_118 357 bool "1024x768 16.8M-color (8:8:8)" 358 359config FRAMEBUFFER_VESA_MODE_119 360 bool "1280x1024 32k-color (1:5:5:5)" 361 362config FRAMEBUFFER_VESA_MODE_11A 363 bool "1280x1024 64k-color (5:6:5)" 364 365config FRAMEBUFFER_VESA_MODE_11B 366 bool "1280x1024 16.8M-color (8:8:8)" 367 368config FRAMEBUFFER_VESA_MODE_USER 369 bool "Manually select VESA mode" 370 371endchoice 372 373# Map the config names to an integer (KB). 374config FRAMEBUFFER_VESA_MODE 375 prompt "VESA mode" if FRAMEBUFFER_VESA_MODE_USER 376 hex 377 default 0x100 if FRAMEBUFFER_VESA_MODE_100 378 default 0x101 if FRAMEBUFFER_VESA_MODE_101 379 default 0x102 if FRAMEBUFFER_VESA_MODE_102 380 default 0x103 if FRAMEBUFFER_VESA_MODE_103 381 default 0x104 if FRAMEBUFFER_VESA_MODE_104 382 default 0x105 if FRAMEBUFFER_VESA_MODE_105 383 default 0x106 if FRAMEBUFFER_VESA_MODE_106 384 default 0x107 if FRAMEBUFFER_VESA_MODE_107 385 default 0x108 if FRAMEBUFFER_VESA_MODE_108 386 default 0x109 if FRAMEBUFFER_VESA_MODE_109 387 default 0x10A if FRAMEBUFFER_VESA_MODE_10A 388 default 0x10B if FRAMEBUFFER_VESA_MODE_10B 389 default 0x10C if FRAMEBUFFER_VESA_MODE_10C 390 default 0x10D if FRAMEBUFFER_VESA_MODE_10D 391 default 0x10E if FRAMEBUFFER_VESA_MODE_10E 392 default 0x10F if FRAMEBUFFER_VESA_MODE_10F 393 default 0x110 if FRAMEBUFFER_VESA_MODE_110 394 default 0x111 if FRAMEBUFFER_VESA_MODE_111 395 default 0x112 if FRAMEBUFFER_VESA_MODE_112 396 default 0x113 if FRAMEBUFFER_VESA_MODE_113 397 default 0x114 if FRAMEBUFFER_VESA_MODE_114 398 default 0x115 if FRAMEBUFFER_VESA_MODE_115 399 default 0x116 if FRAMEBUFFER_VESA_MODE_116 400 default 0x117 if FRAMEBUFFER_VESA_MODE_117 401 default 0x118 if FRAMEBUFFER_VESA_MODE_118 402 default 0x119 if FRAMEBUFFER_VESA_MODE_119 403 default 0x11A if FRAMEBUFFER_VESA_MODE_11A 404 default 0x11B if FRAMEBUFFER_VESA_MODE_11B 405 default 0x117 if FRAMEBUFFER_VESA_MODE_USER 406 407config VIDEO_LCD_ANX9804 408 bool "ANX9804 bridge chip" 409 default n 410 ---help--- 411 Support for the ANX9804 bridge chip, which can take pixel data coming 412 from a parallel LCD interface and translate it on the fy into a DP 413 interface for driving eDP TFT displays. It uses I2C for configuration. 414 415config VIDEO_LCD_ORISETECH_OTM8009A 416 bool "OTM8009A DSI LCD panel support" 417 depends on DM_VIDEO 418 select VIDEO_MIPI_DSI 419 default n 420 help 421 Say Y here if you want to enable support for Orise Technology 422 otm8009a 480x800 dsi 2dl panel. 423 424config VIDEO_LCD_RAYDIUM_RM68200 425 bool "RM68200 DSI LCD panel support" 426 depends on DM_VIDEO 427 select VIDEO_MIPI_DSI 428 default n 429 help 430 Say Y here if you want to enable support for Raydium RM68200 431 720x1280 DSI video mode panel. 432 433config VIDEO_LCD_SSD2828 434 bool "SSD2828 bridge chip" 435 default n 436 ---help--- 437 Support for the SSD2828 bridge chip, which can take pixel data coming 438 from a parallel LCD interface and translate it on the fly into MIPI DSI 439 interface for driving a MIPI compatible LCD panel. It uses SPI for 440 configuration. 441 442config VIDEO_LCD_SSD2828_TX_CLK 443 int "SSD2828 TX_CLK frequency (in MHz)" 444 depends on VIDEO_LCD_SSD2828 445 default 0 446 ---help--- 447 The frequency of the crystal, which is clocking SSD2828. It may be 448 anything in the 8MHz-30MHz range and the exact value should be 449 retrieved from the board schematics. Or in the case of Allwinner 450 hardware, it can be usually found as 'lcd_xtal_freq' variable in 451 FEX files. It can be also set to 0 for selecting PCLK from the 452 parallel LCD interface instead of TX_CLK as the PLL clock source. 453 454config VIDEO_LCD_SSD2828_RESET 455 string "RESET pin of SSD2828" 456 depends on VIDEO_LCD_SSD2828 457 default "" 458 ---help--- 459 The reset pin of SSD2828 chip. This takes a string in the format 460 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 461 462config VIDEO_LCD_TDO_TL070WSH30 463 bool "TDO TL070WSH30 DSI LCD panel support" 464 depends on DM_VIDEO 465 select VIDEO_MIPI_DSI 466 default n 467 help 468 Say Y here if you want to enable support for TDO TL070WSH30 469 1024x600 DSI video mode panel. 470 471config VIDEO_LCD_HITACHI_TX18D42VM 472 bool "Hitachi tx18d42vm LVDS LCD panel support" 473 depends on VIDEO 474 default n 475 ---help--- 476 Support for Hitachi tx18d42vm LVDS LCD panels, these panels have a 477 lcd controller which needs to be initialized over SPI, once that is 478 done they work like a regular LVDS panel. 479 480config VIDEO_LCD_SPI_CS 481 string "SPI CS pin for LCD related config job" 482 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 483 default "" 484 ---help--- 485 This is one of the SPI communication pins, involved in setting up a 486 working LCD configuration. The exact role of SPI may differ for 487 different hardware setups. The option takes a string in the format 488 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 489 490config VIDEO_LCD_SPI_SCLK 491 string "SPI SCLK pin for LCD related config job" 492 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 493 default "" 494 ---help--- 495 This is one of the SPI communication pins, involved in setting up a 496 working LCD configuration. The exact role of SPI may differ for 497 different hardware setups. The option takes a string in the format 498 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 499 500config VIDEO_LCD_SPI_MOSI 501 string "SPI MOSI pin for LCD related config job" 502 depends on VIDEO_LCD_SSD2828 || VIDEO_LCD_HITACHI_TX18D42VM 503 default "" 504 ---help--- 505 This is one of the SPI communication pins, involved in setting up a 506 working LCD configuration. The exact role of SPI may differ for 507 different hardware setups. The option takes a string in the format 508 understood by 'name_to_gpio' function, e.g. PH1 for pin 1 of port H. 509 510config VIDEO_LCD_SPI_MISO 511 string "SPI MISO pin for LCD related config job (optional)" 512 depends on VIDEO_LCD_SSD2828 513 default "" 514 ---help--- 515 This is one of the SPI communication pins, involved in setting up a 516 working LCD configuration. The exact role of SPI may differ for 517 different hardware setups. If wired up, this pin may provide additional 518 useful functionality. Such as bi-directional communication with the 519 hardware and LCD panel id retrieval (if the panel can report it). The 520 option takes a string in the format understood by 'name_to_gpio' 521 function, e.g. PH1 for pin 1 of port H. 522 523source "drivers/video/meson/Kconfig" 524 525config VIDEO_MVEBU 526 bool "Armada XP LCD controller" 527 default n 528 ---help--- 529 Support for the LCD controller integrated in the Marvell 530 Armada XP SoC. 531 532config VIDEO_OMAP3 533 bool "Enable OMAP3+ DSS Support" 534 depends on ARCH_OMAP2PLUS 535 help 536 This enables the Display subsystem (DSS) on OMAP3+ boards. 537 538config I2C_EDID 539 bool "Enable EDID library" 540 default n 541 help 542 This enables library for accessing EDID data from an LCD panel. 543 544config DISPLAY 545 bool "Enable Display support" 546 depends on DM 547 default n 548 select I2C_EDID 549 help 550 This supports drivers that provide a display, such as eDP (Embedded 551 DisplayPort) and HDMI (High Definition Multimedia Interface). 552 The devices provide a simple interface to start up the display, 553 read display information and enable it. 554 555config NXP_TDA19988 556 bool "Enable NXP TDA19988 support" 557 depends on DISPLAY 558 default n 559 help 560 This enables support for the NXP TDA19988 HDMI encoder. This encoder 561 will convert RGB data streams into HDMI-encoded signals. 562 563config ATMEL_HLCD 564 bool "Enable ATMEL video support using HLCDC" 565 help 566 HLCDC supports video output to an attached LCD panel. 567 568source "drivers/video/ti/Kconfig" 569 570config LOGICORE_DP_TX 571 bool "Enable Logicore DP TX driver" 572 depends on DISPLAY 573 help 574 Enable the driver for the transmitter part of the Xilinx LogiCORE 575 DisplayPort, a IP core for Xilinx FPGAs that implements a DisplayPort 576 video interface as defined by VESA DisplayPort v1.2. 577 578 Note that this is a pure transmitter device, and has no display 579 capabilities by itself. 580 581config VIDEO_BROADWELL_IGD 582 bool "Enable Intel Broadwell integrated graphics device" 583 depends on X86 584 help 585 This enables support for integrated graphics on Intel broadwell 586 devices. Initialisation is mostly performed by a VGA boot ROM, with 587 some setup handled by U-Boot itself. The graphics adaptor works as 588 a VESA device and supports LCD panels, eDP and LVDS outputs. 589 Configuration of most aspects of device operation is performed using 590 a special tool which configures the VGA ROM, but the graphics 591 resolution can be selected in U-Boot. 592 593config VIDEO_IVYBRIDGE_IGD 594 bool "Enable Intel Ivybridge integration graphics support" 595 depends on X86 596 help 597 This enables support for integrated graphics on Intel ivybridge 598 devices. Initialisation is mostly performed by a VGA boot ROM, with 599 some setup handled by U-Boot itself. The graphics adaptor works as 600 a VESA device and supports LCD panels, eDP and LVDS outputs. 601 Configuration of most aspects of device operation is performed using 602 a special tool which configures the VGA ROM, but the graphics 603 resolution can be selected in U-Boot. 604 605config VIDEO_FSL_DCU_FB 606 bool "Enable Freescale Display Control Unit" 607 depends on VIDEO || DM_VIDEO 608 help 609 This enables support for Freescale Display Control Unit (DCU4) 610 module found on Freescale Vybrid and QorIQ family of SoCs. 611 612config VIDEO_FSL_DCU_MAX_FB_SIZE_MB 613 int "Freescale DCU framebuffer size" 614 depends on VIDEO_FSL_DCU_FB 615 default 4194304 616 help 617 Set maximum framebuffer size to be used for Freescale Display 618 Controller Unit (DCU4). 619 620source "drivers/video/rockchip/Kconfig" 621 622config VIDEO_ARM_MALIDP 623 bool "Enable Arm Mali Display Processor support" 624 depends on DM_VIDEO && OF_CONTROL 625 select VEXPRESS_CLK 626 help 627 This enables support for Arm Ltd Mali Display Processors from 628 the DP500, DP550 and DP650 family. 629 630config VIDEO_SANDBOX_SDL 631 bool "Enable sandbox video console using SDL" 632 depends on SANDBOX 633 help 634 When using sandbox you can enable an emulated LCD display which 635 appears as an SDL (Simple DirectMedia Layer) window. This is a 636 console device and can display stdout output. Within U-Boot is is 637 a normal bitmap display and can display images as well as text. 638 639source "drivers/video/stm32/Kconfig" 640 641config VIDEO_TEGRA20 642 bool "Enable LCD support on Tegra20" 643 depends on OF_CONTROL 644 help 645 Tegra20 supports video output to an attached LCD panel as well as 646 other options such as HDMI. Only the LCD is supported in U-Boot. 647 This option enables this support which can be used on devices which 648 have an LCD display connected. 649 650config VIDEO_TEGRA124 651 bool "Enable video support on Tegra124" 652 depends on DM_VIDEO 653 help 654 Tegra124 supports many video output options including eDP and 655 HDMI. At present only eDP is supported by U-Boot. This option 656 enables this support which can be used on devices which 657 have an eDP display connected. 658 659source "drivers/video/bridge/Kconfig" 660 661source "drivers/video/imx/Kconfig" 662 663config VIDEO_NX 664 bool "Enable video support on Nexell SoC" 665 depends on ARCH_S5P6818 || ARCH_S5P4418 666 help 667 Nexell SoC supports many video output options including eDP and 668 HDMI. This option enables this support which can be used on devices 669 which have an eDP display connected. 670 671config VIDEO_SEPS525 672 bool "Enable video support for Seps525" 673 depends on DM_VIDEO 674 help 675 Enable support for the Syncoam PM-OLED display driver (RGB 160x128). 676 Currently driver is supporting only SPI interface. 677 678source "drivers/video/nexell/Kconfig" 679 680config VIDEO 681 bool "Enable legacy video support" 682 depends on !DM_VIDEO 683 help 684 Define this for video support, without using driver model. Some 685 drivers use this because they are not yet converted to driver 686 model. Video drivers typically provide a colour text console and 687 cursor. 688 689config CFB_CONSOLE 690 bool "Enable colour frame buffer console" 691 depends on VIDEO || ARCH_OMAP2PLUS 692 default y if VIDEO 693 help 694 Enables the colour frame buffer driver. This supports colour 695 output on a bitmap display from an in-memory frame buffer. 696 Several colour devices are supported along with various options to 697 adjust the supported features. The driver is implemented in 698 cfb_console.c 699 700 The following defines are needed (cf. smiLynxEM, i8042) 701 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation 702 (default big endian) 703 VIDEO_HW_RECTFILL graphic chip supports 704 rectangle fill (cf. smiLynxEM) 705 VIDEO_HW_BITBLT graphic chip supports 706 bit-blit (cf. smiLynxEM) 707 VIDEO_VISIBLE_COLS visible pixel columns (cols=pitch) 708 VIDEO_VISIBLE_ROWS visible pixel rows 709 VIDEO_PIXEL_SIZE bytes per pixel 710 VIDEO_DATA_FORMAT graphic data format 711 (0-5, cf. cfb_console.c) 712 VIDEO_FB_ADRS framebuffer address 713 VIDEO_KBD_INIT_FCT keyboard int fct (i.e. rx51_kp_init()) 714 VIDEO_TSTC_FCT test char fct (i.e. rx51_kp_tstc) 715 VIDEO_GETC_FCT get char fct (i.e. rx51_kp_getc) 716 CONFIG_VIDEO_LOGO display Linux logo in upper left corner 717 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of linux_logo.h 718 for logo. Requires CONFIG_VIDEO_LOGO 719 CONFIG_CONSOLE_EXTRA_INFO 720 additional board info beside 721 the logo 722 CONFIG_HIDE_LOGO_VERSION 723 do not display bootloader 724 version string 725 726 When CONFIG_CFB_CONSOLE is defined, the video console is the 727 default console. The serial console can be forced by setting the 728 environment 'console=serial'. 729 730config CFB_CONSOLE_ANSI 731 bool "Support ANSI escape sequences" 732 depends on CFB_CONSOLE 733 help 734 This allows the colour buffer frame buffer driver to support 735 a limited number of ANSI escape sequences (cursor control, 736 erase functions and limited graphics rendition control). Normal 737 output from U-Boot will pass through this filter. 738 739config VGA_AS_SINGLE_DEVICE 740 bool "Set the video as an output-only device" 741 depends on CFB_CONSOLE 742 default y 743 help 744 If enable the framebuffer device will be initialized as an 745 output-only device. The Keyboard driver will not be set up. This 746 may be used if you have no keyboard device, or more than one 747 (USB Keyboard, AT Keyboard). 748 749config VIDEO_SW_CURSOR 750 bool "Enable a software cursor" 751 depends on CFB_CONSOLE 752 default y if CFB_CONSOLE 753 help 754 This draws a cursor after the last character. No blinking is 755 provided. This makes it possible to see the current cursor 756 position when entering text on the console. It is recommended to 757 enable this. 758 759config CONSOLE_EXTRA_INFO 760 bool "Display additional board information" 761 depends on CFB_CONSOLE 762 help 763 Display additional board information strings that normally go to 764 the serial port. When this option is enabled, a board-specific 765 function video_get_info_str() is called to get the string for 766 each line of the display. The function should return the string, 767 which can be empty if there is nothing to display for that line. 768 769config CONSOLE_SCROLL_LINES 770 int "Number of lines to scroll the console by" 771 depends on CFB_CONSOLE || DM_VIDEO || LCD 772 default 1 773 help 774 When the console need to be scrolled, this is the number of 775 lines to scroll by. It defaults to 1. Increasing this makes the 776 console jump but can help speed up operation when scrolling 777 is slow. 778 779config SYS_CONSOLE_BG_COL 780 hex "Background colour" 781 depends on CFB_CONSOLE 782 default 0x00 783 help 784 Defines the background colour for the console. The value is from 785 0x00 to 0xff and the meaning depends on the graphics card. 786 Typically, 0x00 means black and 0xff means white. Do not set 787 the background and foreground to the same colour or you will see 788 nothing. 789 790config SYS_CONSOLE_FG_COL 791 hex "Foreground colour" 792 depends on CFB_CONSOLE 793 default 0xa0 794 help 795 Defines the foreground colour for the console. The value is from 796 0x00 to 0xff and the meaning depends on the graphics card. 797 Typically, 0x00 means black and 0xff means white. Do not set 798 the background and foreground to the same colour or you will see 799 nothing. 800 801config LCD 802 bool "Enable legacy LCD support" 803 help 804 Define this to enable LCD support (for output to LCD display). 805 You will also need to select an LCD driver using an additional 806 CONFIG option. See the README for details. Drives which have been 807 converted to driver model will instead used CONFIG_DM_VIDEO. 808 809config VIDEO_DW_HDMI 810 bool 811 help 812 Enables the common driver code for the Designware HDMI TX 813 block found in SoCs from various vendors. 814 As this does not provide any functionality by itself (but 815 rather requires a SoC-specific glue driver to call it), it 816 can not be enabled from the configuration menu. 817 818config VIDEO_DSI_HOST_SANDBOX 819 bool "Enable sandbox for dsi host" 820 depends on SANDBOX 821 select VIDEO_MIPI_DSI 822 help 823 Enable support for sandbox dsi host device used for testing 824 purposes. 825 Display Serial Interface (DSI) defines a serial bus and 826 a communication protocol between the host and the device 827 (panel, bridge). 828 829config VIDEO_DW_MIPI_DSI 830 bool 831 select VIDEO_MIPI_DSI 832 help 833 Enables the common driver code for the Synopsis Designware 834 MIPI DSI block found in SoCs from various vendors. 835 As this does not provide any functionality by itself (but 836 rather requires a SoC-specific glue driver to call it), it 837 can not be enabled from the configuration menu. 838 839config VIDEO_SIMPLE 840 bool "Simple display driver for preconfigured display" 841 help 842 Enables a simple generic display driver which utilizes the 843 simple-framebuffer devicetree bindings. 844 845 This driver assumes that the display hardware has been initialized 846 before u-boot starts, and u-boot will simply render to the pre- 847 allocated frame buffer surface. 848 849config VIDEO_DT_SIMPLEFB 850 bool "Enable SimpleFB support for passing framebuffer to OS" 851 help 852 Enables the code to pass the framebuffer to the kernel as a 853 simple framebuffer in the device tree. 854 The video output is initialized by U-Boot, and kept by the 855 kernel. 856 857config OSD 858 bool "Enable OSD support" 859 depends on DM 860 default n 861 help 862 This supports drivers that provide a OSD (on-screen display), which 863 is a (usually text-oriented) graphics buffer to show information on 864 a display. 865 866config SANDBOX_OSD 867 bool "Enable sandbox OSD" 868 depends on OSD 869 help 870 Enable support for sandbox OSD device used for testing purposes. 871 872config IHS_VIDEO_OUT 873 bool "Enable IHS video out driver" 874 depends on OSD 875 help 876 Enable support for the gdsys Integrated Hardware Systems (IHS) video 877 out On-screen Display (OSD) used on gdsys FPGAs to control dynamic 878 textual overlays of the display outputs. 879 880config SPLASH_SCREEN 881 bool "Show a splash-screen image" 882 help 883 If this option is set, the environment is checked for a variable 884 "splashimage". If found, the usual display of logo, copyright and 885 system information on the LCD is suppressed and the BMP image at the 886 address specified in "splashimage" is loaded instead. The console is 887 redirected to the "nulldev", too. This allows for a "silent" boot 888 where a splash screen is loaded very quickly after power-on. 889 890 The splash_screen_prepare() function is a weak function defined in 891 common/splash.c. It is called as part of the splash screen display 892 sequence. It gives the board an opportunity to prepare the splash 893 image data before it is processed and sent to the frame buffer by 894 U-Boot. Define your own version to use this feature. 895 896config SPLASHIMAGE_GUARD 897 bool "Support unaligned BMP images" 898 depends on SPLASH_SCREEN 899 help 900 If this option is set, then U-Boot will prevent the environment 901 variable "splashimage" from being set to a problematic address 902 (see doc/README.displaying-bmps). 903 904 This option is useful for targets where, due to alignment 905 restrictions, an improperly aligned BMP image will cause a data 906 abort. If you think you will not have problems with unaligned 907 accesses (for example because your toolchain prevents them) 908 there is no need to set this option. 909 910config SPLASH_SCREEN_ALIGN 911 bool "Allow positioning the splash image anywhere on the display" 912 depends on SPLASH_SCREEN || CMD_BMP 913 help 914 If this option is set the splash image can be freely positioned 915 on the screen. Environment variable "splashpos" specifies the 916 position as "x,y". If a positive number is given it is used as 917 number of pixel from left/top. If a negative number is given it 918 is used as number of pixel from right/bottom. You can also 919 specify 'm' for centering the image. 920 921 Example: 922 setenv splashpos m,m 923 => image at center of screen 924 925 setenv splashpos 30,20 926 => image at x = 30 and y = 20 927 928 setenv splashpos -10,m 929 => vertically centered image 930 at x = dspWidth - bmpWidth - 9 931 932config SPLASH_SOURCE 933 bool "Control the source of the splash image" 934 depends on SPLASH_SCREEN 935 help 936 Use the splash_source.c library. This library provides facilities to 937 declare board specific splash image locations, routines for loading 938 splash image from supported locations, and a way of controlling the 939 selected splash location using the "splashsource" environment 940 variable. 941 942 This CONFIG works as follows: 943 944 - If splashsource is set to a supported location name as defined by 945 board code, use that splash location. 946 - If splashsource is undefined, use the first splash location as 947 default. 948 - If splashsource is set to an unsupported value, do not load a splash 949 screen. 950 951 A splash source location can describe either storage with raw data, a 952 storage formatted with a file system or a FIT image. In case of a 953 filesystem, the splash screen data is loaded as a file. The name of 954 the splash screen file can be controlled with the environment variable 955 "splashfile". 956 957 To enable loading the splash image from a FIT image, CONFIG_FIT must 958 be enabled. The FIT image has to start at the 'offset' field address 959 in the selected splash location. The name of splash image within the 960 FIT shall be specified by the environment variable "splashfile". 961 962 In case the environment variable "splashfile" is not defined the 963 default name 'splash.bmp' will be used. 964 965config VIDEO_BMP_GZIP 966 bool "Gzip compressed BMP image support" 967 depends on CMD_BMP || SPLASH_SCREEN 968 help 969 If this option is set, additionally to standard BMP 970 images, gzipped BMP images can be displayed via the 971 splashscreen support or the bmp command. 972 973config VIDEO_BMP_RLE8 974 bool "Run length encoded BMP image (RLE8) support" 975 depends on DM_VIDEO || CFB_CONSOLE 976 help 977 If this option is set, the 8-bit RLE compressed BMP images 978 is supported. 979 980config BMP_16BPP 981 bool "16-bit-per-pixel BMP image support" 982 depends on DM_VIDEO || LCD 983 help 984 Support display of bitmaps file with 16-bit-per-pixel 985 986config BMP_24BPP 987 bool "24-bit-per-pixel BMP image support" 988 depends on DM_VIDEO || LCD 989 help 990 Support display of bitmaps file with 24-bit-per-pixel. 991 992config BMP_32BPP 993 bool "32-bit-per-pixel BMP image support" 994 depends on DM_VIDEO || LCD 995 help 996 Support display of bitmaps file with 32-bit-per-pixel. 997 998config VIDEO_VCXK 999 bool "Enable VCXK video controller driver support" 1000 default n 1001 help 1002 This enables VCXK driver which can be used with VC2K, VC4K 1003 and VC8K devices on various boards from BuS Elektronik GmbH. 1004 1005endmenu 1006
