1config HAS_CAAM
2	bool
3
4config IMX_CONFIG
5	string
6
7config ROM_UNIFIED_SECTIONS
8	bool
9
10config SYSCOUNTER_TIMER
11	bool
12
13config GPT_TIMER
14	bool
15
16config IMX_RDC
17	bool "i.MX Resource domain controller driver"
18	depends on ARCH_MX6 || ARCH_MX7
19	help
20	  i.MX Resource domain controller is used to assign masters
21	  and peripherals to differet domains. This can be used to
22	  isolate resources.
23
24config IMX_BOOTAUX
25	bool "Support boot auxiliary core"
26	depends on ARCH_MX7 || ARCH_MX6 || ARCH_VF610 || ARCH_IMX8M
27	help
28	  bootaux [addr] to boot auxiliary core.
29
30config IMX_MODULE_FUSE
31	bool "i.MX Module Fuse"
32	depends on ARCH_MX6
33	help
34	  i.MX module fuse to runtime disable some driver, including
35	  Linux OS device node.
36
37config USE_IMXIMG_PLUGIN
38	bool "Use imximage plugin code"
39	depends on ARCH_MX7 || ARCH_MX6 || ARCH_MX7ULP
40	help
41	  i.MX6/7 supports DCD and Plugin. Enable this configuration
42	  to use Plugin, otherwise DCD will be used.
43
44config IMX_HAB
45	bool "Support i.MX HAB features"
46	depends on ARCH_MX7 || ARCH_MX6 || ARCH_MX5
47	select FSL_CAAM if HAS_CAAM
48	imply CMD_DEKBLOB
49	help
50	  This option enables the support for secure boot (HAB).
51	  See doc/imx/habv4/* for more details.
52
53config CSF_SIZE
54	hex "Maximum size for Command Sequence File (CSF) binary"
55	depends on IMX_HAB
56	default 0x2000 if ARCH_IMX8M
57	default 0x2060
58	help
59	  Define the maximum size for Command Sequence File (CSF) binary
60	  this information is used to define the image boot data.
61
62config CMD_BMODE
63	bool "Support the 'bmode' command"
64	default y
65	depends on ARCH_MX7 || ARCH_MX6 || ARCH_MX5
66	help
67	  This enables the 'bmode' (bootmode) command for forcing
68	  a boot from specific media.
69
70	  This is useful for forcing the ROM's usb downloader to
71	  activate upon a watchdog reset which is nice when iterating
72	  on U-Boot.  Using the reset button or running bmode normal
73	  will set it back to normal.  This command currently
74	  supports i.MX53 and i.MX6.
75
76config CMD_DEKBLOB
77	bool "Support the 'dek_blob' command"
78	help
79	  This enables the 'dek_blob' command which is used with the
80	  Freescale secure boot mechanism. This command encapsulates and
81	  creates a blob of data. See also CMD_BLOB and doc/imx/habv4/* for
82	  more information.
83
84config CMD_HDMIDETECT
85	bool "Support the 'hdmidet' command"
86	help
87	  This enables the 'hdmidet' command which detects if an HDMI monitor
88	  is connected.
89
90config CMD_NANDBCB
91	bool "i.MX6 NAND Boot Control Block(BCB) command"
92	depends on MTD_RAW_NAND && CMD_MTDPARTS
93	select BCH if MX6UL || MX6ULL
94	default y if ((ARCH_MX6 || ARCH_MX7 || ARCH_IMX8M) && NAND_MXS)
95	help
96	  Unlike normal 'nand write/erase' commands, this command update
97	  Boot Control Block(BCB) for i.MX6 platform NAND IP's.
98
99	  This is similar to kobs-ng, which is used in Linux as separate
100	  rootfs package.
101
102config NXP_BOARD_REVISION
103	bool "Read NXP board revision from fuses"
104	depends on ARCH_MX6 || ARCH_MX7
105	help
106	  NXP boards based on i.MX6/7 contain the board revision information
107	  stored in the fuses. Select this option if you want to be able to
108	  retrieve the board revision information.
109
110config DDRMC_VF610_CALIBRATION
111	bool "Enable DDRMC (DDR3) on-chip calibration"
112	depends on ARCH_VF610
113	help
114	  Vybrid (vf610) SoC provides some on-chip facility to tune the DDR3
115	  memory parameters. Select this option if you want to calculate them
116	  at boot time.
117	  NOTE:
118	  NXP does NOT recommend to perform this calibration at each boot. One
119	  shall perform it on a new PCB and then use those values to program
120	  the ddrmc_cr_setting on relevant board file.
121
122config SPL_IMX_ROMAPI_LOADADDR
123	hex "Default load address to load image through ROM API"
124	depends on IMX8MN || IMX8MP
125
126config IMX_DCD_ADDR
127	hex "DCD Blocks location on the image"
128	default 0x00910000 if !ARCH_MX7ULP
129	default 0x2f010000 if ARCH_MX7ULP
130	help
131	  Indicates where the Device Configuration Data, a binary table used by
132	  the ROM code to configure the device at early boot stage, is located.
133	  This information is shared with the user via mkimage -l just so the
134	  image can be signed.
135