From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Oder Chiou <oder_chiou@realtek.com>,
alsa-devel@alsa-project.org,
Nicolas Boichat <drinkcat@chromium.org>,
lgirdwood@gmail.com, john.lin@realtek.com,
Antti Palosaari <crope@iki.fi>, Bard Liao <bardliao@realtek.com>,
flove@realtek.com
Subject: Re: [PATCH] ASoC: rt5677: Avoid recursive locking in the DEADLOCK detector
Date: Fri, 5 Jun 2015 18:13:51 +0100 [thread overview]
Message-ID: <20150605171351.GZ14071@sirena.org.uk> (raw)
In-Reply-To: <55717FA7.8030005@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]
On Fri, Jun 05, 2015 at 12:53:27PM +0200, Lars-Peter Clausen wrote:
> Now the issue here is that we have nested regmap instances, meaning one
> regmap instances uses another instance in its read/write implementation.
Ah, that sounds more familiar than unlocking in different orders.
> I think Antti submitted some patches to attend to fix this, but there were
> still issues with the patches and they never got merged.
IIRC his patch was adding the ability for drivers to override the lock
class which wasn't exactly fixing the problem but rather providing a
different way to try to work around it in drivers.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-06-05 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 15:53 [PATCH] ASoC: rt5677: Avoid recursive locking in the DEADLOCK detector Oder Chiou
2015-06-03 16:44 ` Mark Brown
2015-06-05 0:53 ` Nicolas Boichat
2015-06-05 10:31 ` Mark Brown
2015-06-05 10:53 ` Lars-Peter Clausen
2015-06-05 17:13 ` Mark Brown [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=20150605171351.GZ14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=crope@iki.fi \
--cc=drinkcat@chromium.org \
--cc=flove@realtek.com \
--cc=john.lin@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.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