From: Vipul Kumar Samar <vipulkumar.samar@st.com>
To: <grant.likely@secretlab.ca>, <spi-devel-general@lists.sourceforge.net>
Cc: <linux-arm-kernel@lists.infradead.org>, <spear-devel@list.st.com>,
<linux-kernel@vger.kernel.org>, <linus.walleij@linaro.org>,
Vipul Kumar Samar <vipulkumar.samar@st.com>
Subject: [PATCH] spi: pl022: Add clk_{un}prepare() support in runtime PM
Date: Mon, 17 Sep 2012 16:07:10 +0530 [thread overview]
Message-ID: <1f784b72399e0e96414f00866b209e2e218065af.1347877746.git.vipulkumar.samar@st.com> (raw)
clk_{un}prepare is mandatory for platforms using common clock framework. Add
clk_{un}prepare() support for spi-pl022 runtime PM.
Signed-off-by: Vipul Kumar Samar <vipulkumar.samar@st.com>
---
drivers/spi/spi-pl022.c | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/spi-pl022.c b/drivers/spi/spi-pl022.c
index f2a80ff..500e75e 100644
--- a/drivers/spi/spi-pl022.c
+++ b/drivers/spi/spi-pl022.c
@@ -2334,7 +2334,7 @@ static int pl022_runtime_suspend(struct device *dev)
{
struct pl022 *pl022 = dev_get_drvdata(dev);
- clk_disable(pl022->clk);
+ clk_disable_unprepare(pl022->clk);
return 0;
}
@@ -2342,10 +2342,13 @@ static int pl022_runtime_suspend(struct device *dev)
static int pl022_runtime_resume(struct device *dev)
{
struct pl022 *pl022 = dev_get_drvdata(dev);
+ int ret = 0;
- clk_enable(pl022->clk);
+ ret = clk_prepare_enable(pl022->clk);
+ if (ret)
+ dev_err(dev, "could not enable SSP/SPI bus clock\n");
- return 0;
+ return ret;
}
#endif
--
1.7.2.2
next reply other threads:[~2012-09-17 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 10:37 Vipul Kumar Samar [this message]
2012-09-17 10:50 ` viresh kumar
2012-09-17 12:09 ` Sergei Shtylyov
2012-09-17 13:39 ` Linus Walleij
2012-09-18 4:09 ` viresh kumar
2012-09-18 11:50 ` Linus Walleij
2012-09-19 3:31 ` viresh kumar
2012-09-20 6:43 ` Linus Walleij
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=1f784b72399e0e96414f00866b209e2e218065af.1347877746.git.vipulkumar.samar@st.com \
--to=vipulkumar.samar@st.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.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
all inboxes | Powered by JetHome®