From: Mark Brown <broonie@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] regulator: Fix recursive mutex lockdep warning
Date: Fri, 7 Aug 2015 15:12:58 +0100 [thread overview]
Message-ID: <20150807141258.GH10301@sirena.org.uk> (raw)
In-Reply-To: <55C349C2.1020009@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On Thu, Aug 06, 2015 at 12:49:22PM +0100, Srinivas Kandagatla wrote:
> On 06/08/15 12:40, Mark Brown wrote:
> >>lock_class per regulator makes more sense, I will try to cookup an RFC
> >>patch.
> >There's an issue there with all lock classes needing to be statically
> >allocated which makes things a bit tricky.
> Yes, just realized it with "BUG: key edadc07c not in .data!"
Yeah, it's a bit nasty. We went round this a bit with regmap and
unfortunately didn't manage to come up with any great ideas. The regmap
workaround just landed in my tree, I'm not sure it's really great for
regulator though.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-08-07 14:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 16:02 Srinivas Kandagatla
2015-08-06 1:39 ` Krzysztof Kozlowski
2015-08-06 7:29 ` Srinivas Kandagatla
2015-08-06 7:35 ` Krzysztof Kozlowski
2015-08-06 7:53 ` Krzysztof Kozlowski
2015-08-06 9:43 ` Mark Brown
2015-08-06 11:01 ` Srinivas Kandagatla
2015-08-06 11:40 ` Mark Brown
2015-08-06 11:49 ` Srinivas Kandagatla
2015-08-07 14:12 ` 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=20150807141258.GH10301@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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
all inboxes | Powered by JetHome®