On 01/20/2016 06:36 PM, Viresh Kumar wrote:

On 20-01-16, 17:18, Stephen Boyd wrote:

quoted

Yeah I don't understand why we at least can't populate the OPP
structures and get the clocks and regulators for all the CPU
devices before we register the dt_cpufreq_driver structure. The
CPU devices should exist at that point, and we can wait to do
CPUfreq transitions until the regulators/clocks for all the CPUs
are registered. Sure we'd need to find the OPPs that are being
shared in the cpufreq_init callback and populate the cpu
frequency tables, etc., but that's not a big deal.

We can do this, yes. But ->init() was really the right place to fix
that, we aren't able to do it properly because we lack a cpu processor
driver for ARM.

Sorry I don't understand why ->init() is so important here. It seems
like ->init() is being used because we lack a proper processor driver on
ARM, but it isn't required and I don't see how it could be the right
place to handle any probe defer stuff because that's already been
rejected by Rafael and Greg.

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project