[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52BD3C2F.9010409@ti.com>
Date: Fri, 27 Dec 2013 14:07:03 +0530
From: Sricharan R <r.sricharan@...com>
To: <balbi@...com>
CC: <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-doc@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-omap@...r.kernel.org>, <linus.walleij@...aro.org>,
<linux@....linux.org.uk>, <tony@...mide.com>, <rnayak@...com>,
<marc.zyngier@....com>, <grant.likely@...aro.org>,
<mark.rutland@....com>, <robherring2@...il.com>,
<tglx@...utronix.de>, <galak@...eaurora.org>,
<rob.herring@...xeda.com>, <santosh.shilimkar@...com>, <nm@...com>,
<bcousson@...libre.com>
Subject: Re: [PATCH V5 2/4] DRIVERS: IRQCHIP: CROSSBAR: Add support for Crossbar
IP
Hi Felipe,
On Friday 27 December 2013 01:31 AM, Felipe Balbi wrote:
> Hi,
>
> On Tue, Dec 03, 2013 at 03:57:23PM +0530, Sricharan R wrote:
>> +static const struct of_device_id crossbar_match[] __initconst = {
>> + { .compatible = "ti,irq-crossbar" },
>> + {}
>> +};
>> +
>> +int irqcrossbar_init(void)
>> +{
>> + struct device_node *np;
>> + np = of_find_matching_node(NULL, crossbar_match);
>> + if (!np)
>> + return -ENODEV;
>> +
>> + crossbar_of_init(np);
>> + return 0;
>> +}
>
> instead, please use IRQCHIP_DECLARE() then you won't need to expose this
> symbol to be used by arch/arm/ code.
>
Crossbar node does not have a "interrupt-controller" property and
not a regular Interrupt controller. This was added in here
after all below discussions
https://lkml.org/lkml/2013/9/18/540
So IRQCHIP_DECLARE() macro cannot be used here.
Regards,
Sricharan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists