From: Matthias Brugger <matthias.bgg@gmail.com>
To: Youlin Pei <youlin.pei@mediatek.com>,
Marc Zyngier <marc.zyngier@arm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Mark Rutland <mark.rutland@arm.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, srv_heupstream@mediatek.com,
hongkun.cao@mediatek.com, yong.wu@mediatek.com,
erin.lo@mediatek.com
Subject: Re: [PATCH v4 0/3] Add Mediatek CIRQ interrupt controller
Date: Wed, 10 May 2017 11:42:19 +0200 [thread overview]
Message-ID: <36732dc3-e113-246c-0828-150e9b31f4fb@gmail.com> (raw)
In-Reply-To: <1491558884.24848.3.camel@mtksdaap41>
On 07/04/17 11:54, Youlin Pei wrote:
> 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?
queued now for v4.12-next/dts32
sorry for the late answer.
Matthias
> Thanks a lot!
>
>>
>> Thanks,
>>
>> M.
>
>
prev parent reply other threads:[~2017-05-10 9:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 8:06 Youlin Pei
2017-04-07 8:06 ` [PATCH v4 1/3] binding: irqchip: mtk-cirq: Add binding document Youlin Pei
2017-04-07 8:06 ` [PATCH v4 2/3] irqchip: mtk-cirq: Add mediatek mtk-cirq implement Youlin Pei
2017-04-07 8:06 ` [PATCH v4 3/3] ARM: dts: mt2701: Add mtk-cirq node for mt2701 Youlin Pei
2017-04-07 8:52 ` [PATCH v4 0/3] Add Mediatek CIRQ interrupt controller Marc Zyngier
2017-04-07 9:54 ` Youlin Pei
2017-05-10 9:42 ` Matthias Brugger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36732dc3-e113-246c-0828-150e9b31f4fb@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=erin.lo@mediatek.com \
--cc=hongkun.cao@mediatek.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tglx@linutronix.de \
--cc=yong.wu@mediatek.com \
--cc=youlin.pei@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome