[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140626074209.GE28884@atomide.com>
Date: Thu, 26 Jun 2014 00:42:09 -0700
From: Tony Lindgren <tony@...mide.com>
To: Sricharan R <r.sricharan@...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
Subject: Re: [PATCH V4 00/16] irqchip: crossbar: Driver fixes
* Sricharan R <r.sricharan@...com> [140626 00:14]:
> This series does some cleanups, fixes for handling two interrupts
> getting mapped twice to same crossbar and provides support for
> hardwired IRQ and crossbar definitions.
>
> On certain platforms such as DRA7, SPIs 0, 1, 2, 3, 5, 6, 10,
> 131, 132, 133 are direct wired to hardware blocks bypassing
> crossbar. This quirky implementation is *NOT* supposed to be the
> expectation of crossbar hardware usage. This series adds support
> to represent such hard-wired irqs through DT and avoid generic
> allocation/programming of crossbar in the driver.
>
> This way of supporting hard-wired irqs was a result of
> the below discussions.
> http://www.spinics.net/lists/arm-kernel/msg329946.html
>
> Based on 3.16 rc2 mainline.
Jason, once these patches look OK for merging, can you please
set them up into an immutable branch so I too can merge them in?
The immutable branch is needed so I can eventually apply
the related .dts changes to enable the crossbar interrupts.
Regards,
Tony
--
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