From: mans@mansr.com (Måns Rullgård)
To: linux-arm-kernel@lists.infradead.org
Subject: Porting MIPS IRQ handler to ARM
Date: Wed, 02 Sep 2015 18:17:36 +0100 [thread overview]
Message-ID: <yw1xy4goyc3z.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <55E722F2.50905@free.fr> (Mason's message of "Wed, 02 Sep 2015 18:25:22 +0200")
Mason <slash.tmp@free.fr> writes:
> On 01/09/2015 18:58, Florian Fainelli wrote:
>
>> On 01/09/15 09:14, Mason wrote:
>>
>>> I'm trying to port to my ARM platform: IRQ handling code written for MIPS.
>>> https://github.com/mansr/linux-tangox/blob/master/drivers/irqchip/irq-tangox.c
>>
>> Calling clear_c0_status() and write_c0_status() in tangox_irq_handler()
>> sounds like a layering violation here, this should be taken care of by
>> the interrupt code once proper parenting between the MIPS IRQ controller
>> and your tangox controller is established.
>
> Following Mans' suggestion, I deleted the arch-specific code, and
> the driver now compiles and links.
>
> Unfortunately, I still can't get it to work, and I've been banging
> my head against the wall over this device tree monstrosity.
>
> tangox_irq_init() fails in irq_of_parse_and_map()
>
> I see that
> irqchip_init is called
> gic_of_init is called
> but of_irq_parse_one(dev, index, &oirq) fails... :-(
Use the latest DT from my tree. It looks like you're missing some
changes.
--
M?ns Rullg?rd
mans at mansr.com
next prev parent reply other threads:[~2015-09-02 17:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 16:14 Porting MIPS IRQ handler to ARM Mason
2015-09-01 16:58 ` Florian Fainelli
2015-09-02 16:25 ` Mason
2015-09-02 17:17 ` Måns Rullgård [this message]
2015-09-02 18:01 ` Mason
2015-09-04 16:13 ` Mason
2015-09-04 16:36 ` Måns Rullgård
2015-09-04 17:46 ` Mason
2015-09-04 21:49 ` Måns Rullgård
2015-09-04 16:37 ` Måns Rullgård
2015-09-04 21:20 ` Matthias Brugger
2015-09-01 17:07 ` Måns Rullgård
2015-09-01 17:57 ` Mason
2015-09-01 18:07 ` Florian Fainelli
2015-09-01 19:01 ` Mason
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=yw1xy4goyc3z.fsf@unicorn.mansr.com \
--to=mans@mansr.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).