From: Florian Fainelli <f.fainelli@gmail.com>
To: Rob Herring <robh@kernel.org>,
Detlev Casanova <detlev.casanova@collabora.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de,
bcm-kernel-feedback-list@broadcom.com,
devicetree@vger.kernel.org, f.fainelli@gmail.com,
frowand.list@gmail.com, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, masahiroy@kernel.org,
michal.lkml@markovi.net, ndesaulniers@google.com,
nsaenz@kernel.org, olof@lixom.net, rjui@broadcom.com,
sbranden@broadcom.com, soc@kernel.org, stefan.wahren@i2se.com
Subject: Re: [RFC PATCH v2 2/3] of: Add support for -@ when compiling overlays
Date: Wed, 27 Apr 2022 17:01:57 -0700 [thread overview]
Message-ID: <21986066-f72c-83ce-d1b9-ef5767fdebef@gmail.com> (raw)
In-Reply-To: <Ymm0l2/oGpt/SeDO@robh.at.kernel.org>
On 4/27/2022 2:24 PM, Rob Herring wrote:
> On Wed, Apr 27, 2022 at 02:52:42PM -0400, Detlev Casanova wrote:
>> This commit adds an option to compile all device trees with -@ to add the
>> symbol table to the Device Tree Blobs.
>
> Why would we want to tie this to the kernel config?
>
> Globally enabling it has already been discussed and rejected.
>
>> It prepares the introduction of device tree overlays that are
>> not applied on device trees at compile time (dtbo files.)
>>
>> These device tree overlays will be used by either a bootloader or a
>> linux userspace tool to extend the base device tree.
>>
>> This is used e.g. for drivers that need device tree nodes for optional
>> non plug and play devices, like an external DSI touchscreen panel that
>> embeds different i2c devices to control it.
>
> You can already set DTC_FLAGS per directory (and target?), so enable it
> for the dtbs that have overlays.
Looks like this patch series from Aurelien should take care of that:
https://lore.kernel.org/linux-arm-kernel/20220427233607.1225419-1-
aurelien@aurel32.net/
--
Florian
next prev parent reply other threads:[~2022-04-28 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 18:52 [RFC PATCH v2 0/3] ARM: dts: Support official Raspberry Pi 7inch touchscreen Detlev Casanova
2022-04-27 18:52 ` [RFC PATCH v2 1/3] ARM: dts: bcm2*: Demux i2c0 with a pinctrl Detlev Casanova
2022-04-27 18:52 ` [RFC PATCH v2 2/3] of: Add support for -@ when compiling overlays Detlev Casanova
2022-04-27 21:24 ` Rob Herring
2022-04-28 0:01 ` Florian Fainelli [this message]
2022-04-27 18:52 ` [RFC PATCH v2 3/3] ARM: dto: Add bcm2711-rpi-7-inches-ts.dts overlay Detlev Casanova
2022-04-27 21:16 ` Rob Herring
2022-04-28 6:44 ` Geert Uytterhoeven
2022-04-28 14:26 ` Rob Herring
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=21986066-f72c-83ce-d1b9-ef5767fdebef@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=nsaenz@kernel.org \
--cc=olof@lixom.net \
--cc=rjui@broadcom.com \
--cc=robh@kernel.org \
--cc=sbranden@broadcom.com \
--cc=soc@kernel.org \
--cc=stefan.wahren@i2se.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).