Kconfig 32 KB

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