From: Lars-Peter Clausen <lars@metafoo.de>
To: Nicolas Boichat <drinkcat@chromium.org>, Mark Brown <broonie@kernel.org>
Cc: Oder Chiou <oder_chiou@realtek.com>,
alsa-devel@alsa-project.org,
Anatol Pomozov <anatol.pomozov@gmail.com>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Takashi Iwai <tiwai@suse.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Antti Palosaari <crope@iki.fi>, Bard Liao <bardliao@realtek.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [alsa-devel] [RFC PATCH 1/2] regmap: add configurable lock class key for lockdep
Date: Tue, 30 Jun 2015 13:02:10 +0200 [thread overview]
Message-ID: <55927732.4060207@metafoo.de> (raw)
In-Reply-To: <20150630045655.GA38694@google.com>
On 06/30/2015 06:56 AM, Nicolas Boichat wrote:
> On Mon, Jun 29, 2015 at 04:34:11PM +0100, Mark Brown wrote:
>> On Mon, Jun 29, 2015 at 04:18:11PM +0200, Lars-Peter Clausen wrote:
>>> Leaves us pretty much with only two options. Either add a lock key pointer
>>> to regmap_config which needs to be manually initialized. Or wrap all
>>> regmap_init() variants to create a static lock key. I'd slightly prefer the
>>> later. We can avoid most of the boiler-plate code by using some helper
>>> macros to generate the wrappers.
>>
>> It's better to keep the bodges in the core, yes.
>
> Partial attempt below. Of course all other _init functions will need to be
> converted as well. I'd like to get feedback before I do the rest of the work.
Looks good to me.
> The macro part is quite repetitive and I don't think it can be simplified.
How about something like
#ifdef CONFIG_LOCKDEP
#define regmap_lockdep_wrapper(fn, ...) \
( \
({ \
static struct lock_class_key _key; \
fn(__VA_ARGS__, &_key, \
KBUILD_BASENAME ":" \
__stringify(__LINE__) ":" \
"(" #config ")->_lock"); \
}) \
)
#else
#define regmap_lockdep_wrapper(fn, ...) fn(__VA_ARGS__, NULL, NULL)
#endif
#define regmap_init_i2c(i2c, config) \
regmap_lockdep_wrapper(__regmap_init_i2c, i2c, config)
...
next prev parent reply other threads:[~2015-06-30 11:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 9:35 [RFC PATCH 1/2] regmap: add configurable lock class key for lockdep Nicolas Boichat
2015-06-25 9:35 ` [RFC PATCH 2/2] ASoC: rt5677: Add lockdep class to silence lockdep warnings Nicolas Boichat
2015-06-25 13:21 ` [RFC PATCH 1/2] regmap: add configurable lock class key for lockdep Arjan van de Ven
2015-06-25 14:29 ` Mark Brown
2015-06-25 15:03 ` Lars-Peter Clausen
2015-06-25 15:33 ` Mark Brown
2015-06-25 15:47 ` Lars-Peter Clausen
2015-06-25 16:08 ` Mark Brown
2015-06-26 3:16 ` Nicolas Boichat
2015-06-29 12:51 ` Nicolas Boichat
2015-06-29 12:59 ` Lars-Peter Clausen
2015-06-29 14:03 ` Nicolas Boichat
2015-06-29 14:18 ` Lars-Peter Clausen
2015-06-29 15:34 ` Mark Brown
2015-06-30 4:56 ` Nicolas Boichat
2015-06-30 11:02 ` Lars-Peter Clausen [this message]
2015-06-29 14:22 ` Mark Brown
2015-06-29 14:35 ` Arjan van de Ven
2015-06-29 15:32 ` Mark Brown
2015-06-29 15:36 ` Arjan van de Ven
2015-06-29 16:02 ` Mark Brown
2015-06-29 14:19 ` Mark Brown
2015-06-25 14:49 ` Mark Brown
2015-06-25 15:59 ` Lars-Peter Clausen
2015-06-26 2:34 ` Nicolas Boichat
2015-06-26 8:31 ` Lars-Peter Clausen
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=55927732.4060207@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=arjan@linux.intel.com \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=crope@iki.fi \
--cc=drinkcat@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=mingo@redhat.com \
--cc=oder_chiou@realtek.com \
--cc=tiwai@suse.de \
/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