From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: Feng Xiao <xf@rock-chips.com>,
linux@arm.linux.org.uk, rjw@rjwysocki.net,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, wxt@rock-chips.com, zyw@rock-chips.com,
jay.xu@rock-chips.com, tim.chen@rock-chips.com,
xxx@rock-chips.com, huangtao@rock-chips.com,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>
Subject: Re: [PATCH] cpufreq: rockchip: add driver
Date: Mon, 21 Mar 2016 15:20:49 +0530 [thread overview]
Message-ID: <20160321095049.GD27778@vireshk-i7> (raw)
In-Reply-To: <1787319.AFAWVqkdk0@diego>
On 18-03-16, 13:56, Heiko Stübner wrote:
> Also, on both the rk3368 as well as the rk3399, you probably want the cluster-
> handling of arm-bL-cpufreq-dt.
> Contrary to its name it is _not_ limited to switching between clusters, but
> can also control frequencies of multiple cpu-clusters running at the same
> time.
We aren't adding any new users to bL driver, please use cpufreq-dt as that also
supports multiple clusters now.
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: rockchip: add driver
Date: Mon, 21 Mar 2016 15:20:49 +0530 [thread overview]
Message-ID: <20160321095049.GD27778@vireshk-i7> (raw)
In-Reply-To: <1787319.AFAWVqkdk0@diego>
On 18-03-16, 13:56, Heiko St?bner wrote:
> Also, on both the rk3368 as well as the rk3399, you probably want the cluster-
> handling of arm-bL-cpufreq-dt.
> Contrary to its name it is _not_ limited to switching between clusters, but
> can also control frequencies of multiple cpu-clusters running at the same
> time.
We aren't adding any new users to bL driver, please use cpufreq-dt as that also
supports multiple clusters now.
--
viresh
next prev parent reply other threads:[~2016-03-21 9:51 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 12:10 [PATCH] cpufreq: rockchip: add driver Feng Xiao
2016-03-18 12:10 ` Feng Xiao
2016-03-18 12:56 ` Heiko Stübner
2016-03-18 12:56 ` Heiko Stübner
2016-03-21 9:50 ` Viresh Kumar [this message]
2016-03-21 9:50 ` Viresh Kumar
2016-03-21 9:54 ` Heiko Stübner
2016-03-21 9:54 ` Heiko Stübner
2016-03-21 9:58 ` Viresh Kumar
2016-03-21 9:58 ` Viresh Kumar
2016-03-21 13:24 ` Feng Xiao
2016-03-21 13:24 ` Feng Xiao
2016-03-21 15:13 ` Viresh Kumar
2016-03-21 15:13 ` Viresh Kumar
2016-03-21 15:13 ` Heiko Stübner
2016-03-21 15:13 ` Heiko Stübner
2016-03-21 15:52 ` Heiko Stübner
2016-03-21 15:52 ` Heiko Stübner
2016-03-22 1:28 ` Feng Xiao
2016-03-22 1:28 ` Feng Xiao
2016-03-22 1:28 ` Feng Xiao
2016-03-22 11:57 ` [PATCH v1] " Feng Xiao
2016-03-22 11:57 ` Feng Xiao
2016-03-22 16:07 ` Heiko Stübner
2016-03-22 16:07 ` Heiko Stübner
2016-03-23 2:18 ` [PATCH v2] " Feng Xiao
2016-03-23 2:18 ` Feng Xiao
2016-03-23 4:40 ` Viresh Kumar
2016-03-23 4:40 ` Viresh Kumar
2016-03-24 3:01 ` Feng Xiao
2016-03-24 3:01 ` Feng Xiao
2016-03-24 3:01 ` Feng Xiao
2016-03-24 6:43 ` Viresh Kumar
2016-03-24 6:43 ` Viresh Kumar
2016-03-24 15:09 ` Finley Xiao
2016-03-24 15:09 ` Finley Xiao
2016-03-25 4:42 ` Viresh Kumar
2016-03-25 4:42 ` 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=20160321095049.GD27778@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=tim.chen@rock-chips.com \
--cc=wxt@rock-chips.com \
--cc=xf@rock-chips.com \
--cc=xxx@rock-chips.com \
--cc=zyw@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.