From: Vibhore Vardhan <vibhore@ti.com>
To: <rafael@kernel.org>, <viresh.kumar@linaro.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<vigneshr@ti.com>, <d-gole@ti.com>,
Vibhore Vardhan <vibhore@ti.com>
Subject: [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62A7 CPUFreq
Date: Fri, 26 May 2023 09:43:52 -0500 [thread overview]
Message-ID: <20230526144354.38478-1-vibhore@ti.com> (raw)
Hi,
This series adds cpufreq support for TI AM62A7 SoC.
AM62A7 has the same A53 and efuse configuration as AM625. Thus, soc_data
from AM625 is reused. This series adds compatible string for AM62A7 to
ti-cpufreq and cpufreq-dt-platdev drivers respectively.
Tested on am62a-sk board using manual frequency changes and then reading
back frequency with k3conf, and this shows matching frequency to what
was set.
Link to the complete series including the DT patches:
https://github.com/DhruvaG2000/v-linux/commits/am62a_cpufreq_2023
Based on patch series for AM625 by Dave Gerlach.
Regards,
Vibhore
Vibhore Vardhan (2):
cpufreq: ti-cpufreq: Add support for AM62A7
cpufreq: dt-platdev: Blacklist ti,am62a7 SoC
drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
drivers/cpufreq/ti-cpufreq.c | 1 +
2 files changed, 2 insertions(+)
--
2.34.1
next reply other threads:[~2023-05-26 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 14:43 Vibhore Vardhan [this message]
2023-05-26 14:43 ` [PATCH 1/2] cpufreq: ti-cpufreq: Add support for AM62A7 Vibhore Vardhan
2023-05-26 14:43 ` [PATCH 2/2] cpufreq: dt-platdev: Blacklist ti,am62a7 SoC Vibhore Vardhan
2023-05-26 15:49 ` [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62A7 CPUFreq Dhruva Gole
2023-05-29 5:04 ` Viresh Kumar
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=20230526144354.38478-1-vibhore@ti.com \
--to=vibhore@ti.com \
--cc=d-gole@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--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