All of lore.kernel.org
 help / color / mirror / Atom feed
From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm:davinci: clk - migrate to new common clock API
Date: Tue, 14 Aug 2012 12:00:17 +0530	[thread overview]
Message-ID: <5029F079.8010901@ti.com> (raw)
In-Reply-To: <1343926428-5210-1-git-send-email-m-karicheri2@ti.com>


Hi Murali,

On 8/2/2012 10:23 PM, Murali Karicheri wrote:
> As a first step towards migrating davinci platforms to use common clock
> framework, replace all instances of clk_enable() with clk_prepare_enable()
> and clk_disable() with clk_disable_unprepare(). Until the platform is
> switched to use the CONFIG_HAVE_CLK_PREPARE Kconfig variable, this just
> adds a might_sleep() call and would work without any issues.
> 
> This will make it easy later to switch to common clk based implementation
> of clk driver from DaVinci specific driver.
> 
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>

Queuing this patch for v3.7. The subject line should have ARM in
capitals for consistency. Also, you are not really migrating to new API
in this patch - just preparing for migration so I prefer:

"ARM: davinci: convert platform code to use clk_prepare/clk_unprepare"

I will make this change while committing.

Thanks,
Sekhar

  parent reply	other threads:[~2012-08-14  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1343926428-5210-1-git-send-email-m-karicheri2@ti.com>
2012-08-02 21:20 ` [PATCH] arm:davinci: clk - migrate to new common clock API Mike Turquette
2012-08-13 21:13   ` [linux-keystone] " Karicheri, Muralidharan
2012-08-13 21:44     ` Turquette, Mike
2012-08-02 21:28 ` Mike Turquette
2012-08-13 21:15   ` Karicheri, Muralidharan
2012-08-14  6:30 ` Sekhar Nori [this message]
2012-08-30 16:17   ` Karicheri, Muralidharan

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=5029F079.8010901@ti.com \
    --to=nsekhar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.