From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: <lee.jones@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <patches@opensource.wolfsonmicro.com>
Subject: [PATCH RESEND] mfd: arizona: Fix lockdep recursion warning on set_irq_wake
Date: Thu, 10 Mar 2016 10:16:49 +0000 [thread overview]
Message-ID: <1457605009-7792-1-git-send-email-ckeepax@opensource.wolfsonmicro.com> (raw)
Lockdep explicitly sets all the irq_desc locks as a single lock-class,
which causes a "possible recursive locking detected" warning when we
attempt to propagate the IRQ wake to our parent IRQ in
arizona_irq_set_wake. Although this appears to be a false positive
because an IRQ is unlikely to be its own parent, this was clearly
intentionally prohibited.
To avoid this lockdep warning, take a cue from the regmap-irq system,
and add bus lock callbacks on the IRQ chip and propagate the wake in
the bus unlock which will happen after the desc lock has been released
and thus avoid the issue.
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
---
drivers/mfd/arizona-irq.c | 35 ++++++++++++++++++++++++++++++++++-
include/linux/mfd/arizona/core.h | 3 +++
2 files changed, 37 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c
index 5fef014..6497a65 100644
--- a/drivers/mfd/arizona-irq.c
+++ b/drivers/mfd/arizona-irq.c
@@ -154,17 +154,48 @@ static void arizona_irq_disable(struct irq_data *data)
{
}
+static void arizona_irq_lock(struct irq_data *data)
+{
+ struct arizona *arizona = irq_data_get_irq_chip_data(data);
+
+ mutex_lock(&arizona->irq_lock);
+}
+
+static void arizona_irq_sync_unlock(struct irq_data *data)
+{
+ struct arizona *arizona = irq_data_get_irq_chip_data(data);
+ int i;
+
+ if (arizona->pending_wake_count < 0)
+ for (i = arizona->pending_wake_count; i < 0; i++)
+ irq_set_irq_wake(arizona->irq, 0);
+ else if (arizona->pending_wake_count > 0)
+ for (i = 0; i < arizona->pending_wake_count; i++)
+ irq_set_irq_wake(arizona->irq, 1);
+
+ arizona->pending_wake_count = 0;
+
+ mutex_unlock(&arizona->irq_lock);
+}
+
static int arizona_irq_set_wake(struct irq_data *data, unsigned int on)
{
struct arizona *arizona = irq_data_get_irq_chip_data(data);
- return irq_set_irq_wake(arizona->irq, on);
+ if (on)
+ arizona->pending_wake_count++;
+ else
+ arizona->pending_wake_count--;
+
+ return 0;
}
static struct irq_chip arizona_irq_chip = {
.name = "arizona",
.irq_disable = arizona_irq_disable,
.irq_enable = arizona_irq_enable,
+ .irq_bus_lock = arizona_irq_lock,
+ .irq_bus_sync_unlock = arizona_irq_sync_unlock,
.irq_set_wake = arizona_irq_set_wake,
};
@@ -193,6 +224,8 @@ int arizona_irq_init(struct arizona *arizona)
const struct regmap_irq_chip *aod, *irq;
struct irq_data *irq_data;
+ mutex_init(&arizona->irq_lock);
+
arizona->ctrlif_error = true;
switch (arizona->type) {
diff --git a/include/linux/mfd/arizona/core.h b/include/linux/mfd/arizona/core.h
index d55a422..a0374ea 100644
--- a/include/linux/mfd/arizona/core.h
+++ b/include/linux/mfd/arizona/core.h
@@ -148,6 +148,9 @@ struct arizona {
uint16_t dac_comp_coeff;
uint8_t dac_comp_enabled;
struct mutex dac_comp_lock;
+
+ int pending_wake_count;
+ struct mutex irq_lock;
};
int arizona_clk32k_enable(struct arizona *arizona);
--
2.1.4
next reply other threads:[~2016-03-10 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 10:16 Charles Keepax [this message]
[not found] ` <20160324123618.GB3496@x1>
2016-03-24 12:44 ` [PATCH RESEND] mfd: arizona: Fix lockdep recursion warning on set_irq_wake Lee Jones
2016-03-24 12:56 ` Thomas Gleixner
2016-03-24 15:35 ` Charles Keepax
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=1457605009-7792-1-git-send-email-ckeepax@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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