linux-kernel - Re: [PATCH v2] drivers: cpufreq: sun8i-r40: Add cpufreq support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 12 May 2022 14:22:33 +0800
From:   qianfan <qianfanguijin@....com>
To:     Viresh Kumar <viresh.kumar@...aro.org>
Cc:     Jernej Škrabec <jernej.skrabec@...il.com>,
        linux-sunxi@...ts.linux.dev, Rob Herring <robh+dt@...nel.org>,
        Maxime Ripard <mripard@...nel.org>,
        Chen-Yu Tsai <wens@...e.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>,
        devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2] drivers: cpufreq: sun8i-r40: Add cpufreq support



在 2022/5/12 12:58, Viresh Kumar 写道:
> On 12-05-22, 12:34, qianfan wrote:
>> Actually I'm not make sure the difference, seems both of them can work.
>> Most of allwinner device_id is added in allowlist, so I did this.
> For OPP V1 the cpufreq device isn't created by default and hence the allowlist
> allows us to know the devices for which the device shall be created.
>
> For OPP V2, we have the compatible string available and with help of that we
> create a device without need of any entry to any list. The blocklist however
> allows us to skip creating the device for some platforms, which don't want it.
>
> As your case is opp-v2 and you want the device, you aren't required to add entry
> anywhere.
I read the source code again and understand the behaivors.
And I will it from allowlist.

Thanks
>