[people/ms/u-boot.git] / common / Kconfig

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 accumated time and report it.

	  Normally, IDs are defined in bootstage.h but a small number of
	  additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
	  as the ID.

	  Calls to show_boot_progress() wil 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 microsecond, 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 "Boot media"

config NOR_BOOT
	bool "Support for booting from NOR flash"
	depends on NOR
	help
	  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 NAND_BOOT
	bool "Support for booting from NAND flash"
	default n
	help
	  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,
	  somes not.

config ONENAND_BOOT
	bool "Support for booting from ONENAND"
	default n
	help
	  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,
	  somes not.

config QSPI_BOOT
	bool "Support for booting from QSPI flash"
	default n
	help
	  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,
	  somes not.

config SATA_BOOT
	bool "Support for booting from SATA"
	default n
	help
	  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,
	  somes not.

config SD_BOOT
	bool "Support for booting from SD/EMMC"
	default n
	help
	  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,
	  somes not.

config SPI_BOOT
	bool "Support for booting from SPI flash"
	default n
	help
	  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,
	  somes not.

endmenu

config BOOTDELAY
	int "delay in seconds before automatically booting"
	default 2
	depends on AUTOBOOT
	help
	  Delay before automatically running bootcmd;
	  set to -1 to disable autoboot.
	  set to -2 to autoboot with no delay and not check for abort
	  (even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).

	  See doc/README.autoboot for details.

config CONSOLE_RECORD
	bool "Console recording"
	help
	  This provides a way to record console output (and provide console
	  input) through cirular 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 CONSOLE_RECORD_OUT_SIZE
	hex "Output buffer size"
	depends on CONSOLE_RECORD
	default 0x400 if CONSOLE_RECORD
	help
	  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 CONSOLE_RECORD_IN_SIZE
	hex "Input buffer size"
	depends on CONSOLE_RECORD
	default 0x100 if CONSOLE_RECORD
	help
	  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.
Commit	Line	Data
ee2b2434 SG	1	menu "Boot timing"
	2
	3	config BOOTSTAGE
	4	bool "Boot timing and reporting"
	5	help
	6	Enable recording of boot time while booting. To use it, insert
	7	calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
	8	bootstage.h. Only a single entry is recorded for each ID. You can
	9	give the entry a name with bootstage_mark_name(). You can also
	10	record elapsed time in a particular stage using bootstage_start()
	11	before starting and bootstage_accum() when finished. Bootstage will
	12	add up all the accumated time and report it.
	13
	14	Normally, IDs are defined in bootstage.h but a small number of
	15	additional 'user' IDs can be used but passing BOOTSTAGE_ID_ALLOC
	16	as the ID.
	17
	18	Calls to show_boot_progress() wil also result in log entries but
	19	these will not have names.
	20
	21	config BOOTSTAGE_REPORT
	22	bool "Display a detailed boot timing report before booting the OS"
	23	depends on BOOTSTAGE
	24	help
	25	Enable output of a boot time report just before the OS is booted.
	26	This shows how long it took U-Boot to go through each stage of the
	27	boot process. The report looks something like this:
	28
	29	Timer summary in microseconds:
	30	Mark Elapsed Stage
	31	0 0 reset
	32	3,575,678 3,575,678 board_init_f start
	33	3,575,695 17 arch_cpu_init A9
	34	3,575,777 82 arch_cpu_init done
	35	3,659,598 83,821 board_init_r start
	36	3,910,375 250,777 main_loop
	37	29,916,167 26,005,792 bootm_start
	38	30,361,327 445,160 start_kernel
	39
	40	config BOOTSTAGE_USER_COUNT
	41	hex "Number of boot ID numbers available for user use"
	42	default 20
	43	help
	44	This is the number of available user bootstage records.
	45	Each time you call bootstage_mark(BOOTSTAGE_ID_ALLOC, ...)
	46	a new ID will be allocated from this stash. If you exceed
	47	the limit, recording will stop.
	48
