From: Mason <slash.tmp@free.fr>
To: Marc Zyngier <marc.zyngier@arm.com>, Sebastian Frias <sf84@laposte.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Sricharan R <r.sricharan@ti.com>, Mans Rullgard <mans@mansr.com>
Subject: Re: Using irq-crossbar.c
Date: Fri, 10 Jun 2016 21:36:29 +0200 [thread overview]
Message-ID: <575B16BD.50600@free.fr> (raw)
In-Reply-To: <575AE52E.9020005@arm.com>
On 10/06/2016 18:05, Marc Zyngier wrote:
> On 10/06/16 16:37, Sebastian Frias wrote:
>
>> here's the diff on our DT:
>>
>> --- tango4-common.dtsi 2016-06-10 16:23:08.244246017 +0200
>> +++ tangox_irqv2-common.dtsi 2016-06-10 16:24:01.212588737 +0200
>> @@ -47,7 +47,7 @@
>>
>> soc {
>> compatible = "simple-bus";
>> - interrupt-parent = <&irq0>;
>> + interrupt-parent = <&irq_mux>;
>> #address-cells = <1>;
>> #size-cells = <1>;
>> ranges;
>> @@ -75,7 +75,7 @@
>> uart: serial@10700 {
>> compatible = "ralink,rt2880-uart";
>> reg = <0x10700 0x30>;
>> - interrupts = <1 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupts = <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>;
>> clock-frequency = <7372800>;
>> reg-shift = <2>;
>> };
>> @@ -83,10 +83,11 @@
>> eth0: ethernet@26000 {
>> compatible = "sigma,smp8734-ethernet";
>> reg = <0x26000 0x800>;
>> - interrupts = <38 IRQ_TYPE_LEVEL_HIGH>;
>> + interrupts = <GIC_SPI 38 IRQ_TYPE_LEVEL_HIGH>;
>> clocks = <&clkgen 1>;
>> };
>>
>> +#if 0
>> intc: interrupt-controller@6e000 {
>> compatible = "sigma,smp8642-intc";
>> reg = <0x6e000 0x400>;
>> @@ -117,5 +118,16 @@
>> interrupts = <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>;
>> };
>> };
>> +#else
>> + irq_mux: irq_mux@6f800 {
>> + compatible = "sigma,smp-irq-mux";
>> + reg = <0x6f800 0x400>;
>> + interrupt-controller;
>> + interrupt-parent = <&gic>;
>> + irqs-reserved = <2 3 4 125 126 127>;
>> + };
>
> Where is the GIC? Where is the #interrupt-cells property? What is the
> interrupt parent for the GIC itself? (and I'm tempted to add "What is
> your name? What is you quest?", but that's because it is Friday and I
> feel like I need a beer...).
Beer and cheese? Beurk! ;-)
I think Sebastian is even more baffled by the DT mess
(sorry, intricacies) than I am.
The base file he was referring to is:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tango4-common.dtsi
Regards.
next prev parent reply other threads:[~2016-06-10 19:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 15:37 Using irq-crossbar.c Sebastian Frias
2016-06-10 16:05 ` Marc Zyngier
2016-06-10 19:36 ` Mason [this message]
2016-06-11 9:58 ` Marc Zyngier
2016-06-11 15:37 ` Mason
2016-06-12 10:00 ` Marc Zyngier
2016-06-12 13:50 ` Mason
2016-06-13 7:58 ` Marc Zyngier
2016-06-13 14:04 ` Lennart Sorensen
2016-06-13 14:57 ` Sebastian Frias
2016-06-13 15:42 ` Lennart Sorensen
2016-06-13 15:49 ` Mason
2016-06-13 15:57 ` Marc Zyngier
2016-06-13 17:55 ` Lennart Sorensen
2016-06-13 15:15 ` Sebastian Frias
2016-06-13 16:26 ` Marc Zyngier
2016-06-13 15:46 ` Sebastian Frias
2016-06-13 16:24 ` Marc Zyngier
2016-06-14 16:37 ` Sebastian Frias
2016-06-14 16:39 ` Sebastian Frias
2016-06-16 12:39 ` Sebastian Frias
2016-06-21 10:18 ` Marc Zyngier
2016-06-21 11:03 ` Sebastian Frias
2016-06-21 12:41 ` Marc Zyngier
2016-06-21 15:29 ` Sebastian Frias
2016-06-13 17:59 ` Lennart Sorensen
2016-06-10 16:06 ` Lennart Sorensen
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=575B16BD.50600@free.fr \
--to=slash.tmp@free.fr \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=marc.zyngier@arm.com \
--cc=r.sricharan@ti.com \
--cc=sf84@laposte.net \
--cc=tglx@linutronix.de \
/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).