From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Mikko Perttunen <cyndis@kapsi.fi>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Mikko Perttunen <mperttunen@nvidia.com>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 1/3] cpufreq: Add Tegra186 cpufreq driver
Date: Thu, 20 Apr 2017 02:46:37 +0200 [thread overview]
Message-ID: <4060196.qTg8b6XvfH@aspire.rjw.lan> (raw)
In-Reply-To: <ce29c6b7-2942-0054-d014-7b262da6fb6d@kapsi.fi>
On Tuesday, April 11, 2017 09:37:28 AM Mikko Perttunen wrote:
> On 04/11/2017 09:35 AM, Viresh Kumar wrote:
> > On 04-04-17, 16:43, Mikko Perttunen wrote:
> >> Add a new cpufreq driver for Tegra186 (and likely later).
> >> The CPUs are organized into two clusters, Denver and A57,
> >> with two and four cores respectively. CPU frequency can be
> >> adjusted by writing the desired rate divisor and a voltage
> >> hint to a special per-core register.
> >>
> >> The frequency of each core can be set individually; however,
> >> this is just a hint as all CPUs in a cluster will run at
> >> the maximum rate of non-idle CPUs in the cluster.
> >>
> >> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> >> ---
> >> v2:
> >> - Many cosmetic / restructuring changes
> >> - Only one aperture read from DT now, with a new
> >> structure containing the offset among other details
> >> per cluster.
> >> - Don't enable the driver by default.
> >>
> >> drivers/cpufreq/Kconfig.arm | 6 +
> >> drivers/cpufreq/Makefile | 1 +
> >> drivers/cpufreq/tegra186-cpufreq.c | 275 +++++++++++++++++++++++++++++++++++++
> >> 3 files changed, 282 insertions(+)
> >> create mode 100644 drivers/cpufreq/tegra186-cpufreq.c
> >
> > For all three patches.
> >
> > Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
I've applied the [1/3], but ACKs from the DT maintainers are needed for the
other two.
Thanks,
Rafael
next prev parent reply other threads:[~2017-04-20 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 13:43 Mikko Perttunen
2017-04-04 13:43 ` [PATCH v2 2/3] dt-bindings: Add bindings for nvidia,tegra186-ccplex-cluster Mikko Perttunen
2017-04-20 6:43 ` Mikko Perttunen
2017-04-04 13:43 ` [PATCH v2 3/3] arm64: tegra: Add CCPLEX_CLUSTER area in Tegra186 Mikko Perttunen
2017-04-20 6:44 ` Mikko Perttunen
2017-04-11 6:35 ` [PATCH v2 1/3] cpufreq: Add Tegra186 cpufreq driver Viresh Kumar
2017-04-11 6:37 ` Mikko Perttunen
2017-04-20 0:46 ` Rafael J. Wysocki [this message]
2017-04-11 8:09 ` [PATCH v3 " Mikko Perttunen
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=4060196.qTg8b6XvfH@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=cyndis@kapsi.fi \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=thierry.reding@gmail.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
all inboxes | Powered by JetHome®