From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Gopikrishna Garmidi <gopikrishna.garmidi@oss.qualcomm.com>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Qiang Yu <qiang.yu@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Sivansh Gupta <sivansh.gupta@oss.qualcomm.com>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
Jyothi Kumar Seerapu <jyothi.seerapu@oss.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
Subject: Re: [PATCH v3 5/8] dt-bindings: arm: qcom: Add Glymur SIP CRD
Date: Mon, 9 Nov 2026 13:29:09 +0100 [thread overview]
Message-ID: <20261109-adept-unbreakable-gerbil-3f375f@quoll> (raw)
In-Reply-To: <20261106-topic-sip_cob-v3-5-52cd3826ab49@oss.qualcomm.com>
On Fri, Nov 06, 2026 at 10:29:06AM +0100, Konrad Dybcio wrote:
> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>
> Document the compatible for the Glymur CRD variant which uses the
> System-in-Package variant of the chip (different package and power
> grid). The rest of the board is seemingly identical.
>
> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-09 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 9:29 [PATCH v3 0/8] Commonize Glymur regulator settings for fixed rails Konrad Dybcio
2026-11-06 9:29 ` [PATCH v3 1/8] arm64: dts: qcom: Unify Glymur/Mahua regulator handles Konrad Dybcio
2026-11-09 8:43 ` Abel Vesa
2026-11-06 9:29 ` [PATCH v3 2/8] arm64: dts: qcom: Consolidate Glymur CoB power grid Konrad Dybcio
2026-11-09 8:43 ` Abel Vesa
2026-11-06 9:29 ` [PATCH v3 3/8] arm64: dts: qcom: glymur: Drop L4F0 Konrad Dybcio
2026-11-06 9:29 ` [PATCH v3 4/8] arm64: dts: qcom: glymur-crd: Fix L8B0 voltage Konrad Dybcio
2026-11-09 8:43 ` Abel Vesa
2026-11-06 9:29 ` [PATCH v3 5/8] dt-bindings: arm: qcom: Add Glymur SIP CRD Konrad Dybcio
2026-11-09 12:29 ` Krzysztof Kozlowski [this message]
2026-11-06 9:29 ` [PATCH v3 6/8] arm64: dts: qcom: Consolidate Glymur SiP power grid Konrad Dybcio
2026-11-09 8:45 ` Abel Vesa
2026-11-06 9:29 ` [PATCH v3 7/8] arm64: dts: qcom: glymur-crd: Move DP0/DP1 to common dtsi Konrad Dybcio
2026-11-09 8:46 ` Abel Vesa
2026-11-06 9:29 ` [PATCH v3 8/8] arm64: dts: qcom: Add Glymur SiP CRD Konrad Dybcio
2026-11-09 8:46 ` Abel Vesa
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=20261109-adept-unbreakable-gerbil-3f375f@quoll \
--to=krzk@kernel.org \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gopikrishna.garmidi@oss.qualcomm.com \
--cc=jyothi.seerapu@oss.qualcomm.com \
--cc=kamal.wadhwa@oss.qualcomm.com \
--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=pankaj.patil@oss.qualcomm.com \
--cc=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@oss.qualcomm.com \
--cc=sivansh.gupta@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®