From: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
To: Srinivas Kandagatla <srini@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: dts: qcom: glymur: Add QFPROM efuse support
Date: Mon, 27 Apr 2026 14:11:56 +0530 [thread overview]
Message-ID: <1cb7a0a5-4bc0-4391-9592-3909a627ea96@oss.qualcomm.com> (raw)
In-Reply-To: <20260331-glymur-qfprom-v1-0-5b4284d23c80@oss.qualcomm.com>
On 3/31/2026 7:24 PM, Pankaj Patil wrote:
> Add dt-bindings and dt-node for Glymur QFPROM efuse. The GPU speed bin
> child node nvmem cell contains details of clk frequencies supported by
> the GPU, which is then read by the GPU driver to select the correct set
> of operating performance points (OPPs) for the device
>
> Signed-off-by: Pankaj Patil <pankaj.patil@oss.qualcomm.com>
> ---
> Pankaj Patil (2):
> dt-bindings: nvmem: qfprom: Add glymur compatible
> arm64: dts: qcom: glymur: Add qfprom efuse node
>
> Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml | 1 +
> arch/arm64/boot/dts/qcom/glymur.dtsi | 12 ++++++++++++
> 2 files changed, 13 insertions(+)
> ---
> base-commit: cf7c3c02fdd0dfccf4d6611714273dcb538af2cb
> change-id: 20260311-glymur-qfprom-51c7521e4da0
>
> Best regards,
Reaching out about the patch series,
Wasn't acked and no outstanding review comments as well
prev parent reply other threads:[~2026-04-27 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 13:54 [PATCH 0/2] arm64: dts: qcom: glymur: Add QFPROM efuse support Pankaj Patil
2026-03-31 13:54 ` [PATCH 1/2] dt-bindings: nvmem: qfprom: Add glymur compatible Pankaj Patil
2026-04-01 7:49 ` Krzysztof Kozlowski
2026-03-31 13:54 ` [PATCH 2/2] arm64: dts: qcom: glymur: Add qfprom efuse node Pankaj Patil
2026-03-31 18:02 ` Dmitry Baryshkov
2026-04-01 8:56 ` Konrad Dybcio
2026-04-27 8:41 ` Pankaj Patil [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=1cb7a0a5-4bc0-4391-9592-3909a627ea96@oss.qualcomm.com \
--to=pankaj.patil@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=robh@kernel.org \
--cc=srini@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