Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932734AbdDGJzE (ORCPT ); Fri, 7 Apr 2017 05:55:04 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:54223 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1756732AbdDGJyv (ORCPT ); Fri, 7 Apr 2017 05:54:51 -0400 Message-ID: <1491558884.24848.3.camel@mtksdaap41> Subject: Re: [PATCH v4 0/3] Add Mediatek CIRQ interrupt controller From: Youlin Pei To: Marc Zyngier CC: Rob Herring , Matthias Brugger , Thomas Gleixner , "Jason Cooper" , Mark Rutland , Russell King , , , , , , , , Date: Fri, 7 Apr 2017 17:54:44 +0800 In-Reply-To: <771954fe-c994-96be-76ab-ece75383d058@arm.com> References: <1491552397-7893-1-git-send-email-youlin.pei@mediatek.com> <771954fe-c994-96be-76ab-ece75383d058@arm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1554 Lines: 45 On Fri, 2017-04-07 at 09:52 +0100, Marc Zyngier wrote: > On 07/04/17 09:06, Youlin Pei wrote: > > In Mediatek SOCs, the CIRQ is a low power interrupt controller designed to > > works outside MCUSYS which comprises with Cortex-Ax cores,CCI and GIC. > > > > The CIRQ controller is integrated in between MCUSYS and interrupt sources > > as the second level interrupt controller. The external interrupts which > > outside MCUSYS will feed through CIRQ then bypass to GIC. > > > > In normal mode(where MCUSYS is active), CIRQ is disabled and interrupts > > will directly issue to MCUSYS. When MCUSYS enters sleep mode, where GIC > > is power downed. CIRQ will be enabled and monitor all edge trigger > > interrupts(only edge trigger interrupts will be lost in this scenario). > > When an edge interrupt is triggered, CIRQ will record the status and > > generated a pulse signal to GIC when flush command is executed. > > > > With CIRQ, MCUSYS can be completely turned off to improve the system > > power consumption without losing interrupts. > > > > change in v4: > > 1. add some comment to explain CIRQ suspend callback. > > 2. rebase on 4.11 > > Hi Youlin, > > I'm happy to take the first two patches through the irq tree. How do we > deal with the third one? It seems to me that it'd be better routed via > armsoc. > > Let me know what you and Matthias want to do. Hi Marc, Thanks for your review. I think that driver and dtsi can merged separately. Hi Matthias, Could you help to review the dtsi patch? Thanks a lot! > > Thanks, > > M.