From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Bo Shen <voice.shen@atmel.com>, Arnd Bergmann <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Mark Brown <broonie@kernel.org>,
<boris.brezillon@free-electrons.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH] misc: atmel-ssc: prepare clock only when request
Date: Wed, 24 Sep 2014 17:59:32 +0200 [thread overview]
Message-ID: <5422EA64.1070907@atmel.com> (raw)
In-Reply-To: <1411551235-16502-1-git-send-email-voice.shen@atmel.com>
On 24/09/2014 11:33, Bo Shen :
> Prepare SSC clock only when request SSC channel, the clock will be
> enabled when initialize the SSC.
>
> Signed-off-by: Bo Shen <voice.shen@atmel.com>
okay: it is the driver that uses the ssc that would enable the clock as
it is done in sound/soc/atmel/atmel_ssc_dai.c
Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Bye,
> ---
> Send this patch to driver/misc maintainer as Mark Brown suggested.
>
> drivers/misc/atmel-ssc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/atmel-ssc.c b/drivers/misc/atmel-ssc.c
> index 60843a2..f9807a7 100644
> --- a/drivers/misc/atmel-ssc.c
> +++ b/drivers/misc/atmel-ssc.c
> @@ -57,7 +57,7 @@ struct ssc_device *ssc_request(unsigned int ssc_num)
> ssc->user++;
> spin_unlock(&user_lock);
>
> - clk_prepare_enable(ssc->clk);
> + clk_prepare(ssc->clk);
>
> return ssc;
> }
> @@ -77,7 +77,7 @@ void ssc_free(struct ssc_device *ssc)
> spin_unlock(&user_lock);
>
> if (disable_clk)
> - clk_disable_unprepare(ssc->clk);
> + clk_unprepare(ssc->clk);
> }
> EXPORT_SYMBOL(ssc_free);
>
>
--
Nicolas Ferre
prev parent reply other threads:[~2014-09-24 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:33 [RESEND PATCH] misc: atmel-ssc: prepare clock only when request Bo Shen
2014-09-24 15:59 ` Nicolas Ferre [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=5422EA64.1070907@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=arnd@arndb.de \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=voice.shen@atmel.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