[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53ABDA9A.8000108@ti.com>
Date: Thu, 26 Jun 2014 14:02:26 +0530
From: Sricharan R <r.sricharan@...com>
To: Tony Lindgren <tony@...mide.com>
CC: <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<santosh.shilimkar@...com>, <nm@...com>, <rnayak@...com>,
<linux@....linux.org.uk>, <tglx@...utronix.de>,
<jason@...edaemon.net>, <joe@...ches.com>,
Benoit Cousson <bcousson@...libre.com>
Subject: Re: [PATCH V4 2/2] arm: dts: dra7: add crossbar device binding
Hi Tony,
On Thursday 26 June 2014 01:14 PM, Tony Lindgren wrote:
> * Sricharan R <r.sricharan@...com> [140626 00:29]:
>> From: R Sricharan <r.sricharan@...com>
>>
>> There is a IRQ crossbar device in the soc, which
>> maps the irq requests from the peripherals to the
>> mpu interrupt controller's inputs. The Peripheral irq
>> requests are connected to only one crossbar
>> input and the output of the crossbar is connected to only one
>> controller's input line. The crossbar device is used to map
>> a peripheral input to a free mpu's interrupt controller line.
>>
>> Here, adding a new crossbar device node and replacing all the peripheral
>> interrupt numbers with its fixed crossbar input lines.
>
> I think these two patches need to be a single patch to avoid
> breaking booting for git bisect inbetween these patches?
This does not cause booting issues. irq_desc gets allocated linearly,
but that does not create boot issues.
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