From: Ben Dooks <ben.dooks@codethink.co.uk>
To: alsa-devel@alsa-project.org
Cc: kuninori.morimoto.gx@renesas.com, broonie@kernel.org,
lgirdwood@gmail.com, linux-sh@vger.kernel.org,
magnus.damm@opensource.se, linux-kernel@lists.codethink.co.uk,
Ben Dooks <ben.dooks@codethink.co.uk>
Subject: [PATCH] ASoC: rsnd: fix src clock prepare/unprepare
Date: Fri, 28 Mar 2014 15:03:17 +0000 [thread overview]
Message-ID: <1396018997-12390-1-git-send-email-ben.dooks@codethink.co.uk> (raw)
As with the previous commit, before a clock can be used it must be prepared
for use. Change from clk_enable() and clk_disable() to the versions of the
calls which also prepare and un-prepare the clocks.
Will fix warnings from the clock code when this is used.
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
---
sound/soc/sh/rcar/scu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sound/soc/sh/rcar/scu.c b/sound/soc/sh/rcar/scu.c
index 9153a11..3b1d1d2 100644
--- a/sound/soc/sh/rcar/scu.c
+++ b/sound/soc/sh/rcar/scu.c
@@ -284,7 +284,7 @@ static int rsnd_scu_start(struct rsnd_mod *mod,
return 0;
}
- clk_enable(scu->clk);
+ clk_prepare_enable(scu->clk);
/* it use DMA transter */
@@ -317,7 +317,7 @@ static int rsnd_scu_stop(struct rsnd_mod *mod,
rsnd_scu_transfer_stop(priv, mod, rdai, io);
- clk_disable(scu->clk);
+ clk_disable_unprepare(scu->clk);
return 0;
}
--
1.9.0
next reply other threads:[~2014-03-28 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 15:03 Ben Dooks [this message]
2014-03-29 10:10 ` [PATCH] ASoC: rsnd: fix src clock prepare/unprepare Mark Brown
2014-03-30 13:36 ` Ben Dooks
2014-03-30 22:24 ` Mark Brown
2014-03-31 10:05 ` Ben Dooks
2014-03-31 10:18 ` Mark Brown
2014-03-31 10:30 ` Ben Dooks
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=1396018997-12390-1-git-send-email-ben.dooks@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@opensource.se \
/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).