ee2b2434 SG	49	config BOOTSTAGE_FDT
	50	bool "Store boot timing information in the OS device tree"
	51	depends on BOOTSTAGE
	52	help
	53	Stash the bootstage information in the FDT. A root 'bootstage'
	54	node is created with each bootstage id as a child. Each child
	55	has a 'name' property and either 'mark' containing the
	56	mark time in microsecond, or 'accum' containing the
	57	accumulated time for that bootstage id in microseconds.
	58	For example:
	59
	60	bootstage {
	61	154 {
	62	name = "board_init_f";
	63	mark = <3575678>;
	64	};
	65	170 {
	66	name = "lcd";
	67	accum = <33482>;
	68	};
	69	};
	70
	71	Code in the Linux kernel can find this in /proc/devicetree.
	72
	73	config BOOTSTAGE_STASH
	74	bool "Stash the boot timing information in memory before booting OS"
	75	depends on BOOTSTAGE
	76	help
	77	Some OSes do not support device tree. Bootstage can instead write
	78	the boot timing information in a binary format at a given address.
	79	This happens through a call to bootstage_stash(), typically in
	80	the CPU's cleanup_before_linux() function. You can use the
	81	'bootstage stash' and 'bootstage unstash' commands to do this on
	82	the command line.
	83
	84	config BOOTSTAGE_STASH_ADDR
	85	hex "Address to stash boot timing information"
	86	default 0
	87	help
	88	Provide an address which will not be overwritten by the OS when it
	89	starts, so that it can read this information when ready.
	90
	91	config BOOTSTAGE_STASH_SIZE
	92	hex "Size of boot timing stash region"
	93	default 4096
	94	help
	95	This should be large enough to hold the bootstage stash. A value of
	96	4096 (4KiB) is normally plenty.
	97
	98	endmenu
	99
d14739ff PF	100	menu "Boot media"
	101
	102	config NOR_BOOT
	103	bool "Support for booting from NOR flash"
	104	depends on NOR
	105	help
	106	Enabling this will make a U-Boot binary that is capable of being
	107	booted via NOR. In this case we will enable certain pinmux early
	108	as the ROM only partially sets up pinmux. We also default to using
	109	NOR for environment.
	110
faaef73f PF	111	config NAND_BOOT
	112	bool "Support for booting from NAND flash"
	113	default n
	114	help
	115	Enabling this will make a U-Boot binary that is capable of being
	116	booted via NAND flash. This is not a must, some SoCs need this,
	117	somes not.
	118
	119	config ONENAND_BOOT
	120	bool "Support for booting from ONENAND"
	121	default n
	122	help
	123	Enabling this will make a U-Boot binary that is capable of being
	124	booted via ONENAND. This is not a must, some SoCs need this,
	125	somes not.
	126
	127	config QSPI_BOOT
	128	bool "Support for booting from QSPI flash"
	129	default n
	130	help
	131	Enabling this will make a U-Boot binary that is capable of being
	132	booted via QSPI flash. This is not a must, some SoCs need this,
	133	somes not.
	134
	135	config SATA_BOOT
	136	bool "Support for booting from SATA"
	137	default n
	138	help
	139	Enabling this will make a U-Boot binary that is capable of being
	140	booted via SATA. This is not a must, some SoCs need this,
	141	somes not.
	142
	143	config SD_BOOT
	144	bool "Support for booting from SD/EMMC"
	145	default n
	146	help
	147	Enabling this will make a U-Boot binary that is capable of being
	148	booted via SD/EMMC. This is not a must, some SoCs need this,
	149	somes not.
	150
	151	config SPI_BOOT
	152	bool "Support for booting from SPI flash"
	153	default n
	154	help
	155	Enabling this will make a U-Boot binary that is capable of being
	156	booted via SPI flash. This is not a must, some SoCs need this,
	157	somes not.
	158
d14739ff PF	159	endmenu
d14739ff PF	160
bb597c0e HS	161	config BOOTDELAY
bb597c0e HS	162	int "delay in seconds before automatically booting"
5e4e8741	163	default 2
41598c82	164	depends on AUTOBOOT
bb597c0e HS	165	help
	166	Delay before automatically running bootcmd;
	167	set to -1 to disable autoboot.
	168	set to -2 to autoboot with no delay and not check for abort
	169	(even when CONFIG_ZERO_BOOTDELAY_CHECK is defined).
	170
9060970f MY	171	See doc/README.autoboot for details.
9060970f MY	172
9854a874 SG	173	config CONSOLE_RECORD
	174	bool "Console recording"
	175	help
	176	This provides a way to record console output (and provide console
	177	input) through cirular buffers. This is mostly useful for testing.
	178	Console output is recorded even when the console is silent.
	179	To enable console recording, call console_record_reset_enable()
	180	from your code.
	181
	182	config CONSOLE_RECORD_OUT_SIZE
	183	hex "Output buffer size"
	184	depends on CONSOLE_RECORD
	185	default 0x400 if CONSOLE_RECORD
	186	help
	187	Set the size of the console output buffer. When this fills up, no
	188	more data will be recorded until some is removed. The buffer is
	189	allocated immediately after the malloc() region is ready.
	190
	191	config CONSOLE_RECORD_IN_SIZE
	192	hex "Input buffer size"
	193	depends on CONSOLE_RECORD
	194	default 0x100 if CONSOLE_RECORD
	195	help
	196	Set the size of the console input buffer. When this contains data,
	197	tstc() and getc() will use this in preference to real device input.
	198	The buffer is allocated immediately after the malloc() region is
	199	ready.