On Sun, 25 Jan 2015 19:31:14 +0530
Viresh Kumar wrote:
> On 23 January 2015 at 19:27, Lukasz Majewski
> wrote:
> > Please pay a note about following problem:
> >
> > Previously we got: cpu0: cpu@0 for all Exynos devices.
> >
> > Now, however, cpu numbering has changed (due to GIC rework).
> > Fo
On Sun, 25 Jan 2015 12:46:21 -0400
Eduardo Valentin wrote:
> On Sun, Jan 25, 2015 at 07:31:14PM +0530, Viresh Kumar wrote:
> > On 23 January 2015 at 19:27, Lukasz Majewski
> > wrote:
> > > Please pay a note about following problem:
> > >
> > > Previously we got: cpu0: cpu@0 for all Exynos device
On Sun, Jan 25, 2015 at 07:31:14PM +0530, Viresh Kumar wrote:
> On 23 January 2015 at 19:27, Lukasz Majewski wrote:
> > Please pay a note about following problem:
> >
> > Previously we got: cpu0: cpu@0 for all Exynos devices.
> >
> > Now, however, cpu numbering has changed (due to GIC rework).
> >
On 23 January 2015 at 19:27, Lukasz Majewski wrote:
> Please pay a note about following problem:
>
> Previously we got: cpu0: cpu@0 for all Exynos devices.
>
> Now, however, cpu numbering has changed (due to GIC rework).
> For example:
>
> Exynos4412:
> cpus {
> cpu0: cpu@A
Hi Viresh,
> On 23 January 2015 at 17:44, Lukasz Majewski
> wrote:
> > + cpus = of_find_node_by_path("/cpus");
> > + if (!cpus) {
> > + pr_err("failed to find cpus node\n");
> > + return 0;
> > + }
> > +
> > + np = of_get_next_child(cpus, NULL);
On 23 January 2015 at 17:44, Lukasz Majewski wrote:
> + cpus = of_find_node_by_path("/cpus");
> + if (!cpus) {
> + pr_err("failed to find cpus node\n");
> + return 0;
> + }
> +
> + np = of_get_next_child(cpus, NULL);
> + if (!np) {
> +
With thermal subsystem rework it is necessary to tune current cpufreq code
to use cpu frequency change as a potential cooling device.
Now the cpu cooling device is registered only when proper nodes and properties
are available in device tree. Lack of them, however, will not prevent
cpufreq for nor
