From: Lee Jones <lee.jones@linaro.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v2] mfd: arizona: Fix lockdep recursion warning on set_irq_wake
Date: Mon, 11 Apr 2016 09:18:45 +0100 [thread overview]
Message-ID: <20160411081845.GE4592@x1> (raw)
In-Reply-To: <1458916029-6540-1-git-send-email-ckeepax@opensource.wolfsonmicro.com>
On Fri, 25 Mar 2016, Charles Keepax wrote:
> Avoid a false recursive locking warning from lockdep by adding a lock
> class for the arizona IRQ chip.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> ---
> drivers/mfd/arizona-irq.c | 3 +++
> 1 file changed, 3 insertions(+)
Applied, thanks.
> Thanks for the pointers guys and sorry again for missing this the
> first time around.
>
> Changes since v1:
> - Ditch the bus_lock stuff and use irq_set_lockdep_class
>
> Thanks,
> Charles
>
> diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
> index 5fef014..edeb495 100644
> --- a/drivers/mfd/arizona-irq.c
> +++ b/drivers/mfd/arizona-irq.c
> @@ -168,12 +168,15 @@ static struct irq_chip arizona_irq_chip = {
> .irq_set_wake = arizona_irq_set_wake,
> };
>
> +static struct lock_class_key arizona_irq_lock_class;
> +
> static int arizona_irq_map(struct irq_domain *h, unsigned int virq,
> irq_hw_number_t hw)
> {
> struct arizona *data = h->host_data;
>
> irq_set_chip_data(virq, data);
> + irq_set_lockdep_class(virq, &arizona_irq_lock_class);
> irq_set_chip_and_handler(virq, &arizona_irq_chip, handle_simple_irq);
> irq_set_nested_thread(virq, 1);
> irq_set_noprobe(virq);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2016-04-11 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 14:27 [PATCH v2] mfd: arizona: Fix lockdep recursion warning on set_irq_wake Charles Keepax
2016-03-29 8:27 ` Thomas Gleixner
2016-04-11 8:18 ` Lee Jones [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=20160411081845.GE4592@x1 \
--to=lee.jones@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=tglx@linutronix.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