[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200629080358.GA1217385@google.com>
Date: Mon, 29 Jun 2020 09:03:58 +0100
From: Quentin Perret <qperret@...gle.com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>,
Jonathan Corbet <corbet@....net>, linux-pm@...r.kernel.org,
Vincent Guittot <vincent.guittot@...aro.org>,
kernel-team@...roid.com, tkjos@...gle.com, adharmap@...eaurora.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 3/3] cpufreq: Specify default governor on command line
On Monday 29 Jun 2020 at 07:38:43 (+0530), Viresh Kumar wrote:
> On 26-06-20, 16:57, Quentin Perret wrote:
> > Do we need both cpufreq_param_governor and default_governor?
> > Could we move everything to only one of them? Something a little bit
> > like that maybe?
>
> No because we want to fallback to the default governor when the
> governor shown by the cpufreq_param_governor is valid but missing.
But that would still work with my suggestion no? You still fallback to
calling cpufreq_default_governor() in cpufreq_init_policy() if
get_governor(default_governor) doesn't succeed, so we should be covered.
Thanks,
Quentin
Powered by blists - more mailing lists