From: Dhruva Gole <d-gole@ti.com>
To: Bryan Brattlof <bb@ti.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Vibhore Vardhan <vibhore@ti.com>,
ARM Power Management <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62P5 CPUFreq
Date: Wed, 11 Oct 2023 08:29:13 +0530 [thread overview]
Message-ID: <20231011025913.aadng3zuq6mpwjel@dhruva> (raw)
In-Reply-To: <20231010175524.558577-4-bb@ti.com>
Hi,
On Oct 10, 2023 at 12:55:25 -0500, Bryan Brattlof wrote:
> Hello everyone!
>
> This short series adds the am62p5 compatible to ti-cpufreq and
> cpufreq-dt-platdev for the new am62p family of TI SoCs. It uses the same
> A53s and efuse configuration as the rest of the am62xxx extended family
> so we're just using the same am625 data structure for the am62p5.
>
> Thanks for reviewing
> ~Bryan
>
> Bryan Brattlof (2):
> cpufreq: dt-platdev: add am62p5 to blocklist
> cpufreq: ti-cpufreq: Add opp support for am62p5 SoCs
>
> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
> drivers/cpufreq/ti-cpufreq.c | 1 +
> 2 files changed, 2 insertions(+)
For the series,
Reviewed-by: Dhruva Gole <d-gole@ti.com>
>
>
> base-commit: c9727271cb239dce91add464364f10fb2b376456
> --
> 2.42.0
>
--
Best regards,
Dhruva Gole <d-gole@ti.com>
next prev parent reply other threads:[~2023-10-11 2:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 17:55 [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62P5 CPUFreq Bryan Brattlof
2023-10-10 17:55 ` [PATCH 1/2] cpufreq: dt-platdev: add am62p5 to blocklist Bryan Brattlof
2023-10-10 17:55 ` [PATCH 2/2] cpufreq: ti-cpufreq: Add opp support for am62p5 SoCs Bryan Brattlof
2023-10-11 2:59 ` Dhruva Gole [this message]
2023-10-11 5:26 ` [PATCH 0/2] cpufreq: ti-cpufreq: Enable AM62P5 CPUFreq 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=20231011025913.aadng3zuq6mpwjel@dhruva \
--to=d-gole@ti.com \
--cc=bb@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=vibhore@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