From: Krzysztof Kozlowski <krzk@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, sbkim73@samsung.com,
patches@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
krzk@kernel.org, broonie@kernel.org, s.nawrocki@samsung.com
Subject: Re: [PATCH] ASoC: samsung: i2s: Fixup last IRQ unsafe spin lock call
Date: Fri, 21 Oct 2016 16:31:29 +0300 [thread overview]
Message-ID: <20161021133129.GA3289@kozik-lap> (raw)
In-Reply-To: <1477055928-11712-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Fri, Oct 21, 2016 at 02:18:48PM +0100, Charles Keepax wrote:
> Unfortunately, I seem to have missed a case where an IRQ safe spinlock was
> required, in samsung_i2s_dai_remove, when I fixed up the other calls in
> this patch:
>
> 316fa9e09ad7 ("ASoC: samsung: Use IRQ safe spin lock calls")
>
> This causes a lockdep warning when unbinding and rebinding the audio card:
>
> [ 104.357664] CPU0 CPU1
> [ 104.362174] ---- ----
> [ 104.366692] lock(&(&pri_dai->spinlock)->rlock);
> [ 104.371372] local_irq_disable();
> [ 104.377283] lock(&(&substream->self_group.lock)->rlock);
> [ 104.385259] lock(&(&pri_dai->spinlock)->rlock);
> [ 104.392469] <Interrupt>
> [ 104.395072] lock(&(&substream->self_group.lock)->rlock);
> [ 104.400710]
> [ 104.400710] *** DEADLOCK ***
>
> Fixes: ce8bcdbb61d9 ("ASoC: samsung: i2s: Protect more registers with a spinlock")
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> sound/soc/samsung/i2s.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-10-21 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161021131846eucas1p27e73aba30a83a17e121c571259cbc7c3@eucas1p2.samsung.com>
2016-10-21 13:18 ` [PATCH] ASoC: samsung: i2s: Fixup last IRQ unsafe spin lock call Charles Keepax
2016-10-21 13:31 ` Krzysztof Kozlowski [this message]
2016-10-21 14:20 ` Sylwester Nawrocki
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=20161021133129.GA3289@kozik-lap \
--to=krzk@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=s.nawrocki@samsung.com \
--cc=sbkim73@samsung.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 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.