From: Sekhar Nori <nsekhar@ti.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: <spi-devel-general@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>,
<davinci-linux-open-source@linux.davincidsp.com>,
<grant.likely@secretlab.ca>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/1] spi:clk: preparation for switch to common clock framework
Date: Tue, 9 Oct 2012 17:07:17 +0530 [thread overview]
Message-ID: <50740C6D.7070906@ti.com> (raw)
In-Reply-To: <1347900122-25101-2-git-send-email-m-karicheri2@ti.com>
On 9/17/2012 10:12 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>
This patch had to be applied manually and with some fuzz when I applied
it to latest linus/master. There were no conflicts though and once I
applied it, I was able to test SPI flash on DA850 EVM successfully using it.
Acked-by: Sekhar Nori <nsekhar@ti.com>
I am hoping this patch can still go in v3.7. I realize we are in the
middle of the merge window though.
Thanks,
Sekhar
prev parent reply other threads:[~2012-10-09 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1347900122-25101-1-git-send-email-m-karicheri2@ti.com>
[not found] ` <1347900122-25101-2-git-send-email-m-karicheri2@ti.com>
2012-09-28 16:11 ` [REMINDER: PATCH 1/1] spi:clk: preparation for switch to common clock framework Karicheri, Muralidharan
2012-10-09 11:37 ` 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=50740C6D.7070906@ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=spi-devel-general@lists.sourceforge.net \
/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