[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <575EDECC.1050502@arm.com>
Date: Mon, 13 Jun 2016 17:26:52 +0100
From: Marc Zyngier <marc.zyngier@....com>
To: Sebastian Frias <sf84@...oste.net>
Cc: Mason <slash.tmp@...e.fr>, Thomas Gleixner <tglx@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Grygorii Strashko <grygorii.strashko@...com>,
Sricharan R <r.sricharan@...com>,
Mans Rullgard <mans@...sr.com>
Subject: Re: Using irq-crossbar.c
On 13/06/16 16:15, Sebastian Frias wrote:
>>> 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
>>
>> I know which file that is, it is mentioned in the diff. I was merely
>> trying to point out the glaring mistakes that could be enough for a
>> interrupt controller hierarchy to be completely non-functional:
>>
>> - Your crossbar doesn't have a #interrupt-cells property. How do you
>> expect the interrupt specifiers to be interpreted?
>
> Thanks for the pointer, actually, after adding "#interrupt-cells =
> <3>;" I can see the driver getting requests for domain maps and
> xlates :-)
OK, we're getting somewhere.
>> - You've changed the default interrupt controller to be your crossbar.
>> Which means that all the sub-nodes are inheriting it. Have you
>> checked that this was valid for all of these nodes?
>
> What do you mean with "valid for all these nodes"? All HW irq lines go to the crossbar.
All the interrupt lines *in the system*? Or just those that are in the
nodes below the "soc" section?
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists