From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: irq_create_fwspec_mapping() in 4.8-rc2
Date: Fri, 2 Sep 2016 15:47:45 +0100 [thread overview]
Message-ID: <57C99111.3030105@arm.com> (raw)
In-Reply-To: <9FCA11A3-B677-42EA-80DB-674AC8E489E8@gmail.com>
On 02/09/16 15:29, Andras Szemzo wrote:
> Hi,
>
>> On 02 Sep 2016, at 16:15, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>
>> So this is the interrupt that gets a mismatch.
>
> Yes.
>
>> Is there any other device in your system that uses the same interrupt?
>> Where can I see your full DT file?
>
> There is no other device using pioC 11.
> Here is the DT:
>
> http://pastebin.com/G7Z0hF5v
Can you try this patch and report the values you find?
diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
index 4752b43..d79d780 100644
--- a/kernel/irq/irqdomain.c
+++ b/kernel/irq/irqdomain.c
@@ -623,7 +623,8 @@ unsigned int irq_create_fwspec_mapping(struct irq_fwspec *fwspec)
return virq;
}
- pr_warn("type mismatch, failed to map hwirq-%lu for %s!\n",
+ pr_warn("type mismatch (%u/%u), failed to map hwirq-%lu for %s!\n",
+ type, irq_get_trigger_type(virq),
hwirq, of_node_full_name(to_of_node(fwspec->fwnode)));
return 0;
}
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-09-02 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 6:51 irq_create_fwspec_mapping() in 4.8-rc2 Andras Szemzo
2016-09-02 14:15 ` Marc Zyngier
2016-09-02 14:29 ` Andras Szemzo
2016-09-02 14:47 ` Marc Zyngier [this message]
2016-09-02 14:52 ` Andras Szemzo
2016-09-02 15:09 ` Marc Zyngier
2016-09-02 15:15 ` Andras Szemzo
2016-09-02 15:31 ` Marc Zyngier
2016-09-05 12:40 ` Linus Walleij
2016-09-05 12:56 ` Marc Zyngier
2016-09-05 21:41 ` Linus Walleij
2016-09-06 5:53 ` Nicolas Ferre
2016-09-05 13:10 ` Nicolas Ferre
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=57C99111.3030105@arm.com \
--to=marc.zyngier@arm.com \
--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).