[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140627120151.GC23978@titan.lakedaemon.net>
Date: Fri, 27 Jun 2014 08:01:51 -0400
From: Jason Cooper <jason@...edaemon.net>
To: Tony Lindgren <tony@...mide.com>
Cc: Sricharan R <r.sricharan@...com>, 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,
joe@...ches.com
Subject: Re: [PATCH V4 00/16] irqchip: crossbar: Driver fixes
On Thu, Jun 26, 2014 at 12:42:09AM -0700, Tony Lindgren wrote:
> * 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?
Sure thing.
thx,
Jason.
--
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