Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
On Mon, Dec 15, 2014 at 9:38 PM, Viresh Kumar wrote: > On 16 December 2014 at 11:02, Dmitry Torokhov wrote: >> Yes we will. Which simply means that this WARN is stupid. We also will >> hit it if there is no opp table and the allocation below fails; or if >> it succeeds then

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Viresh Kumar
On 16 December 2014 at 11:02, Dmitry Torokhov wrote: > Yes we will. Which simply means that this WARN is stupid. We also will > hit it if there is no opp table and the allocation below fails; or if > it succeeds then dev_pm_opp_init_cpufreq_table() will fail and we'll > hit this code path again.

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
On Mon, Dec 15, 2014 at 9:10 PM, Viresh Kumar wrote: > On 16 December 2014 at 05:40, Dmitry Torokhov wrote: >> cpufreq-dt driver supports mode when OPP table is provided by platform >> code and not device tree. However on certain platforms code that fills >> OPP table may run after cpufreq

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Viresh Kumar
On 16 December 2014 at 05:40, Dmitry Torokhov wrote: > cpufreq-dt driver supports mode when OPP table is provided by platform > code and not device tree. However on certain platforms code that fills > OPP table may run after cpufreq driver tries to initialize, so let's > report -EPROBE_DEFER if

[PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
cpufreq-dt driver supports mode when OPP table is provided by platform code and not device tree. However on certain platforms code that fills OPP table may run after cpufreq driver tries to initialize, so let's report -EPROBE_DEFER if we do not find any entires in OPP table for the CPU.

[PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
cpufreq-dt driver supports mode when OPP table is provided by platform code and not device tree. However on certain platforms code that fills OPP table may run after cpufreq driver tries to initialize, so let's report -EPROBE_DEFER if we do not find any entires in OPP table for the CPU.

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Viresh Kumar
On 16 December 2014 at 05:40, Dmitry Torokhov d...@chromium.org wrote: cpufreq-dt driver supports mode when OPP table is provided by platform code and not device tree. However on certain platforms code that fills OPP table may run after cpufreq driver tries to initialize, so let's report

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
On Mon, Dec 15, 2014 at 9:10 PM, Viresh Kumar viresh.ku...@linaro.org wrote: On 16 December 2014 at 05:40, Dmitry Torokhov d...@chromium.org wrote: cpufreq-dt driver supports mode when OPP table is provided by platform code and not device tree. However on certain platforms code that fills OPP

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Viresh Kumar
On 16 December 2014 at 11:02, Dmitry Torokhov d...@chromium.org wrote: Yes we will. Which simply means that this WARN is stupid. We also will hit it if there is no opp table and the allocation below fails; or if it succeeds then dev_pm_opp_init_cpufreq_table() will fail and we'll hit this code

Re: [PATCH] cpufreq-dt: defer probing if OPP table is not ready

2014-12-15 Thread Dmitry Torokhov
On Mon, Dec 15, 2014 at 9:38 PM, Viresh Kumar viresh.ku...@linaro.org wrote: On 16 December 2014 at 11:02, Dmitry Torokhov d...@chromium.org wrote: Yes we will. Which simply means that this WARN is stupid. We also will hit it if there is no opp table and the allocation below fails; or if it