X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=common%2FKconfig;h=c69c1418c92ad1794b42426b4b056eaabaa49033;hb=0a0e53cb2ee625f603b7e2bb0caba23946f5fe40;hp=fd84fa08bd3efc2569ac4200684f26abca5ac205;hpb=dee332ffb735f65ab922118791a583c17bb0b795;p=karo-tx-uboot.git diff --git a/common/Kconfig b/common/Kconfig index fd84fa08bd..c69c1418c9 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -1,316 +1,222 @@ -menu "Command line interface" - depends on !SPL_BUILD - -config HUSH_PARSER - bool "Use hush shell" - select SYS_HUSH_PARSER - help - This option enables the "hush" shell (from Busybox) as command line - interpreter, thus enabling powerful command line syntax like - if...then...else...fi conditionals or `&&' and '||' - constructs ("shell scripts"). - - If disabled, you get the old, much simpler behaviour with a somewhat - smaller memory footprint. - -config SYS_HUSH_PARSER - bool - help - Backward compatibility. - -comment "Commands" - -menu "Info commands" - -config CMD_BDI - bool "bdinfo" - help - Print board info - -config CMD_CONSOLE - bool "coninfo" - help - Print console devices and information. - -config CMD_LICENSE - bool "license" - help - Print GPL license text - -endmenu - -menu "Boot commands" - -config CMD_BOOTD - bool "bootd" - help - Run the command stored in the environment "bootcmd", i.e. - "bootd" does the same thing as "run bootcmd". - -config CMD_BOOTM - bool "bootm" - default y - help - Boot an application image from the memory. - -config CMD_GO - bool "go" - default y - help - Start an application at a given address. - -config CMD_RUN - bool "run" - help - Run the command in the given environment variable. - -config CMD_IMI - bool "iminfo" - help - Print header information for application image. - -config CMD_IMLS - bool "imls" - help - List all images found in flash - -config CMD_XIMG - bool "imxtract" - help - Extract a part of a multi-image. - -endmenu - -menu "Environment commands" - -config CMD_EXPORTENV - bool "env export" - default y - help - Export environments. - -config CMD_IMPORTENV - bool "env import" - default y - help - Import environments. - -config CMD_EDITENV - bool "editenv" - help - Edit environment variable. - -config CMD_SAVEENV - bool "saveenv" - help - Run the command in the given environment variable. - -endmenu - -menu "Memory commands" - -config CMD_MEMORY - bool "md, mm, nm, mw, cp, cmp, base, loop" - help - Memeory commands. - md - memory display - mm - memory modify (auto-incrementing address) - nm - memory modify (constant address) - mw - memory write (fill) - cp - memory copy - cmp - memory compare - base - print or set address offset - loop - initinite loop on address range - -config CMD_CRC32 - bool "crc32" - default y - help - Compute CRC32. - -config LOOPW - bool "loopw" - help - Infinite write loop on address range - -config CMD_MEMTEST - bool "crc32" - help - Simple RAM read/write test. - -config CMD_MX_CYCLIC - bool "mdc, mwc" - help - mdc - memory display cyclic - mwc - memory write cyclic - -config CMD_MEMINFO - bool "meminfo" - help - Display memory information. +menu "Boot timing" + +config BOOTSTAGE + bool "Boot timing and reporting" + help + Enable recording of boot time while booting. To use it, insert + calls to bootstage_mark() with a suitable BOOTSTAGE_ID from + bootstage.h. Only a single entry is recorded for each ID. You can + give the entry a name with bootstage_mark_name(). You can also + record elapsed time in a particular stage using bootstage_start() + before starting and bootstage_accum() when finished. Bootstage will + add up all the accumulated time and report it. + + Normally, IDs are defined in bootstage.h but a small number of + additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC + as the ID. + + Calls to show_boot_progress() will also result in log entries but + these will not have names. + +config BOOTSTAGE_REPORT + bool "Display a detailed boot timing report before booting the OS" + depends on BOOTSTAGE + help + Enable output of a boot time report just before the OS is booted. + This shows how long it took U-Boot to go through each stage of the + boot process. The report looks something like this: + + Timer summary in microseconds: + Mark Elapsed Stage + 0 0 reset + 3,575,678 3,575,678 board_init_f start + 3,575,695 17 arch_cpu_init A9 + 3,575,777 82 arch_cpu_init done + 3,659,598 83,821 board_init_r start + 3,910,375 250,777 main_loop + 29,916,167 26,005,792 bootm_start + 30,361,327 445,160 start_kernel + +config BOOTSTAGE_USER_COUNT + hex "Number of boot ID numbers available for user use" + default 20 + help + This is the number of available user bootstage records. + Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...) + a new ID will be allocated from this stash. If you exceed + the limit, recording will stop. + +config BOOTSTAGE_FDT + bool "Store boot timing information in the OS device tree" + depends on BOOTSTAGE + help + Stash the bootstage information in the FDT. A root 'bootstage' + node is created with each bootstage id as a child. Each child + has a 'name' property and either 'mark' containing the + mark time in microseconds, or 'accum' containing the + accumulated time for that bootstage id in microseconds. + For example: + + bootstage { + 154 { + name = "board_init_f"; + mark = <3575678>; + }; + 170 { + name = "lcd"; + accum = <33482>; + }; + }; + + Code in the Linux kernel can find this in /proc/devicetree. + +config BOOTSTAGE_STASH + bool "Stash the boot timing information in memory before booting OS" + depends on BOOTSTAGE + help + Some OSes do not support device tree. Bootstage can instead write + the boot timing information in a binary format at a given address. + This happens through a call to bootstage_stash(), typically in + the CPU's cleanup_before_linux() function. You can use the + 'bootstage stash' and 'bootstage unstash' commands to do this on + the command line. + +config BOOTSTAGE_STASH_ADDR + hex "Address to stash boot timing information" + default 0 + help + Provide an address which will not be overwritten by the OS when it + starts, so that it can read this information when ready. + +config BOOTSTAGE_STASH_SIZE + hex "Size of boot timing stash region" + default 4096 + help + This should be large enough to hold the bootstage stash. A value of + 4096 (4KiB) is normally plenty. endmenu -menu "Device access commands" - -config CMD_LOADB - bool "loadb" - help - Load a binary file over serial line. +menu "Boot media" -config CMD_LOADS - bool "loads" +config NOR_BOOT + bool "Support for booting from NOR flash" + depends on NOR help - Load an S-Record file over serial line + Enabling this will make a U-Boot binary that is capable of being + booted via NOR. In this case we will enable certain pinmux early + as the ROM only partially sets up pinmux. We also default to using + NOR for environment. -config CMD_FLASH - bool "flinfo, erase, protect" +config NAND_BOOT + bool "Support for booting from NAND flash" + default n help - NOR flash support. - flinfo - print FLASH memory information - erase - FLASH memory - protect - enable or disable FLASH write protection + Enabling this will make a U-Boot binary that is capable of being + booted via NAND flash. This is not a must, some SoCs need this, + some not. -config CMD_NAND - bool "nand" +config ONENAND_BOOT + bool "Support for booting from ONENAND" + default n help - NAND support. + Enabling this will make a U-Boot binary that is capable of being + booted via ONENAND. This is not a must, some SoCs need this, + some not. -config CMD_SPI - bool "sspi" +config QSPI_BOOT + bool "Support for booting from QSPI flash" + default n help - SPI utility command. + Enabling this will make a U-Boot binary that is capable of being + booted via QSPI flash. This is not a must, some SoCs need this, + some not. -config CMD_I2C - bool "i2c" +config SATA_BOOT + bool "Support for booting from SATA" + default n help - I2C support. + Enabling this will make a U-Boot binary that is capable of being + booted via SATA. This is not a must, some SoCs need this, + some not. -config CMD_USB - bool "usb" +config SD_BOOT + bool "Support for booting from SD/EMMC" + default n help - USB support. + Enabling this will make a U-Boot binary that is capable of being + booted via SD/EMMC. This is not a must, some SoCs need this, + some not. -config CMD_FPGA - bool "fpga" +config SPI_BOOT + bool "Support for booting from SPI flash" + default n help - FPGA support. + Enabling this will make a U-Boot binary that is capable of being + booted via SPI flash. This is not a must, some SoCs need this, + some not. endmenu - -menu "Shell scripting commands" - -config CMD_ECHO - bool "echo" - help - Echo args to console - -config CMD_ITEST - bool "itest" - help - Return true/false on integer compare. - -config CMD_SOURCE - bool "source" - help - Run script from memory - -endmenu - -menu "Network commands" - -config CMD_NET - bool "bootp, tftpboot" +config BOOTDELAY + int "delay in seconds before automatically booting" + default 2 + depends on AUTOBOOT help - Network commands. - bootp - boot image via network using BOOTP/TFTP protocol - tftpboot - boot image via network using TFTP protocol + Delay before automatically running bootcmd; + set to 0 to autoboot with no delay, but you can stop it by key input. + set to -1 to disable autoboot. + set to -2 to autoboot with no delay and not check for abort -config CMD_TFTPPUT - bool "tftp put" - help - TFTP put command, for uploading files to a server - -config CMD_TFTPSRV - bool "tftpsrv" - help - Act as a TFTP server and boot the first received file - -config CMD_RARP - bool "rarpboot" - help - Boot image via network using RARP/TFTP protocol - -config CMD_DHCP - bool "dhcp" - help - Boot image via network using DHCP/TFTP protocol - -config CMD_NFS - bool "nfs" - help - Boot image via network using NFS protocol. + See doc/README.autoboot for details. -config CMD_PING - bool "ping" +config CONSOLE_RECORD + bool "Console recording" help - Send ICMP ECHO_REQUEST to network host + This provides a way to record console output (and provide console + input) through circular buffers. This is mostly useful for testing. + Console output is recorded even when the console is silent. + To enable console recording, call console_record_reset_enable() + from your code. -config CMD_CDP - bool "cdp" +config CONSOLE_RECORD_OUT_SIZE + hex "Output buffer size" + depends on CONSOLE_RECORD + default 0x400 if CONSOLE_RECORD help - Perform CDP network configuration + Set the size of the console output buffer. When this fills up, no + more data will be recorded until some is removed. The buffer is + allocated immediately after the malloc() region is ready. -config CMD_SNTP - bool "sntp" +config CONSOLE_RECORD_IN_SIZE + hex "Input buffer size" + depends on CONSOLE_RECORD + default 0x100 if CONSOLE_RECORD help - Synchronize RTC via network + Set the size of the console input buffer. When this contains data, + tstc() and getc() will use this in preference to real device input. + The buffer is allocated immediately after the malloc() region is + ready. -config CMD_DNS - bool "dns" +config IDENT_STRING + string "Board specific string to be added to uboot version string" help - Lookup the IP of a hostname + This options adds the board specific name to u-boot version. -config CMD_DNS - bool "dns" +config SYS_NO_FLASH + bool "Disable support for parallel NOR flash" + default n help - Lookup the IP of a hostname + This option is used to disable support for parallel NOR flash. -config CMD_LINK_LOCAL - bool "linklocal" +config VERSION_VARIABLE + bool "add U-Boot environment variable vers" + default n help - Acquire a network IP address using the link-local protocol - -endmenu - -menu "Misc commands" + If this variable is defined, an environment variable + named "ver" is created by U-Boot showing the U-Boot + version as printed by the "version" command. + Any change to this variable will be reverted at the + next reset. -config CMD_TIME - bool "time" - help - Run commands and summarize execution time. - -# TODO: rename to CMD_SLEEP -config CMD_MISC - bool "sleep" - help - Delay execution for some time - -config CMD_TIMER - bool "timer" - help - Access the system timer. - -config CMD_SETGETDCR - bool "getdcr, setdcr, getidcr, setidcr" - depends on 4xx - help - getdcr - Get an AMCC PPC 4xx DCR's value - setdcr - Set an AMCC PPC 4xx DCR's value - getidcr - Get a register value via indirect DCR addressing - setidcr - Set a register value via indirect DCR addressing - -endmenu - -endmenu +source "common/spl/Kconfig"