From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Hector Yuan <hector.yuan@mediatek.com>
Cc: kernel@collabora.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-pm@vger.kernel.org,
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Subject: [PATCH 0/5] MT8196 CPUFreq Support
Date: Fri, 11 Jul 2025 16:57:32 +0200 [thread overview]
Message-ID: <20250711-mt8196-cpufreq-v1-0-e1b0a3b4ac61@collabora.com> (raw)
This series adds the necessary bindings and driver changes to integrate
MT8196 CPUFreq into the existing mediatek-cpufreq-hw driver. This
necessitated two preparatory cleanup patches to the driver.
The CPU frequency was verified to actually be changing by comparing
sysbench cpu numbers between fdvfs being enabled and it not being
enabled.
Enablement in the DT will be done once the MT8196 DT lands, so don't be
surprised that no node uses these new compatibles so far.
Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
---
Nicolas Frattaroli (5):
dt-bindings: mfd: syscon: Add mt8196 fdvfs syscons
dt-bindings: cpufreq: mediatek-hw: add mt8196 cpufreq binding
cpufreq: mediatek-hw: Refactor match data into struct
cpufreq: mediatek-hw: Separate per-domain and per-instance data
cpufreq: mediatek-hw: Add support for MT8196
.../bindings/cpufreq/cpufreq-mediatek-hw.yaml | 64 +++++++++-
Documentation/devicetree/bindings/mfd/syscon.yaml | 4 +
drivers/cpufreq/mediatek-cpufreq-hw.c | 140 +++++++++++++++++----
3 files changed, 184 insertions(+), 24 deletions(-)
---
base-commit: 42f78243e0c6fe42f2710f98513a55c102347ff0
change-id: 20250711-mt8196-cpufreq-86d961e2300b
Best regards,
--
Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
next reply other threads:[~2025-07-11 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 14:57 Nicolas Frattaroli [this message]
2025-07-11 14:57 ` [PATCH 1/5] dt-bindings: mfd: syscon: Add mt8196 fdvfs syscons Nicolas Frattaroli
2025-07-14 8:47 ` AngeloGioacchino Del Regno
2025-07-14 11:58 ` Nicolas Frattaroli
2025-07-14 12:33 ` AngeloGioacchino Del Regno
2025-07-11 14:57 ` [PATCH 2/5] dt-bindings: cpufreq: mediatek-hw: add mt8196 cpufreq binding Nicolas Frattaroli
2025-07-11 14:57 ` [PATCH 3/5] cpufreq: mediatek-hw: Refactor match data into struct Nicolas Frattaroli
2025-07-11 14:57 ` [PATCH 4/5] cpufreq: mediatek-hw: Separate per-domain and per-instance data Nicolas Frattaroli
2025-07-11 14:57 ` [PATCH 5/5] cpufreq: mediatek-hw: Add support for MT8196 Nicolas Frattaroli
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=20250711-mt8196-cpufreq-v1-0-e1b0a3b4ac61@collabora.com \
--to=nicolas.frattaroli@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=viresh.kumar@linaro.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
all inboxes | Powered by JetHome®