From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: grant-likely@linaro.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: rob.herring@calxeda.com
Subject: [PATCH v1 2/2] of: irq: Ignore disabled interrupt controllers
Date: Wed, 27 Nov 2013 23:26:13 -0800 [thread overview]
Message-ID: <e395866d7910723ed8cf82ba9475ef51ac6443f2.1385623064.git.peter.crosthwaite@xilinx.com> (raw)
In-Reply-To: <cover.1385623064.git.peter.crosthwaite@xilinx.com>
In-Reply-To: <cover.1385623064.git.peter.crosthwaite@xilinx.com>
When searching the system for interrupt controllers, skip over any
that are explicitly disabled.
This makes interrupt controllers consistent with regular devices,
which can be marked as do-not-probe via the status = "disabled" dts
property.
Signed-off-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Acked-by: Michal Simek <michal.simek@xilinx.com>
---
drivers/of/irq.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/of/irq.c b/drivers/of/irq.c
index 22e414b..bf80268 100644
--- a/drivers/of/irq.c
+++ b/drivers/of/irq.c
@@ -441,7 +441,8 @@ void __init of_irq_init(const struct of_device_id *matches)
INIT_LIST_HEAD(&intc_parent_list);
for_each_matching_node(np, matches) {
- if (!of_find_property(np, "interrupt-controller", NULL))
+ if (!of_find_property(np, "interrupt-controller", NULL) ||
+ !of_device_is_available(np))
continue;
/*
* Here, we allocate and populate an intc_desc with the node
--
1.8.4.4
next prev parent reply other threads:[~2013-11-28 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 7:26 [PATCH v1 0/2] of: irq: Ignore disabled interrupt controllers Peter Crosthwaite
2013-11-28 7:26 ` [PATCH v1 1/2] of: irq: Ignore disabled intc's when searching map Peter Crosthwaite
2013-12-04 4:42 ` Peter Crosthwaite
2013-11-28 7:26 ` Peter Crosthwaite [this message]
2013-12-04 19:24 ` [PATCH v1 0/2] of: irq: Ignore disabled interrupt controllers Rob Herring
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=e395866d7910723ed8cf82ba9475ef51ac6443f2.1385623064.git.peter.crosthwaite@xilinx.com \
--to=peter.crosthwaite@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=grant-likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).