linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 01/11] genirq: generic chip: support hierarchy domain
Date: Thu,  9 Apr 2015 22:04:05 +0200	[thread overview]
Message-ID: <1428609855-27657-2-git-send-email-stefan@agner.ch> (raw)
In-Reply-To: <1428609855-27657-1-git-send-email-stefan@agner.ch>

Use the new helper function irq_domain_set_info to make sure the
function irq_domain_set_hwirq_and_chip is being called, which is
crucial to save irqdomain specific data to irq_data.

Signed-off-by: Stefan Agner <stefan@agner.ch>
---
 kernel/irq/generic-chip.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/kernel/irq/generic-chip.c b/kernel/irq/generic-chip.c
index 61024e8..15b370d 100644
--- a/kernel/irq/generic-chip.c
+++ b/kernel/irq/generic-chip.c
@@ -360,7 +360,7 @@ static struct lock_class_key irq_nested_lock_class;
 int irq_map_generic_chip(struct irq_domain *d, unsigned int virq,
 			 irq_hw_number_t hw_irq)
 {
-	struct irq_data *data = irq_get_irq_data(virq);
+	struct irq_data *data = irq_domain_get_irq_data(d, virq);
 	struct irq_domain_chip_generic *dgc = d->gc;
 	struct irq_chip_generic *gc;
 	struct irq_chip_type *ct;
@@ -405,8 +405,7 @@ int irq_map_generic_chip(struct irq_domain *d, unsigned int virq,
 	else
 		data->mask = 1 << idx;
 
-	irq_set_chip_and_handler(virq, chip, ct->handler);
-	irq_set_chip_data(virq, gc);
+	irq_domain_set_info(d, virq, hw_irq, chip, gc, ct->handler, NULL, NULL);
 	irq_modify_status(virq, dgc->irq_flags_to_clear, dgc->irq_flags_to_set);
 	return 0;
 }
-- 
2.3.5

  reply	other threads:[~2015-04-09 20:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 20:04 [PATCH v5 00/11] ARM: vf610m4: Add Vybrid Cortex-M4 support Stefan Agner
2015-04-09 20:04 ` Stefan Agner [this message]
2015-04-09 20:04 ` [PATCH v5 02/11] irqchip: nvic: support hierarchy irq domain Stefan Agner
2015-04-09 20:04 ` [PATCH v5 03/11] irqchip: vf610-mscm: support NVIC parent Stefan Agner
2015-04-09 20:04 ` [PATCH v5 04/11] ARM: ARMv7M: define size of vector table for Vybrid Stefan Agner
2015-04-09 20:04 ` [PATCH v5 05/11] clocksource: add dependencies for Vybrid pit clocksource Stefan Agner
2015-04-09 20:04 ` [PATCH v5 06/11] ARM: unify MMU/!MMU addruart calls Stefan Agner
2015-04-09 20:04 ` [PATCH v5 07/11] ARM: introduce ARM_SINGLE_ARMV7M for ARMv7-M platforms Stefan Agner
2015-04-09 20:04 ` [PATCH v5 08/11] ARM: efm32: use ARM_SINGLE_ARMV7M Stefan Agner
2015-04-09 20:04 ` [PATCH v5 09/11] ARM: vf610: enable Cortex-M4 configuration on Vybrid SoC Stefan Agner
2015-04-10 17:54   ` Paul Bolle
2015-04-09 20:04 ` [PATCH v5 10/11] ARM: dts: add support for Vybrid running on Cortex-M4 Stefan Agner
2015-04-09 20:04 ` [PATCH v5 11/11] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4 Stefan Agner
2015-04-10  8:50 ` [PATCH v5 00/11] ARM: vf610m4: Add Vybrid Cortex-M4 support Maxime Coquelin
2015-04-11  0:13 ` Jason Cooper
2015-04-13 23:27 ` Arnd Bergmann

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=1428609855-27657-2-git-send-email-stefan@agner.ch \
    --to=stefan@agner.ch \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).