Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2016-02-26 Thread Scott Wood
On Fri, 2016-02-26 at 15:01 -0600, Li Yang wrote: > On Fri, Feb 26, 2016 at 12:16 PM, Scott Wood wrote: > > On Fri, 2016-02-26 at 12:14 -0600, Li Yang wrote: > > > On Fri, Sep 25, 2015 at 4:50 PM, Rafael J. Wysocki > > > wrote: > > > > On Friday, September

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2016-02-26 Thread Li Yang
On Fri, Feb 26, 2016 at 12:16 PM, Scott Wood wrote: > On Fri, 2016-02-26 at 12:14 -0600, Li Yang wrote: >> On Fri, Sep 25, 2015 at 4:50 PM, Rafael J. Wysocki >> wrote: >> > On Friday, September 25, 2015 04:17:07 PM Scott Wood wrote: >> > > On Fri,

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2016-02-26 Thread Scott Wood
On Fri, 2016-02-26 at 12:14 -0600, Li Yang wrote: > On Fri, Sep 25, 2015 at 4:50 PM, Rafael J. Wysocki > wrote: > > On Friday, September 25, 2015 04:17:07 PM Scott Wood wrote: > > > On Fri, 2015-09-25 at 23:42 +0200, Rafael J. Wysocki wrote: > > > > On Tuesday, September 22,

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2016-02-26 Thread Li Yang
On Fri, Sep 25, 2015 at 4:50 PM, Rafael J. Wysocki wrote: > On Friday, September 25, 2015 04:17:07 PM Scott Wood wrote: >> On Fri, 2015-09-25 at 23:42 +0200, Rafael J. Wysocki wrote: >> > On Tuesday, September 22, 2015 12:46:54 PM Viresh Kumar wrote: >> > > On 19-09-15, 23:29,

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2015-09-25 Thread Scott Wood
On Fri, 2015-09-25 at 23:42 +0200, Rafael J. Wysocki wrote: > On Tuesday, September 22, 2015 12:46:54 PM Viresh Kumar wrote: > > On 19-09-15, 23:29, Scott Wood wrote: > > > Get the CPU clock's potential parent clocks from the clock interface > > > itself, rather than manually parsing the clocks

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2015-09-25 Thread Rafael J. Wysocki
On Tuesday, September 22, 2015 12:46:54 PM Viresh Kumar wrote: > On 19-09-15, 23:29, Scott Wood wrote: > > Get the CPU clock's potential parent clocks from the clock interface > > itself, rather than manually parsing the clocks property to find a > > phandle, looking at the clock-names property of

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2015-09-25 Thread Rafael J. Wysocki
On Friday, September 25, 2015 04:17:07 PM Scott Wood wrote: > On Fri, 2015-09-25 at 23:42 +0200, Rafael J. Wysocki wrote: > > On Tuesday, September 22, 2015 12:46:54 PM Viresh Kumar wrote: > > > On 19-09-15, 23:29, Scott Wood wrote: > > > > Get the CPU clock's potential parent clocks from the

Re: [PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2015-09-22 Thread Viresh Kumar
On 19-09-15, 23:29, Scott Wood wrote: > Get the CPU clock's potential parent clocks from the clock interface > itself, rather than manually parsing the clocks property to find a > phandle, looking at the clock-names property of that, and assuming that > those are valid parent clocks for the cpu

[PATCH v3 5/5] cpufreq: qoriq: Don't look at clock implementation details

2015-09-19 Thread Scott Wood
Get the CPU clock's potential parent clocks from the clock interface itself, rather than manually parsing the clocks property to find a phandle, looking at the clock-names property of that, and assuming that those are valid parent clocks for the cpu clock. This is necessary now that the clocks