lkml.org 
[lkml]   [2013]   [Sep]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] of: irq: Pass trigger type in IRQ resource flags
Date
Some drivers might rely on availability of trigger flags in IRQ
resource, for example to configure the hardware for particular interrupt
type. However current code creating IRQ resources from data in device
tree does not configure trigger flags in resulting resources.

This patch tries to solve the problem, based on the fact that
irq_of_parse_and_map() configures the trigger based on DT interrupt
specifier and IRQD_TRIGGER_* flags are consistent with IORESOURCE_IRQ_*,
and we can get correct trigger flags by calling irqd_get_trigger_type()
after mapping the interrupt.

Signed-off-by: Tomasz Figa <tomasz.figa@gmail.com>
---
drivers/of/irq.c | 10 ++++++++++
1 file changed, 10 insertions(+)

diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 1752988..12742d0 100644
--- a/drivers/of/irq.c
+++ b/drivers/of/irq.c
@@ -356,6 +356,16 @@ int of_irq_to_resource(struct device_node *dev, int index, struct resource *r)
r->start = r->end = irq;
r->flags = IORESOURCE_IRQ;
r->name = name ? name : dev->full_name;
+
+ /*
+ * Some drivers might rely on availability of trigger flags
+ * in IRQ resource. Since irq_of_parse_and_map() configures the
+ * trigger based on interrupt specifier and IRQD_TRIGGER_*
+ * flags are consistent with IORESOURCE_IRQ_*, we can get
+ * trigger type that was just set and pass it through resource
+ * flags as well.
+ */
+ r->flags |= irqd_get_trigger_type(irq_get_irq_data(irq));
}

return irq;
--
1.8.3.2


\
 
 \ /
  Last update: 2013-09-28 20:21    [W:0.039 / U:0.008 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site