All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: linux-kbuild@vger.kernel.org
Cc: Marek Vasut <marex@denx.de>, Masahiro Yamada <masahiroy@kernel.org>
Subject: [RFC][PATCH] kbuild: Generate symbols for DTO application in DTBs
Date: Thu,  7 Apr 2022 13:05:22 +0200	[thread overview]
Message-ID: <20220407110522.122393-1-marex@denx.de> (raw)

Emit symbols section in DTBs to permit symbol resolution when applying DTOs.

Signed-off-by: Marek Vasut <marex@denx.de>
Cc: Masahiro Yamada <masahiroy@kernel.org>
---
NOTE: I am sending this as RFC, because I suspect there is a better way how
      to pass extra flags to DTC during kernel build ?
      Maybe from shell environment somehow ?
      Or maybe b7e70391a5451 ("arm64: tegra: Enable device-tree overlay support")
      is the way to go about this ?
---
 arch/arm/boot/dts/Makefile   | 3 +++
 arch/arm64/boot/dts/Makefile | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
index 252353fb4e3b3..2d50302d077dd 100644
--- a/arch/arm/boot/dts/Makefile
+++ b/arch/arm/boot/dts/Makefile
@@ -1,4 +1,7 @@
 # SPDX-License-Identifier: GPL-2.0
+
+DTC_FLAGS += -@
+
 dtb-$(CONFIG_ARCH_ALPINE) += \
 	alpine-db.dtb
 dtb-$(CONFIG_MACH_ARTPEC6) += \
diff --git a/arch/arm64/boot/dts/Makefile b/arch/arm64/boot/dts/Makefile
index 1ba04e31a4387..f7b3c86517a0e 100644
--- a/arch/arm64/boot/dts/Makefile
+++ b/arch/arm64/boot/dts/Makefile
@@ -1,4 +1,7 @@
 # SPDX-License-Identifier: GPL-2.0
+
+DTC_FLAGS += -@
+
 subdir-y += actions
 subdir-y += allwinner
 subdir-y += altera
-- 
2.35.1


             reply	other threads:[~2022-04-07 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07 11:05 Marek Vasut [this message]
2022-04-07 12:30 ` [RFC][PATCH] kbuild: Generate symbols for DTO application in DTBs Masahiro Yamada
2022-04-10  0:07   ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220407110522.122393-1-marex@denx.de \
    --to=marex@denx.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.