From: Markus Schneider-Pargmann <msp@baylibre.com>
To: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Andrew Davis <afd@ti.com>, Dhruva Gole <d-gole@ti.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Markus Schneider-Pargmann <msp@baylibre.com>
Subject: [PATCH 0/3] arm64: am62: Use nvmem for chip information in opp table
Date: Tue, 6 Feb 2024 15:57:18 +0100 [thread overview]
Message-ID: <20240206145721.2418893-1-msp@baylibre.com> (raw)
Hi everyone,
the OPP table on am625 currently uses a syscon node to get required
information from efuse registers. As efuse registers contain many
different information, this series adds nvmem support for the TI OPP
table and cpufreq driver. This way just the specific information can be
referenced in the devicetree without the need to use a syscon reference.
The nvmem layout is added in my previous series, links are below.
This series is based on
https://lore.kernel.org/linux-arm-kernel/20240206143711.2410135-1-msp@baylibre.com/
Which is also available on my public git:
https://gitlab.baylibre.com/msp8/linux/-/tree/topic/ti-chipid-nvmem/v6.8?ref_type=heads
This series is available on git as well:
https://gitlab.baylibre.com/msp8/linux/-/tree/topic/ti-cpufreq-nvmem/v6.8?ref_type=heads
Best,
Markus
Markus Schneider-Pargmann (3):
dt-bindings: cpufreq: Add nvmem-cells for chip information
cpufreq: ti-cpufreq: Support nvmem for chip version
arm64: dts: ti: k3-am625: Use nvmem-cells for opp
.../opp/operating-points-v2-ti-cpu.yaml | 16 ++-
arch/arm64/boot/dts/ti/k3-am625.dtsi | 2 +
drivers/cpufreq/ti-cpufreq.c | 105 +++++++++++-------
3 files changed, 83 insertions(+), 40 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-06 14:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 14:57 Markus Schneider-Pargmann [this message]
2024-02-06 14:57 ` [PATCH 1/3] dt-bindings: cpufreq: Add nvmem-cells for chip information Markus Schneider-Pargmann
2024-02-15 7:26 ` Viresh Kumar
2024-02-15 8:25 ` Krzysztof Kozlowski
2024-02-15 8:36 ` Viresh Kumar
2024-02-15 8:24 ` Krzysztof Kozlowski
2024-02-17 14:27 ` Krzysztof Kozlowski
2024-02-15 8:59 ` Dhruva Gole
2024-02-17 14:27 ` Krzysztof Kozlowski
2024-02-06 14:57 ` [PATCH 2/3] cpufreq: ti-cpufreq: Support nvmem for chip version Markus Schneider-Pargmann
2024-02-15 9:13 ` Dhruva Gole
2024-02-06 14:57 ` [PATCH 3/3] arm64: dts: ti: k3-am625: Use nvmem-cells for opp Markus Schneider-Pargmann
2024-02-15 8:24 ` Krzysztof Kozlowski
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=20240206145721.2418893-1-msp@baylibre.com \
--to=msp@baylibre.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vigneshr@ti.com \
--cc=vireshk@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