From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Nikita Travkin <nikita@trvn.ru>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] {vision/navigation}-mezzanine: Fix overlay root node
Date: Thu, 27 Feb 2025 11:12:33 +0000 [thread overview]
Message-ID: <d12ba10b-6eb3-4344-af50-dba80c79791e@linaro.org> (raw)
In-Reply-To: <20250226-qcom-nonroot-overlays-v1-0-26c6e7605833@trvn.ru>
On 26/02/2025 14:29, Nikita Travkin wrote:
> While considering to propose WoA EL2 dt overlays upstream I was looking
> at existing overlays and noticed that some of them are broken: they put
> seemingly meaningful fixups into the overlay's "/" node, which places
> them into the overlay "metadata" itself, not into a fixup fragment to be
> applied to the actual dtb. This series fixes those two by changing to
> full path "&{/}" which should work as it was initially intended.
>
> See demonstration of the problem below:
>
> $ cat base.dts
> /dts-v1/;
> / {
> compatible = "fake,board";
> fake,value = <42>;
> };
>
> $ cat extra.dtso
> /dts-v1/;
> /plugin/;
>
> / {
> foo;
> bar { baz; };
> };
> &{/} { whatever-comes-next-after-baz; };
>
> $ dtc base.dts -o base.dtb
> $ dtc extra.dtso -o extra.dtbo
> $ fdtoverlay -i base.dtb -o combine.dtb extra.dtbo
> $ dtc base.dtb
> /dts-v1/;
>
> / {
> compatible = "fake,board";
> fake,value = <0x2a>;
> };
>
> $ dtc extra.dtbo
> /dts-v1/;
>
> / {
> foo;
>
> bar {
> baz;
> };
>
> fragment@0 {
> target-path = "/";
>
> __overlay__ {
> whatever-comes-next-after-baz;
> };
> };
> };
>
> $ dtc combine.dtb
> /dts-v1/;
>
> / {
> whatever-comes-next-after-baz;
> compatible = "fake,board";
> fake,value = <0x2a>;
> };
>
> In the resulting dtb foo bar and baz are missing.
>
> Signed-off-by: Nikita Travkin <nikita@trvn.ru>
> ---
> Nikita Travkin (2):
> arm64: dts: qcom: qrb5165-rb5-vision-mezzanine: Fix broken overlay root
> arm64: dts: qcom: sdm845-db845c-navigation-mezzanine: Fix the overlay root
>
> arch/arm64/boot/dts/qcom/qrb5165-rb5-vision-mezzanine.dtso | 2 +-
> arch/arm64/boot/dts/qcom/sdm845-db845c-navigation-mezzanine.dtso | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> ---
> base-commit: 8433c776e1eb1371f5cd40b5fd3a61f9c7b7f3ad
> change-id: 20250226-qcom-nonroot-overlays-bfe21d33be8c
>
> Best regards,
This is a good find however, we should just drop these additional CMA
heap nodes as the reason for their original addition has been superseded.
libcamera can now use UDMA buf for the same purpose as the CMA heap,
without the security concerns of CMA to distros.
You only need the CMA heap when you require uncached physically
contiguous buffers - for example Hantro on iMX but, this is not the case
on qcom hardware.
We can safely drop these CMA nodes for CAMSS.
---
bod
prev parent reply other threads:[~2025-02-27 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 14:29 Nikita Travkin
2025-02-26 14:29 ` [PATCH 1/2] arm64: dts: qcom: qrb5165-rb5-vision-mezzanine: Fix broken overlay root Nikita Travkin
2025-02-26 19:22 ` Rob Herring
2025-02-27 9:18 ` Nikita Travkin
2025-02-26 14:29 ` [PATCH 2/2] arm64: dts: qcom: sdm845-db845c-navigation-mezzanine: Fix the " Nikita Travkin
2025-02-27 4:16 ` [PATCH 0/2] {vision/navigation}-mezzanine: Fix overlay root node Dmitry Baryshkov
2025-02-27 9:01 ` Nikita Travkin
2025-02-27 14:57 ` Dmitry Baryshkov
2025-02-27 11:12 ` Bryan O'Donoghue [this message]
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=d12ba10b-6eb3-4344-af50-dba80c79791e@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®