From: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sibi.sankar@oss.qualcomm.com,
pankaj.patil@oss.qualcomm.com, rajendra.nayak@oss.qualcomm.com
Subject: Re: [PATCH 2/3] arm64: dts: qcom: Commonize Glymur CRD DTSI
Date: Thu, 12 Mar 2026 14:10:32 +0530 [thread overview]
Message-ID: <0330abfa-7932-404f-b3e3-f43251db2e0f@oss.qualcomm.com> (raw)
In-Reply-To: <rdnz6fc3jfypy7yh6lkswvacarketkcepi3zfaq6pxlsljilbp@yzsyuirax2oy>
Hi Dmitry Baryshkov,
>> Commonize the existing Glymur DTSI to allow reuse across the different
>> Glymur SKUs.
>
> Is Mahua a Glymur SKU?
Yes, Mahua is a variant of Glymur SoC with the same silicon but with the
third CPU cluster disabled.
>>
>> Also leave PCIe3b nodes disabled until the PCIe3b PHY init sequence
>> support gets added, since it's disabled at the UEFI level by default.
>>
>> Signed-off-by: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/glymur-crd.dts | 586 +-----------------
>> .../qcom/{glymur-crd.dts => glymur-crd.dtsi} | 7 -
>> 2 files changed, 1 insertion(+), 592 deletions(-)
>> copy arch/arm64/boot/dts/qcom/{glymur-crd.dts => glymur-crd.dtsi} (99%)
>>
>
next prev parent reply other threads:[~2026-03-12 8:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 5:49 [PATCH 0/3] Mahua SoC and CRD DT support Gopikrishna Garmidi
2026-03-10 5:49 ` [PATCH 1/3] dt-bindings: arm: qcom: Document Mahua SoC and board Gopikrishna Garmidi
2026-03-11 10:15 ` Krzysztof Kozlowski
2026-03-10 5:49 ` [PATCH 2/3] arm64: dts: qcom: Commonize Glymur CRD DTSI Gopikrishna Garmidi
2026-03-12 3:03 ` Dmitry Baryshkov
2026-03-12 8:40 ` Gopikrishna Garmidi [this message]
2026-03-12 15:18 ` Dmitry Baryshkov
2026-03-13 6:31 ` Gopikrishna Garmidi
2026-03-10 5:49 ` [PATCH 3/3] arm64: dts: qcom: Add Mahua SoC and CRD Gopikrishna Garmidi
2026-03-12 3:02 ` Dmitry Baryshkov
2026-03-13 7:08 ` Manaf Meethalavalappu Pallikunhi
2026-03-13 10:01 ` Dmitry Baryshkov
2026-03-13 10:06 ` Konrad Dybcio
2026-03-13 16:27 ` Dmitry Baryshkov
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=0330abfa-7932-404f-b3e3-f43251db2e0f@oss.qualcomm.com \
--to=gopikrishna.garmidi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.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=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
all inboxes | Powered by JetHome®