Darren Etheridge wrote on Tue [2014-May-06 14:58:04 -0500]:
> Nishanth Menon wrote on Tue [2014-May-06 14:46:10 -0500]:
> > On 05/06/2014 02:40 PM, Felipe Balbi wrote:
> > > On Tue, May 06, 2014 at 07:26:17PM +0530, Sricharan R wrote:
> > >> This adds the irq crossbar device node.
> > >>
> > >> T
Nishanth Menon wrote on Tue [2014-May-06 14:46:10 -0500]:
> On 05/06/2014 02:40 PM, Felipe Balbi wrote:
> > On Tue, May 06, 2014 at 07:26:17PM +0530, Sricharan R wrote:
> >> This adds the irq crossbar device node.
> >>
> >> There is a IRQ crossbar device in the soc, which
> >> maps the irq request
On 05/06/2014 02:40 PM, Felipe Balbi wrote:
> On Tue, May 06, 2014 at 07:26:17PM +0530, Sricharan R wrote:
>> This adds the irq crossbar device node.
>>
>> 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
On Tue, May 06, 2014 at 07:26:17PM +0530, Sricharan R wrote:
> This adds the irq crossbar device node.
>
> 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 o
This adds the irq crossbar device node.
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
5 matches
Mail list logo