linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org, Vishwanath Sripathy <vishwanath.bs@ti.com>
Subject: RE: [PATCH 1/3] omap2plus: clock: Add an alias cpu_ck to be used in common cpufreq driver
Date: Mon, 14 Mar 2011 14:49:15 +0530	[thread overview]
Message-ID: <ddb27b28063c84f3b2366012e6b9b3ed@mail.gmail.com> (raw)
In-Reply-To: <87zkp2hbee.fsf@ti.com>

> -----Original Message-----
> From: Kevin Hilman [mailto:khilman@ti.com]
> Sent: Friday, March 11, 2011 3:43 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; vishwanath.bs@ti.com
> Subject: Re: [PATCH 1/3] omap2plus: clock: Add an alias cpu_ck to be
> used in common cpufreq driver
>
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:
>
> > Add an alias clock node for cpu clock control on all OMAP2PLUS
> devices.
> > The intention is avoid cpu_is_xxxx() checks in the common cpufreq
> driver.
> >
> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> Rather than having hard-coded clkdev nodes, Since CPUfreq will be
> the
> only user of these clocks, it might make sense to just use cpu_is_*
> in the CPUfreq init and do clk_add_alias().
>

Since we are ok to have cpu_is_*() in CPUfreq init, we don't even
need to clk_add_alias().

We just the correct clock node handle based on SOC.

Regards,
Santosh

  reply	other threads:[~2011-03-14  9:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25  6:10 [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Santosh Shilimkar
2011-02-25  6:10 ` [PATCH 1/3] omap2plus: clock: Add an alias cpu_ck to be used in common cpufreq driver Santosh Shilimkar
2011-03-10 22:13   ` Kevin Hilman
2011-03-14  9:19     ` Santosh Shilimkar [this message]
2011-02-25  6:10 ` [PATCH 2/3] omap: cpufreq: Split omap1 and omap2plus cpufreq drivers Santosh Shilimkar
2011-02-25  7:17   ` Vishwanath Sripathy
2011-02-25  7:22     ` Santosh Shilimkar
2011-02-25  8:19   ` DebBarma, Tarun Kanti
2011-02-25  6:10 ` [PATCH 3/3] omap2plus: cpufreq: Add SMP support to cater OMAP4430 Santosh Shilimkar
2011-02-25  8:10   ` DebBarma, Tarun Kanti
2011-03-10 22:27   ` Kevin Hilman
2011-03-10 22:28 ` [PATCH 0/3] [pm-wip/cpufreq] cpufreq cleanup and SMP support Kevin Hilman
2011-03-11  5:54   ` Santosh Shilimkar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ddb27b28063c84f3b2366012e6b9b3ed@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=vishwanath.bs@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).