Tom Rini 3dd1486800 Kconfig: Centralize prompting for SYS_CONFIG_NAME ... Generally speaking, we do not prompt for this value and define it in the board specific Kconfig file. There are some valid use cases however today where we do prompt for this value, so instead of having this be done in a number of locations, do this at the top-level location only. This removes the question from a number of other locations and makes it consistent that when we do set the value directly, we always do it the same way. We don't need to specify the type, it's always string. Signed-off-by: Tom Rini <trini@konsulko.com>		2024-02-27 14:18:54 -05:00
..
bootscripts	xilinx: Add sd boot command script for reference	2019-10-08 09:11:13 +02:00
common	xilinx: board: Update the kaslr-seed property	2024-01-17 08:12:20 +01:00
mbv	xilinx_mbv: Remove empty config header	2024-02-27 14:18:30 -05:00
microblaze-generic	Kconfig: Centralize prompting for SYS_CONFIG_NAME	2024-02-27 14:18:54 -05:00
versal	treewide: Tidy up semicolon after command macros	2023-12-13 11:51:24 -05:00
versal-net	arm64: versal: Add SelectMAP boot mode identification	2023-10-09 13:03:23 +02:00
zynq	xilinx: zynq: Generate dfu for SPI only when enabled	2023-12-13 08:58:06 +01:00
zynqmp	xilinx: zynqmp: Add the missing function prototype	2024-02-12 09:28:32 +01:00
zynqmp_r5	.mailmap: Start to use new amd.com email address	2022-04-19 14:51:11 -04:00
Kconfig	riscv: Add support for AMD/Xilinx MicroBlaze V	2023-12-18 11:08:49 +08:00