On 10:17-20130312, J, KEERTHY wrote:
> > OK. My intent is to remove omap-cpufreq.c. So, I guess I could do
> > something like the following (not tested yet), but would that be the
> > right approach?
>
> Similar attempt was done for am33xx_clks in this by Shawn:
>
>
Guo; linux-
> ker...@vger.kernel.org; linux...@vger.kernel.org; linux-
> o...@vger.kernel.org
> Subject: Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which
> are not in DT yet.
>
> On 15:24-20130312, Benoit Cousson wrote:
> > Hi Guys,
> >
>
On 15:24-20130312, Benoit Cousson wrote:
> Hi Guys,
>
> On 03/12/2013 06:03 AM, Santosh Shilimkar wrote:
> > On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
> >> On certain SoCs like variants of OMAP, the clock conversion to DT
> >> is not complete. In short, the ability to:
> >> cpus {
Hi Guys,
On 03/12/2013 06:03 AM, Santosh Shilimkar wrote:
> On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
>> On certain SoCs like variants of OMAP, the clock conversion to DT
>> is not complete. In short, the ability to:
>> cpus {
>> cpu@0 {
>> clocks = < 0>;
>> };
>> };
On Mon, Mar 11, 2013 at 06:05:29PM -0500, Nishanth Menon wrote:
> On certain SoCs like variants of OMAP, the clock conversion to DT
> is not complete. In short, the ability to:
> cpus {
> cpu@0 {
> clocks = < 0>;
> };
> };
> is not possible. However, the clock node is registered.
>
On Mon, Mar 11, 2013 at 06:05:29PM -0500, Nishanth Menon wrote:
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = cpuclk 0;
};
};
is not possible. However, the clock node is registered.
Allow
Hi Guys,
On 03/12/2013 06:03 AM, Santosh Shilimkar wrote:
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = cpuclk 0;
};
};
is not
On 15:24-20130312, Benoit Cousson wrote:
Hi Guys,
On 03/12/2013 06:03 AM, Santosh Shilimkar wrote:
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
...@vger.kernel.org; linux...@vger.kernel.org; linux-
o...@vger.kernel.org
Subject: Re: [PATCH 1/2] cpufreq: cpufreq-cpu0: support for clock which
are not in DT yet.
On 15:24-20130312, Benoit Cousson wrote:
Hi Guys,
On 03/12/2013 06:03 AM, Santosh Shilimkar wrote:
On Tuesday 12 March 2013 04
On 10:17-20130312, J, KEERTHY wrote:
OK. My intent is to remove omap-cpufreq.c. So, I guess I could do
something like the following (not tested yet), but would that be the
right approach?
Similar attempt was done for am33xx_clks in this by Shawn:
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
> On certain SoCs like variants of OMAP, the clock conversion to DT
> is not complete. In short, the ability to:
> cpus {
> cpu@0 {
> clocks = < 0>;
> };
> };
> is not possible. However, the clock node is registered.
> Allow
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = < 0>;
};
};
is not possible. However, the clock node is registered.
Allow for clk names to be provided as string so as to be used when needed.
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = cpuclk 0;
};
};
is not possible. However, the clock node is registered.
Allow for clk names to be provided as string so as to be used when needed.
On Tuesday 12 March 2013 04:35 AM, Nishanth Menon wrote:
On certain SoCs like variants of OMAP, the clock conversion to DT
is not complete. In short, the ability to:
cpus {
cpu@0 {
clocks = cpuclk 0;
};
};
is not possible. However, the clock node is registered.
Allow for
14 matches
Mail list logo
