Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1712773

Re: [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2

From Chen-Yu Tsai <wens@csie.org>
Newsgroups linux.kernel
Subject Re: [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2
Date 2017-08-16 10:50 +0200
Message-ID <uf2bw-4Pi-13@gated-at.bofh.it> (permalink)
References <ueZdD-30Q-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Wed, Aug 16, 2017 at 1:37 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> The initial idea of creating the cpufreq-dt-platdev.c file was to keep a
> list of platforms that use the "operating-points" (V1) bindings and
> create cpufreq device for them only, as we weren't sure which platforms
> would want the device to get created automatically as some had their own
> cpufreq drivers as well, or wanted to initialize cpufreq after doing
> some stuff from platform code.
>
> But that wasn't the case with platforms using "operating-points-v2"
> property. We wanted the device to get created automatically without the
> need of adding them to the whitelist. Though, we will still have some
> exceptions where we don't want to create the device automatically.
>
> Rename the earlier platform list as *whitelist* and create a new
> *blacklist* as well.
>
> The cpufreq-dt device will get created if:
> - The platform is there in the whitelist OR
> - The platform has "operating-points-v2" property in CPU0's DT node and
>   isn't part of the blacklist .
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>

Does this mean "cpufreq: dt: Add support for some new Allwinner SoCs",
or any other patch adding new SoCs to the list, isn't needed anymore?

ChenYu

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq device with OPP v2 Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-16 07:40 +0200
  [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-16 07:40 +0200
    Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Geert Uytterhoeven <geert@linux-m68k.org> - 2017-08-16 09:00 +0200
      Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Simon Horman <horms@verge.net.au> - 2017-08-17 10:00 +0200
        Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-17 10:50 +0200
        Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Simon Horman <horms@verge.net.au> - 2017-08-21 15:30 +0200
    Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Chen-Yu Tsai <wens@csie.org> - 2017-08-16 11:00 +0200
      Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-16 13:30 +0200
        Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Chen-Yu Tsai <wens@csie.org> - 2017-08-17 19:10 +0200
    Re: [PATCH 2/2] cpufreq: dt-platdev: Drop few entries from whitelist Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-08-23 05:40 +0200
  Re: [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq  device with OPP v2 Chen-Yu Tsai <wens@csie.org> - 2017-08-16 10:50 +0200
    Re: [PATCH 1/2] cpufreq: dt-platdev: Automatically create cpufreq  device with OPP v2 Viresh Kumar <viresh.kumar@linaro.org> - 2017-08-16 13:30 +0200
  Re: [1/2] cpufreq: dt-platdev: Automatically create cpufreq device  with OPP v2 Simon Horman <horms@verge.net.au> - 2017-08-21 15:20 +0200
    Re: [1/2] cpufreq: dt-platdev: Automatically create cpufreq device  with OPP v2 Masahiro Yamada <yamada.masahiro@socionext.com> - 2017-08-23 05:50 +0200

csiph-web