* [PATCH] regmap: no need primary handler for nested irq
@ 2012-09-08 10:53 Yunfan Zhang
2012-09-09 3:05 ` Mark Brown
0 siblings, 1 reply; 2+ messages in thread
From: Yunfan Zhang @ 2012-09-08 10:53 UTC (permalink / raw)
To: Mark Brown; +Cc: linux-kernel@vger.kernel.org
The primary handler will NOT be called if the interrupt nests into
another interrupt thread. Remove it to avoid confusing.
Signed-off-by: Yunfan Zhang <yfzhang@marvell.com>
---
drivers/base/regmap/regmap-irq.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/base/regmap/regmap-irq.c b/drivers/base/regmap/regmap-irq.c
index c9ff9f0..5972ad9 100644
--- a/drivers/base/regmap/regmap-irq.c
+++ b/drivers/base/regmap/regmap-irq.c
@@ -226,7 +226,7 @@ static int regmap_irq_map(struct irq_domain *h, unsigned int virq,
struct regmap_irq_chip_data *data = h->host_data;
irq_set_chip_data(virq, data);
- irq_set_chip_and_handler(virq, &data->irq_chip, handle_edge_irq);
+ irq_set_chip(virq, &data->irq_chip);
irq_set_nested_thread(virq, 1);
/* ARM needs us to explicitly flag the IRQ as valid
--
1.7.0.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] regmap: no need primary handler for nested irq
2012-09-08 10:53 [PATCH] regmap: no need primary handler for nested irq Yunfan Zhang
@ 2012-09-09 3:05 ` Mark Brown
0 siblings, 0 replies; 2+ messages in thread
From: Mark Brown @ 2012-09-09 3:05 UTC (permalink / raw)
To: Yunfan Zhang; +Cc: linux-kernel@vger.kernel.org
On Sat, Sep 08, 2012 at 03:53:25AM -0700, Yunfan Zhang wrote:
> The primary handler will NOT be called if the interrupt nests into
> another interrupt thread. Remove it to avoid confusing.
Applied, thanks.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-09-09 3:05 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-08 10:53 [PATCH] regmap: no need primary handler for nested irq Yunfan Zhang
2012-09-09 3:05 ` Mark Brown
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).