linux-kernel - Re: [EXT] Re: [PATCH 2/2] cpufreq: dt-platdev: Support building cpufreq platdev driver as module

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]

Message-ID: <20230831105019.tre5hgoad5tpiwwx@vireshk-i7>
Date:   Thu, 31 Aug 2023 16:20:19 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Zhipeng Wang <zhipeng.wang_1@....com>,
        "rafael@...nel.org" <rafael@...nel.org>,
        "linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [EXT] Re: [PATCH 2/2] cpufreq: dt-platdev: Support building
 cpufreq platdev driver as module

On 30-08-23, 07:08, Aurelien Jarno wrote:
> Hi,
> 
> On 2023-08-30 03:09, Zhipeng Wang wrote:
> > Hi Aurelien,
> > 
> > I'm not sure why we need to make cpufreq-dt-platdev autoloading, does it make sense? As I understand it we need to actively modprobe cpufreq-dt-platdev, why not?
> 
> This is needed to recover the old behavior, where if a CPU supports
> cpufreq-dt, it get loaded automatically. Now users has to modprobe
> cpufreq-dt-platdev explicitly to get cpufreq-dt to work. This seems like
> a regression to me.
> 
> Of course one can explicitly make CPUFREQ_DT_PLATDEV=y, but the default
> is to build cpufreq-dt-platdev as module when cpufreq-dt is built as
> module.

Feel free to send me a patch to make this auto-load.

-- 
viresh