From: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
To: 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>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sibi.sankar@oss.qualcomm.com,
rajendra.nayak@oss.qualcomm.com
Subject: Re: [PATCH v2] arm64: dts: qcom: glymur-crd: Move common board nodes to shared DTSI
Date: Mon, 8 Jun 2026 15:33:29 +0530 [thread overview]
Message-ID: <b61ec109-92db-4dc1-ba7d-a5ce79fea08a@oss.qualcomm.com> (raw)
In-Reply-To: <20260519-glymur-mahua-common-nodes-v2-1-9f1b89a3f398@oss.qualcomm.com>
On 5/19/2026 7:55 PM, Gopikrishna Garmidi wrote:
> The Glymur and Mahua CRDs use the same board-level hardware for the
> eDP display panel, MDSS DP3 controller and PHY, USB-C ports (via
> pmic-glink), USB 0/1/HS/MP controllers, QMP PHYs, eUSB2 repeaters,
> HID peripherals (touchpad, keyboard, touchscreen) and their dependent
> regulators and pin control states. This has been verified against
> both CRD schematics.
>
> Move these nodes from glymur-crd.dts to glymur-crd.dtsi to enable code
> reuse with the Mahua CRD.
>
> Signed-off-by: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
> ---
> Changes in v2:
> - Rebased on top of next-20260518
> - Updated subject to include glymur-crd scope prefix
> - Rewrote commit message to describe the actual shared physical hardware
> rather than the code-sharing intent; the commonality was verified
> against Glymur CRD and Mahua CRD schematics
> - Link to v1: https://lore.kernel.org/r/20260326-glymur-mahua-common-nodes-v1-1-12bb26920ea4@oss.qualcomm.com
> ---
> arch/arm64/boot/dts/qcom/glymur-crd.dts | 399 -------------------------------
> arch/arm64/boot/dts/qcom/glymur-crd.dtsi | 396 ++++++++++++++++++++++++++++++
> 2 files changed, 396 insertions(+), 399 deletions(-)
Hi Krzysztof, Konrad,
This has been waiting for a while now and already has a Reviewed-by from
Dmitry. Could you take a look when you get a chance?
Thanks,
Gopikrishna Garmidi
next prev parent reply other threads:[~2026-06-08 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 14:25 [PATCH v2] arm64: dts: qcom: glymur-crd: Move common board nodes to shared DTSI Gopikrishna Garmidi
2026-05-20 13:44 ` Dmitry Baryshkov
2026-06-08 10:03 ` Gopikrishna Garmidi [this message]
2026-06-16 12:04 ` Konrad Dybcio
2026-06-24 10:02 ` Pankaj Patil
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=b61ec109-92db-4dc1-ba7d-a5ce79fea08a@oss.qualcomm.com \
--to=gopikrishna.garmidi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=rajendra.nayak@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.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