From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gopikrishna Garmidi <gopikrishna.garmidi@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 1/3] dt-bindings: arm: qcom: Document Mahua SoC and board
Date: Wed, 11 Mar 2026 11:15:44 +0100 [thread overview]
Message-ID: <20260311-sloppy-weightless-tiger-cb3770@quoll> (raw)
In-Reply-To: <20260310054947.2114445-2-gopikrishna.garmidi@oss.qualcomm.com>
On Mon, Mar 09, 2026 at 10:49:45PM -0700, Gopikrishna Garmidi wrote:
> Mahua is a derivative of Glymur with the third CPU cluster disabled.
"of Glymur SoC"
No need to send new version just for that
> Document the compatible strings for the Mahua SoC and the Compute
> Reference Device (CRD) board based on it.
>
> Signed-off-by: Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-11 10:15 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 [this message]
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
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=20260311-sloppy-weightless-tiger-cb3770@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gopikrishna.garmidi@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®