kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
2015-07-15 20:59:29 +09:00
|
|
|
config CREATE_ARCH_SYMLINK
|
|
|
|
|
bool
|
|
|
|
|
|
2016-06-28 10:48:42 +09:00
|
|
|
config HAVE_ARCH_IOREMAP
|
|
|
|
|
bool
|
|
|
|
|
|
2020-11-04 23:33:20 +09:00
|
|
|
config NEEDS_MANUAL_RELOC
|
|
|
|
|
bool
|
|
|
|
|
|
linker_lists: Fix alignment issue
The linker script uses alphabetic sorting to group the different linker
lists together. Each group has its own struct and potentially its own
alignment. But when the linker packs the structs together it cannot ensure
that a linker list starts on the expected alignment boundary.
For example, if the first list has a struct size of 8 and we place 3 of
them in the image, that means that the next struct will start at offset
0x18 from the start of the linker_list section. If the next struct has
a size of 16 then it will start at an 8-byte aligned offset, but not a
16-byte aligned offset.
With sandbox on x86_64, a reference to a linker list item using
ll_entry_get() can force alignment of that particular linker_list item,
if it is in the same file as the linker_list item is declared.
Consider this example, where struct driver is 0x80 bytes:
ll_entry_declare(struct driver, fred, driver)
...
void *p = ll_entry_get(struct driver, fred, driver)
If these two lines of code are in the same file, then the entry is forced
to be aligned at the 'struct driver' alignment, which is 16 bytes. If the
second line of code is in a different file, then no action is taken, since
the compiler cannot update the alignment of the linker_list item.
In the first case, an 8-byte 'fill' region is added:
.u_boot_list_2_driver_2_testbus_drv
0x0000000000270018 0x80 test/built-in.o
0x0000000000270018 _u_boot_list_2_driver_2_testbus_drv
.u_boot_list_2_driver_2_testfdt1_drv
0x0000000000270098 0x80 test/built-in.o
0x0000000000270098 _u_boot_list_2_driver_2_testfdt1_drv
*fill* 0x0000000000270118 0x8
.u_boot_list_2_driver_2_testfdt_drv
0x0000000000270120 0x80 test/built-in.o
0x0000000000270120 _u_boot_list_2_driver_2_testfdt_drv
.u_boot_list_2_driver_2_testprobe_drv
0x00000000002701a0 0x80 test/built-in.o
0x00000000002701a0 _u_boot_list_2_driver_2_testprobe_drv
With this, the linker_list no-longer works since items after testfdt1_drv
are not at the expected address.
Ideally we would have a way to tell gcc not to align structs in this way.
It is not clear how we could do this, and in any case it would require us
to adjust every struct used by the linker_list feature.
One possible fix is to force each separate linker_list to start on the
largest possible boundary that can be required by the compiler. However
that does not seem to work on x86_64, which uses 16-byte alignment in this
case but needs 32-byte alignment.
So add a Kconfig option to handle this. Set the default value to 4 so
as to avoid changing platforms that don't need it.
Update the ll_entry_start() accordingly.
Signed-off-by: Simon Glass <sjg@chromium.org>
2020-12-17 13:20:06 +09:00
|
|
|
config LINKER_LIST_ALIGN
|
|
|
|
|
int
|
|
|
|
|
default 32 if SANDBOX
|
|
|
|
|
default 8 if ARM64 || X86
|
|
|
|
|
default 4
|
|
|
|
|
help
|
|
|
|
|
Force the each linker list to be aligned to this boundary. This
|
|
|
|
|
is required if ll_entry_get() is used, since otherwise the linker
|
|
|
|
|
may add padding into the table, thus breaking it.
|
|
|
|
|
See linker_lists.rst for full details.
|
|
|
|
|
|
2014-07-30 14:08:15 +09:00
|
|
|
choice
|
|
|
|
|
prompt "Architecture select"
|
|
|
|
|
default SANDBOX
|
|
|
|
|
|
|
|
|
|
config ARC
|
|
|
|
|
bool "ARC architecture"
|
2018-07-23 22:55:13 +09:00
|
|
|
select ARC_TIMER
|
2017-03-21 20:49:49 +09:00
|
|
|
select CLK
|
2020-08-19 17:44:20 +09:00
|
|
|
select DM
|
2018-07-23 22:55:13 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
2017-03-21 20:49:49 +09:00
|
|
|
select TIMER
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config ARM
|
|
|
|
|
bool "ARM architecture"
|
2021-05-20 20:24:22 +09:00
|
|
|
select ARCH_SUPPORTS_LTO
|
kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
2015-07-15 20:59:29 +09:00
|
|
|
select CREATE_ARCH_SYMLINK
|
2015-07-03 16:13:09 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC if !ARM64
|
2014-09-22 19:59:05 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config M68K
|
|
|
|
|
bool "M68000 architecture"
|
2015-12-07 01:47:59 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
2020-11-04 23:33:20 +09:00
|
|
|
select NEEDS_MANUAL_RELOC
|
2018-01-23 08:17:10 +09:00
|
|
|
select SYS_BOOT_GET_CMDLINE
|
|
|
|
|
select SYS_BOOT_GET_KBD
|
2019-03-14 05:46:51 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config MICROBLAZE
|
|
|
|
|
bool "MicroBlaze architecture"
|
2020-11-04 23:33:20 +09:00
|
|
|
select NEEDS_MANUAL_RELOC
|
2014-09-22 19:59:05 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2017-05-17 18:25:39 +09:00
|
|
|
imply CMD_IRQ
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config MIPS
|
|
|
|
|
bool "MIPS architecture"
|
2016-06-28 10:48:42 +09:00
|
|
|
select HAVE_ARCH_IOREMAP
|
2014-10-24 01:30:43 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
2015-12-20 04:20:48 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config NDS32
|
|
|
|
|
bool "NDS32 architecture"
|
2017-04-17 15:41:58 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config NIOS2
|
|
|
|
|
bool "Nios II architecture"
|
2015-10-21 22:34:57 +09:00
|
|
|
select CPU
|
2018-07-23 22:55:13 +09:00
|
|
|
select DM
|
|
|
|
|
select OF_CONTROL
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
2018-07-23 22:55:14 +09:00
|
|
|
imply CMD_DM
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config PPC
|
|
|
|
|
bool "PowerPC architecture"
|
2014-10-24 01:30:43 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
2015-02-08 03:51:35 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2018-01-23 08:17:10 +09:00
|
|
|
select SYS_BOOT_GET_CMDLINE
|
|
|
|
|
select SYS_BOOT_GET_KBD
|
2014-07-30 14:08:15 +09:00
|
|
|
|
2017-12-26 14:55:58 +09:00
|
|
|
config RISCV
|
2018-09-26 22:55:06 +09:00
|
|
|
bool "RISC-V architecture"
|
2019-02-25 17:14:04 +09:00
|
|
|
select CREATE_ARCH_SYMLINK
|
2017-12-26 14:55:58 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2018-09-26 22:55:19 +09:00
|
|
|
select OF_CONTROL
|
|
|
|
|
select DM
|
2018-09-26 22:55:20 +09:00
|
|
|
imply DM_SERIAL
|
|
|
|
|
imply DM_ETH
|
|
|
|
|
imply DM_MMC
|
|
|
|
|
imply DM_SPI
|
|
|
|
|
imply DM_SPI_FLASH
|
|
|
|
|
imply BLK
|
|
|
|
|
imply CLK
|
|
|
|
|
imply MTD
|
|
|
|
|
imply TIMER
|
2018-09-26 22:55:19 +09:00
|
|
|
imply CMD_DM
|
2019-08-22 04:14:45 +09:00
|
|
|
imply SPL_DM
|
|
|
|
|
imply SPL_OF_CONTROL
|
|
|
|
|
imply SPL_LIBCOMMON_SUPPORT
|
|
|
|
|
imply SPL_LIBGENERIC_SUPPORT
|
|
|
|
|
imply SPL_SERIAL_SUPPORT
|
|
|
|
|
imply SPL_TIMER
|
2017-12-26 14:55:58 +09:00
|
|
|
|
2014-07-30 14:08:15 +09:00
|
|
|
config SANDBOX
|
|
|
|
|
bool "Sandbox"
|
2021-05-20 20:24:07 +09:00
|
|
|
select ARCH_SUPPORTS_LTO
|
2017-01-23 09:43:11 +09:00
|
|
|
select BOARD_LATE_INIT
|
2020-05-22 21:07:38 +09:00
|
|
|
select BZIP2
|
2020-10-28 04:29:22 +09:00
|
|
|
select CMD_POWEROFF
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 12:47:53 +09:00
|
|
|
select DM
|
2018-07-23 22:55:13 +09:00
|
|
|
select DM_GPIO
|
|
|
|
|
select DM_I2C
|
2016-09-08 18:47:35 +09:00
|
|
|
select DM_KEYBOARD
|
2018-07-23 22:55:13 +09:00
|
|
|
select DM_MMC
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 12:47:53 +09:00
|
|
|
select DM_SERIAL
|
|
|
|
|
select DM_SPI
|
2018-07-23 22:55:13 +09:00
|
|
|
select DM_SPI_FLASH
|
2020-05-22 21:07:38 +09:00
|
|
|
select GZIP_COMPRESSED
|
2018-02-07 03:43:56 +09:00
|
|
|
select HAVE_BLOCK_DEVICE
|
2017-07-23 07:36:16 +09:00
|
|
|
select LZO
|
2020-03-14 20:13:40 +09:00
|
|
|
select OF_BOARD_SETUP
|
2019-04-27 17:15:23 +09:00
|
|
|
select PCI_ENDPOINT
|
2018-07-23 22:55:13 +09:00
|
|
|
select SPI
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
2020-10-28 04:29:22 +09:00
|
|
|
select SYSRESET_CMD_POWEROFF
|
2021-03-09 00:48:16 +09:00
|
|
|
select IRQ
|
2021-05-05 02:31:23 +09:00
|
|
|
select SUPPORT_EXTENSION_SCAN
|
2018-08-03 15:58:03 +09:00
|
|
|
imply BITREVERSE
|
2018-11-16 10:43:53 +09:00
|
|
|
select BLOBLIST
|
2021-05-20 20:24:08 +09:00
|
|
|
imply LTO
|
2018-07-23 22:55:14 +09:00
|
|
|
imply CMD_DM
|
2020-11-12 08:29:59 +09:00
|
|
|
imply CMD_EXCEPTION
|
2017-05-17 18:25:44 +09:00
|
|
|
imply CMD_GETTIME
|
2017-05-17 18:25:25 +09:00
|
|
|
imply CMD_HASH
|
2017-05-17 18:25:34 +09:00
|
|
|
imply CMD_IO
|
2017-05-17 18:25:36 +09:00
|
|
|
imply CMD_IOTRACE
|
2017-05-17 18:25:43 +09:00
|
|
|
imply CMD_LZMADEC
|
2018-07-23 22:55:13 +09:00
|
|
|
imply CMD_SATA
|
2019-05-30 06:01:28 +09:00
|
|
|
imply CMD_SF
|
2018-07-23 22:55:13 +09:00
|
|
|
imply CMD_SF_TEST
|
2017-06-03 00:03:50 +09:00
|
|
|
imply CRC32_VERIFY
|
|
|
|
|
imply FAT_WRITE
|
2018-09-19 19:43:46 +09:00
|
|
|
imply FIRMWARE
|
2017-05-20 01:26:58 +09:00
|
|
|
imply HASH_VERIFY
|
2017-06-03 00:03:50 +09:00
|
|
|
imply LZMA
|
2017-06-15 12:28:21 +09:00
|
|
|
imply SCSI
|
2018-09-25 23:40:17 +09:00
|
|
|
imply TEE
|
2018-09-25 23:40:23 +09:00
|
|
|
imply AVB_VERIFY
|
|
|
|
|
imply LIBAVB
|
|
|
|
|
imply CMD_AVB
|
2021-02-15 00:27:27 +09:00
|
|
|
imply SCP03
|
|
|
|
|
imply CMD_SCP03
|
2018-09-25 23:40:23 +09:00
|
|
|
imply UDP_FUNCTION_FASTBOOT
|
2018-10-15 18:21:26 +09:00
|
|
|
imply VIRTIO_MMIO
|
|
|
|
|
imply VIRTIO_PCI
|
|
|
|
|
imply VIRTIO_SANDBOX
|
|
|
|
|
imply VIRTIO_BLK
|
|
|
|
|
imply VIRTIO_NET
|
2018-12-11 02:37:31 +09:00
|
|
|
imply DM_SOUND
|
2019-04-27 17:15:23 +09:00
|
|
|
imply PCI_SANDBOX_EP
|
2019-02-17 12:24:49 +09:00
|
|
|
imply PCH
|
2019-06-04 01:12:28 +09:00
|
|
|
imply PHYLIB
|
|
|
|
|
imply DM_MDIO
|
2019-07-12 16:13:53 +09:00
|
|
|
imply DM_MDIO_MUX
|
2019-12-07 13:41:54 +09:00
|
|
|
imply ACPI_PMC
|
|
|
|
|
imply ACPI_PMC_SANDBOX
|
|
|
|
|
imply CMD_PMC
|
2020-07-02 13:01:21 +09:00
|
|
|
imply CMD_CLONE
|
2020-11-06 02:33:38 +09:00
|
|
|
imply SILENT_CONSOLE
|
2020-11-06 02:33:48 +09:00
|
|
|
imply BOOTARGS_SUBST
|
sandbox: Add a DSA sandbox driver and unit test
The DSA sandbox driver is used for unit testing the DSA class code.
It implements a simple 2 port switch plus 1 CPU port, and uses a
very simple tag to identify the ports.
The DSA sandbox device is connected via CPU port to a regular Ethernet
sandbox device, called 'dsa-test-eth, managed by the existing eth
sandbox driver. The 'dsa-test-eth' is not intended for testing the
eth class code however, but it is used to emulate traffic through the
'lan0' and 'lan1' front pannel switch ports. To achieve this the dsa
sandbox driver registers a tx handler for the 'dsa-test-eth' device.
The switch ports, labeled as 'lan0' and 'lan1', are also registered
as eth devices by the dsa class code this time. So pinging through
these switch ports is as easy as:
=> setenv ethact lan0
=> ping 1.2.3.5
Unit tests for the dsa class code were also added. The 'dsa_probe'
test exercises most API functions from dsa.h. The 'dsa' unit test
simply exercises ARP/ICMP traffic through the two switch ports,
including tag injection and extraction, with the help of the dsa
sandbox driver.
I took care to minimize the impact on the existing eth unit tests,
though some adjustments needed to be made with the addition of
extra eth interfaces used by the dsa unit tests. The additional eth
interfaces also require MAC addresses, these have been added to the
sandbox default environment.
Signed-off-by: Alex Marginean <alexandru.marginean@nxp.com>
Signed-off-by: Claudiu Manoil <claudiu.manoil@nxp.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Message-Id: <20210216224804.3355044-5-olteanv@gmail.com>
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
Reviewed-by: Priyanka Jain <priyanka.jain@nxp.com>
2021-03-14 21:14:57 +09:00
|
|
|
imply PHY_FIXED
|
|
|
|
|
imply DM_DSA
|
2021-05-05 02:31:23 +09:00
|
|
|
imply CMD_EXTENSION
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config SH
|
|
|
|
|
bool "SuperH architecture"
|
2014-10-24 01:30:43 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
2019-09-01 01:27:58 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2014-07-30 14:08:15 +09:00
|
|
|
|
|
|
|
|
config X86
|
|
|
|
|
bool "x86 architecture"
|
2019-04-26 12:58:45 +09:00
|
|
|
select SUPPORT_SPL
|
|
|
|
|
select SUPPORT_TPL
|
kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
2015-07-15 20:59:29 +09:00
|
|
|
select CREATE_ARCH_SYMLINK
|
dm: select CONFIG_DM* options
As mentioned in the previous commit, adding default values in each
Kconfig causes problems because it does not co-exist with the
"depends on" syntax. (Please note this is not a bug of Kconfig.)
We should not do so unless we have a special reason. Actually,
for CONFIG_DM*, we have no good reason to do so.
Generally, CONFIG_DM is not a user-configurable option. Once we
convert a driver into Driver Model, the board only works with Driver
Model, i.e. CONFIG_DM must be always enabled for that board.
So, using "select DM" is more suitable rather than allowing users to
modify it. Another good thing is, Kconfig warns unmet dependencies
for "select" syntax, so we easily notice bugs.
Actually, CONFIG_DM and other related options have been added
without consistency: some into arch/*/Kconfig, some into
board/*/Kconfig, and some into configs/*_defconfig.
This commit prefers "select" and cleans up the following issues.
[1] Never use "CONFIG_DM=n" in defconfig files
It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
It is more common to use "# CONFIG_FOO is not set". But here, we
do not even have to do it.
Less than half of OMAP3 boards have been converted to Driver Model.
Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
weird. Instead, add "select DM" only to appropriate boards, which
eventually eliminates "CONFIG_DM=n", etc.
[2] Delete redundant CONFIGs
Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
in configs/sandbox_defconfig.
Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
defines it also in omap3_beagle_defconfig and devkit8000_defconfig.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2015-03-31 12:47:53 +09:00
|
|
|
select DM
|
2017-07-30 22:23:09 +09:00
|
|
|
select DM_PCI
|
2018-10-15 18:21:16 +09:00
|
|
|
select HAVE_ARCH_IOMAP
|
2018-07-23 22:55:13 +09:00
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select OF_CONTROL
|
2017-07-30 22:23:16 +09:00
|
|
|
select PCI
|
2018-07-23 22:55:13 +09:00
|
|
|
select SUPPORT_OF_CONTROL
|
2017-07-30 22:23:07 +09:00
|
|
|
select TIMER
|
2018-07-23 22:55:13 +09:00
|
|
|
select USE_PRIVATE_LIBGCC
|
2017-07-30 22:23:07 +09:00
|
|
|
select X86_TSC_TIMER
|
2021-03-09 00:48:15 +09:00
|
|
|
select IRQ
|
2020-07-20 04:55:52 +09:00
|
|
|
imply HAS_ROM if X86_RESET_VECTOR
|
2017-07-31 11:24:02 +09:00
|
|
|
imply BLK
|
2018-07-23 22:55:14 +09:00
|
|
|
imply CMD_DM
|
2018-07-23 22:55:13 +09:00
|
|
|
imply CMD_FPGA_LOADMK
|
|
|
|
|
imply CMD_GETTIME
|
|
|
|
|
imply CMD_IO
|
|
|
|
|
imply CMD_IRQ
|
|
|
|
|
imply CMD_PCI
|
2019-05-30 06:01:28 +09:00
|
|
|
imply CMD_SF
|
2018-07-23 22:55:13 +09:00
|
|
|
imply CMD_SF_TEST
|
|
|
|
|
imply CMD_ZBOOT
|
2017-07-30 22:23:16 +09:00
|
|
|
imply DM_ETH
|
|
|
|
|
imply DM_GPIO
|
|
|
|
|
imply DM_KEYBOARD
|
2017-07-31 11:24:01 +09:00
|
|
|
imply DM_MMC
|
2017-07-30 22:23:16 +09:00
|
|
|
imply DM_RTC
|
2017-07-31 11:24:02 +09:00
|
|
|
imply DM_SCSI
|
2018-07-23 22:55:13 +09:00
|
|
|
imply DM_SERIAL
|
2017-07-30 22:23:16 +09:00
|
|
|
imply DM_SPI
|
|
|
|
|
imply DM_SPI_FLASH
|
|
|
|
|
imply DM_USB
|
|
|
|
|
imply DM_VIDEO
|
2018-07-19 19:07:33 +09:00
|
|
|
imply SYSRESET
|
2019-04-02 21:41:25 +09:00
|
|
|
imply SPL_SYSRESET
|
2018-07-19 19:07:33 +09:00
|
|
|
imply SYSRESET_X86
|
2017-08-28 17:50:46 +09:00
|
|
|
imply USB_ETHER_ASIX
|
|
|
|
|
imply USB_ETHER_SMSC95XX
|
2018-07-23 22:55:13 +09:00
|
|
|
imply USB_HOST_ETHER
|
2019-02-17 12:24:49 +09:00
|
|
|
imply PCH
|
2019-05-03 01:52:24 +09:00
|
|
|
imply RTC_MC146818
|
2020-07-17 12:22:39 +09:00
|
|
|
imply ACPIGEN if !QEMU
|
2020-11-05 22:32:17 +09:00
|
|
|
imply SYSINFO if GENERATE_SMBIOS_TABLE
|
|
|
|
|
imply SYSINFO_SMBIOS if GENERATE_SMBIOS_TABLE
|
2014-07-30 14:08:15 +09:00
|
|
|
|
2019-04-26 12:58:45 +09:00
|
|
|
# Thing to enable for when SPL/TPL are enabled: SPL
|
|
|
|
|
imply SPL_DM
|
|
|
|
|
imply SPL_OF_LIBFDT
|
|
|
|
|
imply SPL_DRIVERS_MISC_SUPPORT
|
|
|
|
|
imply SPL_GPIO_SUPPORT
|
2019-12-07 13:42:51 +09:00
|
|
|
imply SPL_PINCTRL
|
2019-04-26 12:58:45 +09:00
|
|
|
imply SPL_LIBCOMMON_SUPPORT
|
|
|
|
|
imply SPL_LIBGENERIC_SUPPORT
|
|
|
|
|
imply SPL_SERIAL_SUPPORT
|
|
|
|
|
imply SPL_SPI_FLASH_SUPPORT
|
|
|
|
|
imply SPL_SPI_SUPPORT
|
|
|
|
|
imply SPL_OF_CONTROL
|
|
|
|
|
imply SPL_TIMER
|
|
|
|
|
imply SPL_REGMAP
|
|
|
|
|
imply SPL_SYSCON
|
|
|
|
|
# TPL
|
|
|
|
|
imply TPL_DM
|
|
|
|
|
imply TPL_DRIVERS_MISC_SUPPORT
|
|
|
|
|
imply TPL_GPIO_SUPPORT
|
2019-12-07 13:42:51 +09:00
|
|
|
imply TPL_PINCTRL
|
2019-04-26 12:58:45 +09:00
|
|
|
imply TPL_LIBCOMMON_SUPPORT
|
|
|
|
|
imply TPL_LIBGENERIC_SUPPORT
|
|
|
|
|
imply TPL_SERIAL_SUPPORT
|
|
|
|
|
imply TPL_OF_CONTROL
|
|
|
|
|
imply TPL_TIMER
|
|
|
|
|
imply TPL_REGMAP
|
|
|
|
|
imply TPL_SYSCON
|
|
|
|
|
|
2016-08-11 00:36:44 +09:00
|
|
|
config XTENSA
|
|
|
|
|
bool "Xtensa architecture"
|
|
|
|
|
select CREATE_ARCH_SYMLINK
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
|
2014-07-30 14:08:15 +09:00
|
|
|
endchoice
|
|
|
|
|
|
2014-09-14 03:01:48 +09:00
|
|
|
config SYS_ARCH
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the architecture name to build the
|
|
|
|
|
appropriate arch/<CONFIG_SYS_ARCH> directory.
|
|
|
|
|
All the architectures should specify this option correctly.
|
|
|
|
|
|
|
|
|
|
config SYS_CPU
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the CPU name to build the correct
|
|
|
|
|
arch/<CONFIG_SYS_ARCH>/cpu/<CONFIG_SYS_CPU> directory.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the CPU directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_SOC
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the SoC name to build the directory
|
|
|
|
|
arch/<CONFIG_SYS_ARCH>/cpu/<CONFIG_SYS_CPU>/<CONFIG_SYS_SOC>.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the SoC directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_VENDOR
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the vendor name of the target board.
|
|
|
|
|
If it is set and
|
|
|
|
|
board/<CONFIG_SYS_VENDOR>/common/Makefile exists, the vendor common
|
|
|
|
|
directory is compiled.
|
|
|
|
|
If CONFIG_SYS_BOARD is also set, the sources under
|
|
|
|
|
board/<CONFIG_SYS_VENDOR>/<CONFIG_SYS_BOARD> directory are compiled.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the vendor directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_BOARD
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the name of the target board.
|
|
|
|
|
If it is set, either board/<CONFIG_SYS_VENDOR>/<CONFIG_SYS_BOARD>
|
|
|
|
|
or board/<CONFIG_SYS_BOARD> directory is compiled depending on
|
|
|
|
|
whether CONFIG_SYS_VENDOR is set or not.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the board directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_CONFIG_NAME
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the base name of board header file.
|
|
|
|
|
The header file include/configs/<CONFIG_SYS_CONFIG_NAME>.h
|
|
|
|
|
should be included from include/config.h.
|
|
|
|
|
|
2019-04-23 01:13:32 +09:00
|
|
|
config SYS_DISABLE_DCACHE_OPS
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This option disables dcache flush and dcache invalidation
|
|
|
|
|
operations. For example, on coherent systems where cache
|
|
|
|
|
operatios are not required, enable this option to avoid them.
|
|
|
|
|
Note that, its up to the individual architectures to implement
|
|
|
|
|
this functionality.
|
|
|
|
|
|
2014-07-30 14:08:15 +09:00
|
|
|
source "arch/arc/Kconfig"
|
|
|
|
|
source "arch/arm/Kconfig"
|
|
|
|
|
source "arch/m68k/Kconfig"
|
|
|
|
|
source "arch/microblaze/Kconfig"
|
|
|
|
|
source "arch/mips/Kconfig"
|
|
|
|
|
source "arch/nds32/Kconfig"
|
|
|
|
|
source "arch/nios2/Kconfig"
|
|
|
|
|
source "arch/powerpc/Kconfig"
|
|
|
|
|
source "arch/sandbox/Kconfig"
|
|
|
|
|
source "arch/sh/Kconfig"
|
|
|
|
|
source "arch/x86/Kconfig"
|
2016-08-11 00:36:44 +09:00
|
|
|
source "arch/xtensa/Kconfig"
|
2017-12-26 14:55:58 +09:00
|
|
|
source "arch/riscv/Kconfig"
|