[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f195e30e-bef3-9352-9584-fec35631ec5e@arm.com>
Date: Tue, 19 Jun 2018 14:56:31 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Sricharan R <sricharan@...eaurora.org>
Cc: robh@...nel.org, viresh.kumar@...aro.org, mark.rutland@....com,
mturquette@...libre.com, sboyd@...eaurora.org,
linux@...linux.org.uk, andy.gross@...aro.org,
david.brown@...aro.org, rjw@...ysocki.net,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
linux-pm@...r.kernel.org, linux@....linux.org.uk,
thierry.escande@...aro.org, ctatlor97@...il.com,
Sudeep Holla <sudeep.holla@....com>
Subject: Re: [PATCH v10 13/14] cpufreq: Add module to register cpufreq on
Krait CPUs
On 19/06/18 14:45, Sricharan R wrote:
> From: Stephen Boyd <sboyd@...eaurora.org>
>
> Register a cpufreq-generic device whenever we detect that a
> "qcom,krait" compatible CPU is present in DT.
>
Just curious to know how different is this from qcom kryo driver
that was added recently. IIRC even that gets the speedbin from nvmem.
Can they be merged ? I don't see need to have different driver for Krait
and Kryo CPUs when the code is not even remotely related to CPU type.
Sorry if I have missed anything from previous versions, I just happen
to open and looked at this series first time today.
--
Regards,
Sudeep
Powered by blists - more mailing lists