Re: [PATCH v10 13/14] cpufreq: Add module to register cpufreq on Krait CPUs
From: Craig Tatlor <hidden>
Date: 2018-06-19 14:49:03
Also in:
linux-clk
From: Craig Tatlor <hidden>
Date: 2018-06-19 14:49:03
Also in:
linux-clk
The pvs refuse check is incorrect... With downstream it says it isn't blown and that it is 11, which also happens on upstream if I import it's efuse reading code from an older revision, or comment out the check. Also, I'm still getting my issue about clocks above 2,147,483,647hz however I think this may be related to the division in the hfpll driver so I'll have a debug around there. On Tue, 19 Jun 2018, 14:56 Sudeep Holla, [off-list ref] wrote:
On 19/06/18 14:45, Sricharan R wrote:quoted
From: Stephen Boyd <redacted> 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