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:15:17 +0100 [thread overview]
Message-ID: <57C98975.5020607@arm.com> (raw)
In-Reply-To: <483F737F-9868-4E8A-A831-AA3F6F410AFF@gmail.com>
[cc-ing the maintainers of the code usually helps]
On 02/09/16 07:51, Andras Szemzo wrote:
> Hi,
>
> I try to use 4.8-rc2 on my armv7m board, and I have a problem with GPIO IRQ.
> In my device-tree, I define the ethernet PHY IRQ like this:
>
> pioC: gpio at 0x400e1200 {
> compatible = "atmel,at91sam9x5-gpio", "atmel,at91rm9200-gpio";
> reg = <0x400e1200 0x200>;
> interrupts = <12>;
> #gpio-cells = <2>;
> gpio-controller;
> interrupt-controller;
> #interrupt-cells = <2>;
> clocks = <&pioC_clk>;
> };
> ...
> ethernet-phy at 1 {
> reg = <1>;
> interrupt-parent = <&pioC>;
> interrupts = <11 IRQ_TYPE_EDGE_FALLING>;
So this is the interrupt that gets a mismatch.
> reset-gpios = <&pioC 10 GPIO_ACTIVE_HIGH>;
> };
>
> with the 4.8-rc2 kernel at boot it fails with error:
>
> irq: type mismatch, failed to map hwirq-11 for /soc/pinctrl at 0x400e0e00/gpio at 0x400e1200!
>
> This error comes from kernel/irq/irq_domain.c, irq_create_fwspec_mapping().
>
> My quick hack was to replace this function from 4.6.0 (where with the same device-tree, same kernel config it works)
> and everything works as expected.
>
> Maybe this hack is hiding a problem from somewhere else, but I can?t figure out what I missed.
Is there any other device in your system that uses the same interrupt?
Where can I see your full DT file?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-09-02 14:15 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 [this message]
2016-09-02 14:29 ` Andras Szemzo
2016-09-02 14:47 ` Marc Zyngier
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=57C98975.5020607@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.