From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Anson Huang <anson.huang@nxp.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
Aisheng Dong <aisheng.dong@nxp.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
Daniel Baluta <daniel.baluta@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rtc@vger.kernel.org" <linux-rtc@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH V5 4/4] rtc: imx-sc: add rtc alarm support
Date: Mon, 1 Apr 2019 15:11:30 +0200 [thread overview]
Message-ID: <20190401131130.GE3430@piout.net> (raw)
In-Reply-To: <1552878291-22866-4-git-send-email-Anson.Huang@nxp.com>
On 18/03/2019 03:10:06+0000, Anson Huang wrote:
> Add i.MX system controller RTC alarm support, the RTC alarm
> is implemented via SIP(silicon provider) runtime service call
> and ARM-Trusted-Firmware will communicate with system controller
> via MU(message unit) IPC to set RTC alarm. When RTC alarm fires,
> system controller will generate a common MU irq event and notify
> system controller RTC driver to handle the irq event.
>
> Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> ---
> No function changes, just update imx_scu_irq_register_notifier() function name
> according to SCU IRQ function name change.
> ---
> drivers/rtc/rtc-imx-sc.c | 112 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 112 insertions(+)
>
Applied, thanks.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-01 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 3:09 [PATCH V5 1/4] dt-bindings: fsl: scu: add general interrupt support Anson Huang
2019-03-18 3:09 ` [PATCH V5 2/4] firmware: imx: enable imx scu general irq function Anson Huang
2019-04-03 8:47 ` Shawn Guo
2019-04-08 10:35 ` Aisheng Dong
2019-04-08 13:05 ` Anson Huang
2019-03-18 3:10 ` [PATCH V5 3/4] arm64: dts: freescale: imx8qxp: enable scu general irq channel Anson Huang
2019-03-18 3:10 ` [PATCH V5 4/4] rtc: imx-sc: add rtc alarm support Anson Huang
2019-04-01 13:11 ` Alexandre Belloni [this message]
2019-04-01 15:26 ` Alexandre Belloni
2019-04-01 15:28 ` Alexandre Belloni
2019-04-08 11:08 ` Aisheng Dong
2019-04-09 1:59 ` Anson Huang
2019-04-09 3:08 ` Aisheng Dong
2019-04-01 2:38 ` [PATCH V5 1/4] dt-bindings: fsl: scu: add general interrupt support Anson Huang
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=20190401131130.GE3430@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=aisheng.dong@nxp.com \
--cc=anson.huang@nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=ulf.hansson@linaro.org \
/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).