From: Marc Zyngier <marc.zyngier@arm.com>
To: Youlin Pei <youlin.pei@mediatek.com>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: 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: Fri, 7 Apr 2017 09:52:54 +0100 [thread overview]
Message-ID: <771954fe-c994-96be-76ab-ece75383d058@arm.com> (raw)
In-Reply-To: <1491552397-7893-1-git-send-email-youlin.pei@mediatek.com>
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.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-04-07 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 8:06 [PATCH v4 0/3] Add Mediatek CIRQ interrupt controller Youlin Pei
[not found] ` <1491552397-7893-1-git-send-email-youlin.pei-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
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 ` Marc Zyngier [this message]
[not found] ` <771954fe-c994-96be-76ab-ece75383d058-5wv7dgnIgG8@public.gmane.org>
2017-04-07 9:54 ` [PATCH v4 0/3] Add Mediatek CIRQ interrupt controller Youlin Pei
2017-05-10 9:42 ` Matthias Brugger
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=771954fe-c994-96be-76ab-ece75383d058@arm.com \
--to=marc.zyngier@arm.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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.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