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