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
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
On 2018-06-19 20:59, Craig Tatlor wrote:
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.
ok, atleast on my ipq8064, it works
On 2018-06-19 20:59, Craig Tatlor wrote:
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.
ok, atleast on my ipq8064, it works
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
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
On 19/06/18 14:45, Sricharan R wrote:
> From: Stephen Boyd
>
> 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
On 19/06/18 14:45, Sricharan R wrote:
> From: Stephen Boyd
>
> 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
From: Stephen Boyd
Register a cpufreq-generic device whenever we detect that a
"qcom,krait" compatible CPU is present in DT.
Acked-by: Viresh Kumar
[Sricharan: updated to use dev_pm_opp_set_prop_name and
nvmem apis]
Signed-off-by: Sricharan R
[Thierry Escande: update to add
From: Stephen Boyd
Register a cpufreq-generic device whenever we detect that a
"qcom,krait" compatible CPU is present in DT.
Acked-by: Viresh Kumar
[Sricharan: updated to use dev_pm_opp_set_prop_name and
nvmem apis]
Signed-off-by: Sricharan R
[Thierry Escande: update to add
10 matches
Mail list logo
