From mboxrd@z Thu Jan 1 00:00:00 1970 From: jason@lakedaemon.net (Jason Cooper) Date: Fri, 3 Apr 2015 14:29:22 +0000 Subject: [PATCH 4/5] irqchip: armada-370-xp: Allow using wakeup source In-Reply-To: <551E3EA3.8010409@free-electrons.com> References: <1427724278-12379-1-git-send-email-gregory.clement@free-electrons.com> <1427724278-12379-5-git-send-email-gregory.clement@free-electrons.com> <20150402232316.GJ24598@io.lakedaemon.net> <551E3EA3.8010409@free-electrons.com> Message-ID: <20150403142922.GL24598@io.lakedaemon.net> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, Apr 03, 2015 at 09:17:55AM +0200, Gregory CLEMENT wrote: > Hi Jason, > > On 03/04/2015 01:23, Jason Cooper wrote: > > On Mon, Mar 30, 2015 at 04:04:37PM +0200, Gregory CLEMENT wrote: > >> On the Armada 370/XP SoCs, in standby mode the SoC stay powered and it > >> is possible to wake-up from any interrupt sources. This patch adds > >> flag to the MPIC irqchip driver to let linux know this. > >> > >> Signed-off-by: Gregory CLEMENT > >> --- > >> drivers/irqchip/irq-armada-370-xp.c | 1 + > >> 1 file changed, 1 insertion(+) > > > > Applied to irqchip/mvebu > > Thanks! > > Do you agree to take also the patch 3? hmmm... > It modifies a file in mach-mvebu (board-v7.c) but it depends on a patch > located in irqchip: "irqchip: gic: Add an entry point to set up irqchip flags" Yeah, I saw that. Do you forsee any merge conflicts with mvebu? The reason I ask is that it looks like I'm going to be sending directly to Linus this cycle. I'd really prefer to hold off a cycle on that patch. I'm not 100% certain my second PR (stacked domain/DT break) is going to get accepted. Which is what this patch depends on. thoughts? thx, Jason.