[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200615174141.GA235811@google.com>
Date: Mon, 15 Jun 2020 18:41:41 +0100
From: Quentin Perret <qperret@...gle.com>
To: rjw@...ysocki.net, rafael@...nel.org, viresh.kumar@...aro.org
Cc: arnd@...db.de, mpe@...erman.id.au, benh@...nel.crashing.org,
paulus@...ba.org, mingo@...hat.com, peterz@...radead.org,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, kernel-team@...roid.com,
tkjos@...gle.com, adharmap@...eaurora.org
Subject: Re: [PATCH 2/2] cpufreq: Specify default governor on command line
On Monday 15 Jun 2020 at 17:55:54 (+0100), Quentin Perret wrote:
> static int cpufreq_init_governor(struct cpufreq_policy *policy)
> {
> int ret;
> @@ -2701,6 +2721,8 @@ int cpufreq_register_driver(struct cpufreq_driver *driver_data)
>
> if (driver_data->setpolicy)
> driver_data->flags |= CPUFREQ_CONST_LOOPS;
> + else
> + cpufreq_get_default_governor();
Looking at this again, it appears that the comment above
cpufreq_parse_governor() confused me a bit -- this needs doing
unconditionally I think.
I'll fix it in v2.
Thanks,
Quentin
Powered by blists - more mailing lists