[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190129052144.plicqu4vozh3l3ss@vireshk-i7>
Date: Tue, 29 Jan 2019 10:51:44 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Matthias Kaehlcke <mka@...omium.org>
Cc: Quentin Perret <quentin.perret@....com>, rjw@...ysocki.net,
sudeep.holla@....com, liviu.dudau@....com,
lorenzo.pieralisi@....com, robh+dt@...nel.org,
mark.rutland@....com, nm@...com, sboyd@...nel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
dietmar.eggemann@....com
Subject: Re: [PATCH 2/7] cpufreq: dt: Register an Energy Model
On 28-01-19, 11:36, Matthias Kaehlcke wrote:
> I think this patch will result in error messages at registration on
> platforms that use the cpufreq-dt driver and don't specify
> 'dynamic-power-coefficient' for the CPUs in the DT. Not sure if that's
> a problem as long as the cpufreq initialization succeeds regardless,
> it could be seen as a not-so-gentle nudge to add the values.
That wouldn't be acceptable.
--
viresh
Powered by blists - more mailing lists