From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
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>,
cros-qcom-dts-watchers@chromium.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: use DT label for DSI outputs
Date: Fri, 25 Jul 2025 10:22:36 +0200 [thread overview]
Message-ID: <36c8affa-336a-412d-8002-095fdf23a287@oss.qualcomm.com> (raw)
In-Reply-To: <20250725-msm-dsi-outs-v1-1-18401fb9fc53@oss.qualcomm.com>
On 7/25/25 4:59 AM, Dmitry Baryshkov wrote:
> Instead of keeping a copy of the DT tree going down to the DSI output
> endpoint use the label to reference it directly, making DTs less
> error-prone.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 12 ++++------
> arch/arm64/boot/dts/qcom/sc7180-idp.dts | 12 ++++------
> .../dts/qcom/sc7180-trogdor-quackingstick.dtsi | 12 ++++------
> .../boot/dts/qcom/sc7180-trogdor-wormdingler.dtsi | 12 ++++------
> arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 12 ++++------
> arch/arm64/boot/dts/qcom/sdm845-db845c.dts | 24 +++++++-------------
> arch/arm64/boot/dts/qcom/sdm845-mtp.dts | 26 ++++++++--------------
> .../boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 12 ++++------
> arch/arm64/boot/dts/qcom/sm8150-hdk.dts | 24 +++++++-------------
> arch/arm64/boot/dts/qcom/sm8350-hdk.dts | 12 ++++------
> .../boot/dts/qcom/sm8650-hdk-display-card.dtso | 15 +++----------
This file becomes different after the patch, but upon manual inspection,
it comes down to a phandle index shifting around (i.e. no *real* change)
Nice cleanup
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2025-07-25 8:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 2:59 Dmitry Baryshkov
2025-07-25 8:22 ` Konrad Dybcio [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=36c8affa-336a-412d-8002-095fdf23a287@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@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=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®