From: Sekhar Nori <nsekhar-l0cyMroinI0@public.gmane.org>
To: Murali Karicheri <m-karicheri2-l0cyMroinI0@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.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-l0cyMroinI0@public.gmane.org>
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-l0cyMroinI0@public.gmane.org>
> Reviewed-by: Mike Turquette <mturquette-QSEj5FYQhm4dnm+yROfE0A@public.gmane.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-l0cyMroinI0@public.gmane.org>
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
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
next prev parent reply other threads:[~2012-10-09 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 16:42 [PATCH 0/1] spi:clk: preparation for switch to common clock framework Murali Karicheri
[not found] ` <1347900122-25101-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2012-09-17 16:42 ` [PATCH 1/1] " Murali Karicheri
[not found] ` <1347900122-25101-2-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2012-09-28 16:11 ` [REMINDER: PATCH " Karicheri, Muralidharan
2012-10-09 11:37 ` Sekhar Nori [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-12 20:23 [PATCH 0/1] " Murali Karicheri
[not found] ` <1347481435-6654-1-git-send-email-m-karicheri2-l0cyMroinI0@public.gmane.org>
2012-09-12 20:23 ` [PATCH 1/1] " Murali Karicheri
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-l0cymroini0@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=m-karicheri2-l0cyMroinI0@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 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).