From: Viresh Kumar <viresh.kumar@linaro.org>
To: Chen-Yu Tsai <wens@csie.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Wei Xu <xuwei5@hisilicon.com>, Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
jun.nie@linaro.org, Baoyou Xie <baoyou.xie@linaro.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist
Date: Wed, 16 Aug 2017 16:54:16 +0530 [thread overview]
Message-ID: <20170816112416.GD24299@vireshk-i7> (raw)
In-Reply-To: <CAGb2v65DokoXaJp=hdFpg0GgTs50ZMR=JrZB7zNwQntH14zj3Q@mail.gmail.com>
On 16-08-17, 16:53, Chen-Yu Tsai wrote:
> On Wed, Aug 16, 2017 at 1:37 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > Drop few ARM (32 and 64 bit) platforms from the whitelist which always
> > use "operating-points-v2" property from their DT. They should continue
> > to work after this patch.
> >
> > Tested on Hikey platform (only the "hisilicon,hi6220" entry).
> >
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > drivers/cpufreq/cpufreq-dt-platdev.c | 11 -----------
> > 1 file changed, 11 deletions(-)
> >
> > diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> > index 061b468512a2..45f2ec3b7f7a 100644
> > --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> > +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> > @@ -27,7 +27,6 @@ static const struct of_device_id whitelist[] __initconst = {
> > { .compatible = "allwinner,sun6i-a31s", },
> > { .compatible = "allwinner,sun7i-a20", },
> > { .compatible = "allwinner,sun8i-a23", },
> > - { .compatible = "allwinner,sun8i-a33", },
> > { .compatible = "allwinner,sun8i-a83t", },
> > { .compatible = "allwinner,sun8i-h3", },
> >
>
> Acked-by: Chen-Yu Tsai <wens@csie.org>
>
> In fact, we can drop all the sun8i entries. Of them, only sun8i-a33 has
> cpufreq implemented. All the other ones are missing thermal sensor support,
> and no OPP tables have been added yet.
Then, why did you guys add all those SoCs there ? :)
--
viresh
next prev parent reply other threads:[~2017-08-16 11:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 5:37 [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2 Viresh Kumar
2017-08-16 5:37 ` [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Viresh Kumar
2017-08-16 6:51 ` Geert Uytterhoeven
2017-08-17 7:53 ` Simon Horman
2017-08-17 8:40 ` Viresh Kumar
2017-08-21 13:19 ` Simon Horman
2017-08-16 8:53 ` Chen-Yu Tsai
2017-08-16 11:24 ` Viresh Kumar [this message]
2017-08-17 17:00 ` Chen-Yu Tsai
2017-08-23 3:33 ` Masahiro Yamada
2017-08-16 8:49 ` [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2 Chen-Yu Tsai
2017-08-16 11:23 ` Viresh Kumar
2017-08-21 13:17 ` [1/2] " Simon Horman
2017-08-23 3:48 ` Masahiro Yamada
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=20170816112416.GD24299@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=baoyou.xie@linaro.org \
--cc=geert@linux-m68k.org \
--cc=jun.nie@linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=rjw@rjwysocki.net \
--cc=vincent.guittot@linaro.org \
--cc=wens@csie.org \
--cc=xuwei5@hisilicon.com \
--cc=yamada.masahiro@socionext.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 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).