From: Sekhar Nori <nsekhar@ti.com>
To: Sekhar Nori <nsekhar@ti.com>
Cc: <dwmw2@infradead.org>, <artem.bityutskiy@linux.intel.com>,
<davinci-linux-open-source@linux.davincidsp.com>,
<mikedunn@newsguy.com>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <hs@denx.de>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] mtd:nand:clk: preparation for switch to common clock framework
Date: Tue, 9 Oct 2012 18:39:19 +0530 [thread overview]
Message-ID: <507421FF.2090309@ti.com> (raw)
In-Reply-To: <507420A4.8090905@ti.com>
On 10/9/2012 6:33 PM, Sekhar Nori wrote:
> On 9/17/2012 10:07 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>
>> Reviewed-by: Mike Turquette <mturquette@linaro.org>
>
> Tested this using NAND flash on DA850 EVM.
>
> Acked-by: Sekhar Nori <nsekhar@ti.com>
>
> Any chance this can make into the v3.7 kernel?
Just noticed another thread where Artem replied saying this patch is
pushed. Sorry about the noise.
Thanks,
Sekhar
prev parent reply other threads:[~2012-10-09 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347899860-24358-1-git-send-email-m-karicheri2@ti.com>
[not found] ` <1347899860-24358-2-git-send-email-m-karicheri2@ti.com>
2012-09-28 16:10 ` [REMINDER: PATCH 1/1] mtd:nand:clk: preparation for switch to common clock framework Karicheri, Muralidharan
2012-10-11 9:57 ` Artem Bityutskiy
2012-10-11 10:07 ` Sekhar Nori
2012-10-11 10:09 ` Artem Bityutskiy
2012-10-09 13:03 ` [PATCH " Sekhar Nori
2012-10-09 13:09 ` Sekhar Nori [this message]
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=507421FF.2090309@ti.com \
--to=nsekhar@ti.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=hs@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mikedunn@newsguy.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