[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a15ab80f732ae22f12a1351550be6dc@codeaurora.org>
Date: Wed, 20 Jun 2018 14:38:58 +0530
From: sricharan@...eaurora.org
To: Sudeep Holla <sudeep.holla@....com>
Cc: mark.rutland@....com, robh@...nel.org, linux@....linux.org.uk,
ctatlor97@...il.com, rjw@...ysocki.net, viresh.kumar@...aro.org,
mturquette@...libre.com, linux-pm@...r.kernel.org,
sboyd@...eaurora.org, linux@...linux.org.uk,
thierry.escande@...aro.org, linux-kernel@...r.kernel.org,
david.brown@...aro.org, devicetree@...r.kernel.org,
linux-arm-msm@...r.kernel.org, andy.gross@...aro.org,
linux-soc@...r.kernel.org, linux-clk@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v10 13/14] cpufreq: Add module to register cpufreq on
Krait CPUs
Hi Sudeep,
>>
>> 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.
Correct, having these two merged was pointed out earlier as well by
Viresh.
Now that kryo is merged, i will check once and see if they can be
nicely
merged.
Regards,
Sricharan
Powered by blists - more mailing lists