Devicetree
 help / color / mirror / Atom feed
From: Alexander Koskovich <akoskovich@pm.me>
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: Luca Weiss <luca.weiss@fairphone.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alexander Koskovich <akoskovich@pm.me>
Subject: [PATCH 0/2] arm64: dts: qcom: milos: Add QFPROM efuse support
Date: Wed, 01 Apr 2026 02:24:51 +0000	[thread overview]
Message-ID: <20260331-milos-qfprom-v1-0-36017cc642db@pm.me> (raw)

Add dt-bindings and dt-node for Milos QFPROM efuse. The GPU speed bin child
node nvmem cell contains details of clk frequencies supported by the GPU,
which can then read by the GPU driver to select the correct set of operating
performance points (OPPs) for the device in the future once all the possible
speedbins for Milos are known.

Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
---
Alexander Koskovich (2):
      dt-bindings: nvmem: qfprom: Add Milos compatible
      arm64: dts: qcom: milos: Add qfprom efuse node

 Documentation/devicetree/bindings/nvmem/qcom,qfprom.yaml |  1 +
 arch/arm64/boot/dts/qcom/milos.dtsi                      | 12 ++++++++++++
 2 files changed, 13 insertions(+)
---
base-commit: 7aaa8047eafd0bd628065b15757d9b48c5f9c07d
change-id: 20260331-milos-qfprom-1b00c2892171

Best regards,
-- 
Alexander Koskovich <akoskovich@pm.me>



             reply	other threads:[~2026-04-01  2:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01  2:24 Alexander Koskovich [this message]
2026-04-01  2:24 ` [PATCH 1/2] dt-bindings: nvmem: qfprom: Add Milos compatible Alexander Koskovich
2026-04-01 10:55   ` Krzysztof Kozlowski
2026-05-12 20:47   ` Bjorn Andersson
2026-04-01  2:25 ` [PATCH 2/2] arm64: dts: qcom: milos: Add qfprom efuse node Alexander Koskovich
2026-04-01  9:41   ` Konrad Dybcio
2026-04-01 11:16   ` 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=20260331-milos-qfprom-v1-0-36017cc642db@pm.me \
    --to=akoskovich@pm.me \
    --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=luca.weiss@fairphone.com \
    --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