Kconfig 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508
  1. menu "Command line interface"
  2. config HUSH_PARSER
  3. bool "Use hush shell"
  4. select SYS_HUSH_PARSER
  5. help
  6. This option enables the "hush" shell (from Busybox) as command line
  7. interpreter, thus enabling powerful command line syntax like
  8. if...then...else...fi conditionals or `&&' and '||'
  9. constructs ("shell scripts").
  10. If disabled, you get the old, much simpler behaviour with a somewhat
  11. smaller memory footprint.
  12. config SYS_HUSH_PARSER
  13. bool
  14. help
  15. Backward compatibility.
  16. comment "Commands"
  17. menu "Info commands"
  18. config CMD_BDI
  19. bool "bdinfo"
  20. help
  21. Print board info
  22. config CMD_CONSOLE
  23. bool "coninfo"
  24. help
  25. Print console devices and information.
  26. config CMD_CPU
  27. bool "cpu"
  28. help
  29. Print information about available CPUs. This normally shows the
  30. number of CPUs, type (e.g. manufacturer, architecture, product or
  31. internal name) and clock frequency. Other information may be
  32. available depending on the CPU driver.
  33. config CMD_LICENSE
  34. bool "license"
  35. help
  36. Print GPL license text
  37. endmenu
  38. menu "Boot commands"
  39. config CMD_BOOTD
  40. bool "bootd"
  41. help
  42. Run the command stored in the environment "bootcmd", i.e.
  43. "bootd" does the same thing as "run bootcmd".
  44. config CMD_BOOTM
  45. bool "bootm"
  46. default y
  47. help
  48. Boot an application image from the memory.
  49. config CMD_GO
  50. bool "go"
  51. default y
  52. help
  53. Start an application at a given address.
  54. config CMD_RUN
  55. bool "run"
  56. help
  57. Run the command in the given environment variable.
  58. config CMD_IMI
  59. bool "iminfo"
  60. help
  61. Print header information for application image.
  62. config CMD_IMLS
  63. bool "imls"
  64. help
  65. List all images found in flash
  66. config CMD_XIMG
  67. bool "imxtract"
  68. help
  69. Extract a part of a multi-image.
  70. endmenu
  71. menu "Environment commands"
  72. config CMD_EXPORTENV
  73. bool "env export"
  74. default y
  75. help
  76. Export environments.
  77. config CMD_IMPORTENV
  78. bool "env import"
  79. default y
  80. help
  81. Import environments.
  82. config CMD_EDITENV
  83. bool "editenv"
  84. help
  85. Edit environment variable.
  86. config CMD_SAVEENV
  87. bool "saveenv"
  88. help
  89. Run the command in the given environment variable.
  90. endmenu
  91. menu "Memory commands"
  92. config CMD_MEMORY
  93. bool "md, mm, nm, mw, cp, cmp, base, loop"
  94. help
  95. Memeory commands.
  96. md - memory display
  97. mm - memory modify (auto-incrementing address)
  98. nm - memory modify (constant address)
  99. mw - memory write (fill)
  100. cp - memory copy
  101. cmp - memory compare
  102. base - print or set address offset
  103. loop - initinite loop on address range
  104. config CMD_CRC32
  105. bool "crc32"
  106. default y
  107. help
  108. Compute CRC32.
  109. config LOOPW
  110. bool "loopw"
  111. help
  112. Infinite write loop on address range
  113. config CMD_MEMTEST
  114. bool "memtest"
  115. help
  116. Simple RAM read/write test.
  117. config CMD_MX_CYCLIC
  118. bool "mdc, mwc"
  119. help
  120. mdc - memory display cyclic
  121. mwc - memory write cyclic
  122. config CMD_MEMINFO
  123. bool "meminfo"
  124. help
  125. Display memory information.
  126. endmenu
  127. menu "Device access commands"
  128. config CMD_DM
  129. bool "dm - Access to driver model information"
  130. depends on DM
  131. default y
  132. help
  133. Provides access to driver model data structures and information,
  134. such as a list of devices, list of uclasses and the state of each
  135. device (e.g. activated). This is not required for operation, but
  136. can be useful to see the state of driver model for debugging or
  137. interest.
  138. config CMD_DEMO
  139. bool "demo - Demonstration commands for driver model"
  140. depends on DM
  141. help
  142. Provides a 'demo' command which can be used to play around with
  143. driver model. To use this properly you will need to enable one or
  144. both of the demo devices (DM_DEMO_SHAPE and DM_DEMO_SIMPLE).
  145. Otherwise you will always get an empty list of devices. The demo
  146. devices are defined in the sandbox device tree, so the easiest
  147. option is to use sandbox and pass the -d point to sandbox's
  148. u-boot.dtb file.
  149. config CMD_LOADB
  150. bool "loadb"
  151. help
  152. Load a binary file over serial line.
  153. config CMD_LOADS
  154. bool "loads"
  155. help
  156. Load an S-Record file over serial line
  157. config CMD_FLASH
  158. bool "flinfo, erase, protect"
  159. help
  160. NOR flash support.
  161. flinfo - print FLASH memory information
  162. erase - FLASH memory
  163. protect - enable or disable FLASH write protection
  164. config CMD_ARMFLASH
  165. depends on FLASH_CFI_DRIVER
  166. bool "armflash"
  167. help
  168. ARM Ltd reference designs flash partition access
  169. config CMD_NAND
  170. bool "nand"
  171. help
  172. NAND support.
  173. config CMD_SPI
  174. bool "sspi"
  175. help
  176. SPI utility command.
  177. config CMD_I2C
  178. bool "i2c"
  179. help
  180. I2C support.
  181. config CMD_USB
  182. bool "usb"
  183. help
  184. USB support.
  185. config CMD_FPGA
  186. bool "fpga"
  187. help
  188. FPGA support.
  189. endmenu
  190. menu "Shell scripting commands"
  191. config CMD_ECHO
  192. bool "echo"
  193. help
  194. Echo args to console
  195. config CMD_ITEST
  196. bool "itest"
  197. help
  198. Return true/false on integer compare.
  199. config CMD_SOURCE
  200. bool "source"
  201. help
  202. Run script from memory
  203. config CMD_SETEXPR
  204. bool "setexpr"
  205. help
  206. Evaluate boolean and math expressions and store the result in an env
  207. variable.
  208. Also supports loading the value at a memory location into a variable.
  209. If CONFIG_REGEX is enabled, setexpr also supports a gsub function.
  210. endmenu
  211. menu "Network commands"
  212. config CMD_NET
  213. bool "bootp, tftpboot"
  214. select NET
  215. help
  216. Network commands.
  217. bootp - boot image via network using BOOTP/TFTP protocol
  218. tftpboot - boot image via network using TFTP protocol
  219. config CMD_TFTPPUT
  220. bool "tftp put"
  221. help
  222. TFTP put command, for uploading files to a server
  223. config CMD_TFTPSRV
  224. bool "tftpsrv"
  225. help
  226. Act as a TFTP server and boot the first received file
  227. config CMD_RARP
  228. bool "rarpboot"
  229. help
  230. Boot image via network using RARP/TFTP protocol
  231. config CMD_DHCP
  232. bool "dhcp"
  233. help
  234. Boot image via network using DHCP/TFTP protocol
  235. config CMD_NFS
  236. bool "nfs"
  237. help
  238. Boot image via network using NFS protocol.
  239. config CMD_PING
  240. bool "ping"
  241. help
  242. Send ICMP ECHO_REQUEST to network host
  243. config CMD_CDP
  244. bool "cdp"
  245. help
  246. Perform CDP network configuration
  247. config CMD_SNTP
  248. bool "sntp"
  249. help
  250. Synchronize RTC via network
  251. config CMD_DNS
  252. bool "dns"
  253. help
  254. Lookup the IP of a hostname
  255. config CMD_LINK_LOCAL
  256. bool "linklocal"
  257. help
  258. Acquire a network IP address using the link-local protocol
  259. endmenu
  260. menu "Misc commands"
  261. config CMD_TIME
  262. bool "time"
  263. help
  264. Run commands and summarize execution time.
  265. # TODO: rename to CMD_SLEEP
  266. config CMD_MISC
  267. bool "sleep"
  268. help
  269. Delay execution for some time
  270. config CMD_TIMER
  271. bool "timer"
  272. help
  273. Access the system timer.
  274. config CMD_SETGETDCR
  275. bool "getdcr, setdcr, getidcr, setidcr"
  276. depends on 4xx
  277. help
  278. getdcr - Get an AMCC PPC 4xx DCR's value
  279. setdcr - Set an AMCC PPC 4xx DCR's value
  280. getidcr - Get a register value via indirect DCR addressing
  281. setidcr - Set a register value via indirect DCR addressing
  282. config CMD_SOUND
  283. bool "sound"
  284. depends on SOUND
  285. help
  286. This provides basic access to the U-Boot's sound support. The main
  287. feature is to play a beep.
  288. sound init - set up sound system
  289. sound play - play a sound
  290. endmenu
  291. menu "Boot timing"
  292. config BOOTSTAGE
  293. bool "Boot timing and reporting"
  294. help
  295. Enable recording of boot time while booting. To use it, insert
  296. calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
  297. bootstage.h. Only a single entry is recorded for each ID. You can
  298. give the entry a name with bootstage_mark_name(). You can also
  299. record elapsed time in a particular stage using bootstage_start()
  300. before starting and bootstage_accum() when finished. Bootstage will
  301. add up all the accumated time and report it.
  302. Normally, IDs are defined in bootstage.h but a small number of
  303. additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
  304. as the ID.
  305. Calls to show_boot_progress() wil also result in log entries but
  306. these will not have names.
  307. config BOOTSTAGE_REPORT
  308. bool "Display a detailed boot timing report before booting the OS"
  309. depends on BOOTSTAGE
  310. help
  311. Enable output of a boot time report just before the OS is booted.
  312. This shows how long it took U-Boot to go through each stage of the
  313. boot process. The report looks something like this:
  314. Timer summary in microseconds:
  315. Mark Elapsed Stage
  316. 0 0 reset
  317. 3,575,678 3,575,678 board_init_f start
  318. 3,575,695 17 arch_cpu_init A9
  319. 3,575,777 82 arch_cpu_init done
  320. 3,659,598 83,821 board_init_r start
  321. 3,910,375 250,777 main_loop
  322. 29,916,167 26,005,792 bootm_start
  323. 30,361,327 445,160 start_kernel
  324. config BOOTSTAGE_USER_COUNT
  325. hex "Number of boot ID numbers available for user use"
  326. default 20
  327. help
  328. This is the number of available user bootstage records.
  329. Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
  330. a new ID will be allocated from this stash. If you exceed
  331. the limit, recording will stop.
  332. config CMD_BOOTSTAGE
  333. bool "Enable the 'bootstage' command"
  334. depends on BOOTSTAGE
  335. help
  336. Add a 'bootstage' command which supports printing a report
  337. and un/stashing of bootstage data.
  338. config BOOTSTAGE_FDT
  339. bool "Store boot timing information in the OS device tree"
  340. depends on BOOTSTAGE
  341. help
  342. Stash the bootstage information in the FDT. A root 'bootstage'
  343. node is created with each bootstage id as a child. Each child
  344. has a 'name' property and either 'mark' containing the
  345. mark time in microsecond, or 'accum' containing the
  346. accumulated time for that bootstage id in microseconds.
  347. For example:
  348. bootstage {
  349. 154 {
  350. name = "board_init_f";
  351. mark = <3575678>;
  352. };
  353. 170 {
  354. name = "lcd";
  355. accum = <33482>;
  356. };
  357. };
  358. Code in the Linux kernel can find this in /proc/devicetree.
  359. config BOOTSTAGE_STASH
  360. bool "Stash the boot timing information in memory before booting OS"
  361. depends on BOOTSTAGE
  362. help
  363. Some OSes do not support device tree. Bootstage can instead write
  364. the boot timing information in a binary format at a given address.
  365. This happens through a call to bootstage_stash(), typically in
  366. the CPU's cleanup_before_linux() function. You can use the
  367. 'bootstage stash' and 'bootstage unstash' commands to do this on
  368. the command line.
  369. config BOOTSTAGE_STASH_ADDR
  370. hex "Address to stash boot timing information"
  371. default 0
  372. help
  373. Provide an address which will not be overwritten by the OS when it
  374. starts, so that it can read this information when ready.
  375. config BOOTSTAGE_STASH_SIZE
  376. hex "Size of boot timing stash region"
  377. default 4096
  378. help
  379. This should be large enough to hold the bootstage stash. A value of
  380. 4096 (4KiB) is normally plenty.
  381. endmenu
  382. menu "Power commands"
  383. config CMD_PMIC
  384. bool "Enable Driver Model PMIC command"
  385. depends on DM_PMIC
  386. help
  387. This is the pmic command, based on a driver model pmic's API.
  388. Command features are unchanged:
  389. - list - list pmic devices
  390. - pmic dev <id> - show or [set] operating pmic device (NEW)
  391. - pmic dump - dump registers
  392. - pmic read address - read byte of register at address
  393. - pmic write address - write byte to register at address
  394. The only one change for this command is 'dev' subcommand.
  395. config CMD_REGULATOR
  396. bool "Enable Driver Model REGULATOR command"
  397. depends on DM_REGULATOR
  398. help
  399. This command is based on driver model regulator's API.
  400. User interface features:
  401. - list - list regulator devices
  402. - regulator dev <id> - show or [set] operating regulator device
  403. - regulator info - print constraints info
  404. - regulator status - print operating status
  405. - regulator value <val] <-f> - print/[set] voltage value [uV]
  406. - regulator current <val> - print/[set] current value [uA]
  407. - regulator mode <id> - print/[set] operating mode id
  408. - regulator enable - enable the regulator output
  409. - regulator disable - disable the regulator output
  410. The '-f' (force) option can be used for set the value which exceeds
  411. the limits, which are found in device-tree and are kept in regulator's
  412. uclass platdata structure.
  413. endmenu
  414. endmenu