From: Ben Dooks <ben@trinity.fluff.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@lists.codethink.co.uk, alsa-devel@alsa-project.org,
kuninori.morimoto.gx@renesas.com, linux-sh@vger.kernel.org,
lgirdwood@gmail.com, Ben Dooks <ben.dooks@codethink.co.uk>,
magnus.damm@opensource.se,
William Towle <william.towle@codethink.co.uk>
Subject: Re: [PATCH] ASoC: rsnd: SSI needs to prepare clocks before enabling
Date: Fri, 4 Apr 2014 12:42:50 +0100 [thread overview]
Message-ID: <20140404114250.GS4400@trinity.fluff.org> (raw)
In-Reply-To: <20140329100906.GE21628@sirena.org.uk>
On Sat, Mar 29, 2014 at 10:09:06AM +0000, Mark Brown wrote:
> On Fri, Mar 28, 2014 at 12:27:06PM +0000, Ben Dooks wrote:
> > From: William Towle <william.towle@codethink.co.uk>
> >
> > The rsnd_ssi_hw_{stop|start} functions need to call clk_prepare_enable()
> > and clk_disable_unprepare(), otherwise the following warning occurs on
> > attempt to play sound:
>
> This doesn't apply cleanly against current code, can you please check and
> resend - I can't apply this anyway since...
>
> > Signed-off-by: William Towle <william.towle@codethink.co.uk>
> > [ben.dooks@codethink.co.uk: add more bug info to report]
> > Tested-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > ---
>
> ...you forgot to sign off. I'm also not seeing the debug info you
> mention in the changelog, indeed there's no error checking.
Ooops.
I need to re-do this anyway as we need to prepare the clock separately
from the enable, as the enable code is occasionally being called from
an interrupt context.
I anm not sure what you mean by debug info... there is the log from
the WARN_ON() which is trigger from the clock driver.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
WARNING: multiple messages have this Message-ID (diff)
From: Ben Dooks <ben@trinity.fluff.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@lists.codethink.co.uk, alsa-devel@alsa-project.org,
kuninori.morimoto.gx@renesas.com, linux-sh@vger.kernel.org,
lgirdwood@gmail.com, Ben Dooks <ben.dooks@codethink.co.uk>,
magnus.damm@opensource.se,
William Towle <william.towle@codethink.co.uk>
Subject: Re: [alsa-devel] [PATCH] ASoC: rsnd: SSI needs to prepare clocks before enabling
Date: Fri, 04 Apr 2014 11:42:50 +0000 [thread overview]
Message-ID: <20140404114250.GS4400@trinity.fluff.org> (raw)
In-Reply-To: <20140329100906.GE21628@sirena.org.uk>
On Sat, Mar 29, 2014 at 10:09:06AM +0000, Mark Brown wrote:
> On Fri, Mar 28, 2014 at 12:27:06PM +0000, Ben Dooks wrote:
> > From: William Towle <william.towle@codethink.co.uk>
> >
> > The rsnd_ssi_hw_{stop|start} functions need to call clk_prepare_enable()
> > and clk_disable_unprepare(), otherwise the following warning occurs on
> > attempt to play sound:
>
> This doesn't apply cleanly against current code, can you please check and
> resend - I can't apply this anyway since...
>
> > Signed-off-by: William Towle <william.towle@codethink.co.uk>
> > [ben.dooks@codethink.co.uk: add more bug info to report]
> > Tested-by: Ben Dooks <ben.dooks@codethink.co.uk>
> > ---
>
> ...you forgot to sign off. I'm also not seeing the debug info you
> mention in the changelog, indeed there's no error checking.
Ooops.
I need to re-do this anyway as we need to prepare the clock separately
from the enable, as the enable code is occasionally being called from
an interrupt context.
I anm not sure what you mean by debug info... there is the log from
the WARN_ON() which is trigger from the clock driver.
--
Ben Dooks, ben@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
next prev parent reply other threads:[~2014-04-04 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 12:27 [PATCH] ASoC: rsnd: SSI needs to prepare clocks before enabling Ben Dooks
2014-03-28 12:27 ` Ben Dooks
2014-03-29 10:09 ` Mark Brown
2014-04-04 11:42 ` Ben Dooks [this message]
2014-04-04 11:42 ` [alsa-devel] " 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=20140404114250.GS4400@trinity.fluff.org \
--to=ben@trinity.fluff.org \
--cc=alsa-devel@alsa-project.org \
--cc=ben.dooks@codethink.co.uk \
--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 \
--cc=william.towle@codethink.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.