From: Marc Zyngier <marc.zyngier@arm.com>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org, z.chenhui@gmail.com,
Chenhui Zhao <chenhui.zhao@nxp.com>,
jason.jin@nxp.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH 2/2] soc: nxp: Add a RCPM driver
Date: Mon, 1 Aug 2016 13:55:27 +0100 [thread overview]
Message-ID: <579F46BF.4080604@arm.com> (raw)
In-Reply-To: <2024386.Ra8uvttlE9@wuerfel>
On 01/08/16 13:25, Arnd Bergmann wrote:
> On Monday, August 1, 2016 5:49:03 PM CEST Chenhui Zhao wrote:
>> The NXP's QorIQ Processors based on ARM Core have a RCPM module
>> (Run Control and Power Management), which performs all device-level
>> tasks associated with power management.
>>
>> This patch mainly implements the wakeup sources configuration before
>> entering LPM20, a low power state of device-level. The devices can be
>> waked up by specified sources, such as Flextimer, GPIO and so on.
>>
>> Signed-off-by: Chenhui Zhao <chenhui.zhao@nxp.com>
>
> Adding irqchip maintainers to cc, as this wakeup handling is normally
> part of the irq controller.
Thanks for looping me in. This very much look like it should be a
stacked irqchip, just like we handle everything else. I'll go and review
the actual patch.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-08-01 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:49 [PATCH 1/2] ARM: dts: ls1043a: add a rcpm node Chenhui Zhao
2016-08-01 9:49 ` [PATCH 2/2] soc: nxp: Add a RCPM driver Chenhui Zhao
2016-08-01 12:25 ` Arnd Bergmann
2016-08-01 12:55 ` Marc Zyngier [this message]
2016-08-03 3:42 ` Chenhui Zhao
[not found] ` <1470044943-3814-2-git-send-email-chenhui.zhao-3arQi8VN3Tc@public.gmane.org>
2016-08-01 13:22 ` Marc Zyngier
2016-08-03 3:28 ` Chenhui Zhao
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=579F46BF.4080604@arm.com \
--to=marc.zyngier@arm.com \
--cc=arnd@arndb.de \
--cc=chenhui.zhao@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=jason.jin@nxp.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=z.chenhui@gmail.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;
as well as URLs for NNTP newsgroup(s).