riscv: Fix builtin DTB handling
authorDamien Le Moal <damien.lemoal@wdc.com>
Sun, 13 Dec 2020 13:50:37 +0000 (22:50 +0900)
committerPalmer Dabbelt <palmerdabbelt@google.com>
Fri, 8 Jan 2021 03:00:50 +0000 (19:00 -0800)
commitd5805af9fe9ffe4a9d975e9bc39496f57a161076
tree129e97f2fe1ef10d94ac1981e9389ae1c1a69388
parentd573b5558abb5281306ecb35b41a2814abd8d7e4
riscv: Fix builtin DTB handling

All SiPeed K210 MAIX boards have the exact same vendor, arch and
implementation IDs, preventing differentiation to select the correct
device tree to use through the SOC_BUILTIN_DTB_DECLARE() macro. This
result in this macro to be useless and mandates changing the code of
the sysctl driver to change the builtin device tree suitable for the
target board.

Fix this problem by removing the SOC_BUILTIN_DTB_DECLARE() macro since
it is used only for the K210 support. The code searching the builtin
DTBs using the vendor, arch an implementation IDs is also removed.
Support for builtin DTB falls back to the simpler and more traditional
handling of builtin DTB using the CONFIG_BUILTIN_DTB option, similarly
to other architectures.

Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
Signed-off-by: Palmer Dabbelt <palmerdabbelt@google.com>
arch/riscv/Kconfig.socs
arch/riscv/boot/dts/Makefile
arch/riscv/boot/dts/kendryte/Makefile
arch/riscv/include/asm/soc.h
arch/riscv/kernel/soc.c
arch/riscv/mm/init.c
drivers/soc/kendryte/k210-sysctl.c