From: Bryan Brattlof <bb@ti.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Vibhore Vardhan <vibhore@ti.com>, <linux-pm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Bryan Brattlof <bb@ti.com>
Subject: [PATCH v2 0/5] Update OPP table and add entries for AM62Ax & AM62Px SoCs
Date: Wed, 12 Jun 2024 18:17:33 -0500 [thread overview]
Message-ID: <20240612-ti-opp-updates-v2-0-422b6747a254@ti.com> (raw)
Hello Everyone
This series starts off the process of updating the OPP decoding tables
to align with the new speed grade schemes for TI's AM62Ax and AM62Px SoC
families.
Following this update is the updated binding and the OPPv2 entries we
will be using for the SoC including the 1.4GHz frequency for our
reference boards when the VDD_CORE allows.
Thanks for reviewing
~Bryan
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
Changes in v2:
- removed errant DONOTMERGE tag
- Link to v1: https://lore.kernel.org/r/20240612-ti-opp-updates-v1-0-3551c31d9872@ti.com
---
Bryan Brattlof (5):
cpufreq: ti: update OPP table for AM62Ax SoCs
cpufreq: ti: update OPP table for AM62Px SoCs
dt-bindings: mfd: syscon: add TI's opp table compatible
DONOTMERGE: arm64: dts: ti: k3-am62p: add in opp tables
DONOTMERGE: arm64: dts: ti: k3-am62a: add in opp table
Documentation/devicetree/bindings/mfd/syscon.yaml | 1 +
arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi | 5 ++
arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 9 +++
arch/arm64/boot/dts/ti/k3-am62a7.dtsi | 51 ++++++++++++
arch/arm64/boot/dts/ti/k3-am62p-wakeup.dtsi | 6 ++
arch/arm64/boot/dts/ti/k3-am62p5-sk.dts | 9 +++
arch/arm64/boot/dts/ti/k3-am62p5.dtsi | 47 ++++++++++++
drivers/cpufreq/ti-cpufreq.c | 94 ++++++++++++++++++++++-
8 files changed, 220 insertions(+), 2 deletions(-)
---
base-commit: 629b57597ab52cef2ac5dd16042183c298cc52ed
change-id: 20240509-ti-opp-updates-19c109ab1354
Best regards,
--
Bryan Brattlof <bb@ti.com>
next reply other threads:[~2024-06-12 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 23:17 Bryan Brattlof [this message]
2024-06-12 23:17 ` [PATCH v2 1/5] cpufreq: ti: update OPP table for AM62Ax SoCs Bryan Brattlof
2024-06-13 11:28 ` Dhruva Gole
2024-06-12 23:17 ` [PATCH v2 2/5] cpufreq: ti: update OPP table for AM62Px SoCs Bryan Brattlof
2024-06-13 11:33 ` Dhruva Gole
2024-06-15 14:50 ` Bryan Brattlof
2024-06-12 23:17 ` [PATCH v2 3/5] dt-bindings: mfd: syscon: add TI's opp table compatible Bryan Brattlof
2024-06-13 6:22 ` Krzysztof Kozlowski
2024-06-15 14:43 ` Bryan Brattlof
2024-06-12 23:17 ` [PATCH v2 4/5] DONOTMERGE: arm64: dts: ti: k3-am62p: add in opp tables Bryan Brattlof
2024-06-12 23:17 ` [PATCH v2 5/5] DONOTMERGE: arm64: dts: ti: k3-am62a: add in opp table Bryan Brattlof
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=20240612-ti-opp-updates-v2-0-422b6747a254@ti.com \
--to=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.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@kernel.org \
--cc=vibhore@ti.com \
--cc=vigneshr@ti.com \
--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;
as well as URLs for NNTP newsgroup(s).