summaryrefslogtreecommitdiffstats
path: root/arch/loongarch/Kbuild
diff options
context:
space:
mode:
authorBinbin Zhou <zhoubinbin@loongson.cn>2024-01-17 12:43:00 +0800
committerHuacai Chen <chenhuacai@loongson.cn>2024-01-17 12:43:00 +0800
commit5f346a6e5970229c19c059e8fa62c3dbdde56e7b (patch)
treee313fc1e336a6a67a4d6a30dbadea746b7634fcd /arch/loongarch/Kbuild
parentdb8ce2407090f695339e3406a034377dcdc2c942 (diff)
downloadlinux-stable-5f346a6e5970229c19c059e8fa62c3dbdde56e7b.tar.gz
linux-stable-5f346a6e5970229c19c059e8fa62c3dbdde56e7b.tar.bz2
linux-stable-5f346a6e5970229c19c059e8fa62c3dbdde56e7b.zip
LoongArch: Allow device trees be built into the kernel
During the upstream progress of those DT-based drivers, DT properties are changed a lot so very different from those in existing bootloaders. It is inevitably that some existing systems do not provide a standard, canonical device tree to the kernel at boot time. So let's provide a device tree table in the kernel, keyed by the dts filename, containing the relevant DTBs. We can use the built-in dts files as references. Each SoC has only one built-in dts file which describes all possible device information of that SoC, so the dts files are good examples during development. And as a reference, our built-in dts file only enables the most basic bootable combinations (so it is generic enough), acts as an alternative in case the dts in the bootloader is unexpected. Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn> Signed-off-by: Huacai Chen <chenhuacai@loongson.cn>
Diffstat (limited to 'arch/loongarch/Kbuild')
-rw-r--r--arch/loongarch/Kbuild1
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/loongarch/Kbuild b/arch/loongarch/Kbuild
index beb8499dd8ed..bfa21465d83a 100644
--- a/arch/loongarch/Kbuild
+++ b/arch/loongarch/Kbuild
@@ -4,6 +4,7 @@ obj-y += net/
obj-y += vdso/
obj-$(CONFIG_KVM) += kvm/
+obj-$(CONFIG_BUILTIN_DTB) += boot/dts/
# for cleaning
subdir- += boot