From: Aisheng Dong <aisheng.dong@nxp.com>
To: Anson Huang <anson.huang@nxp.com>,
Shawn Guo <shawnguo@kernel.org>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>
Cc: "robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"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>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"sboyd@kernel.org" <sboyd@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
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: [EXT] Re: [PATCH V7 2/4] firmware: imx: enable imx scu general irq function
Date: Fri, 12 Apr 2019 02:25:42 +0000 [thread overview]
Message-ID: <AM0PR04MB4211816EDBEF23F7B330CCCB80280@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DB3PR0402MB3916B67E6DA995AB70C29799F5280@DB3PR0402MB3916.eurprd04.prod.outlook.com>
> From: Anson Huang
> Sent: Friday, April 12, 2019 9:06 AM
>
> Hello, Alexandre
> As i.MX SCU general irq function is picked up by Shawn, could you please
> also pick up below i.MX SC RTC alarm support patch ?
> https://patchwork.kernel.org/patch/10890525/
>
No, it can't go through Alexandre's tree due to dependency issue.
Shawn,
Do you think you can pick it up? Alexandre already gave the Ack.
AFAIK there's no other SCU RTC patches since v5.1-rc1 in Alexandre's tree.
Regards
Dong Aisheng
> > On Tue, Apr 09, 2019 at 04:59:55AM +0000, Anson Huang wrote:
> > > The System Controller Firmware (SCFW) controls RTC, thermal and WDOG
> > > etc., these resources' interrupt function are managed by SCU. When
> > > any IRQ pending, SCU will notify Linux via MU general interrupt
> > > channel #3, and Linux kernel needs to call SCU APIs to get IRQ
> > > status and notify each module to handle the interrupt.
> > >
> > > Since there is no data transmission for SCU IRQ notification, so
> > > doorbell mode is used for this MU channel, and SCU driver will use
> > > notifier mechanism to broadcast to every module which registers the
> > > SCU block notifier.
> > >
> > > Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
> > > Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
> >
> > Applied, thanks.
next prev parent reply other threads:[~2019-04-12 2:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 4:59 [PATCH V7 1/4] dt-bindings: fsl: scu: add general interrupt support Anson Huang
2019-04-09 4:59 ` [PATCH V7 2/4] firmware: imx: enable imx scu general irq function Anson Huang
2019-04-11 7:32 ` Shawn Guo
2019-04-12 1:05 ` [EXT] " Anson Huang
2019-04-12 2:25 ` Aisheng Dong [this message]
2019-04-12 2:32 ` Anson Huang
2019-04-12 8:41 ` Alexandre Belloni
2019-04-15 9:23 ` Shawn Guo
2019-04-09 5:00 ` [PATCH V7 3/4] arm64: dts: freescale: imx8qxp: enable scu general irq channel Anson Huang
2019-04-11 7:34 ` Shawn Guo
2019-04-09 5:00 ` [PATCH V7 4/4] rtc: imx-sc: add rtc alarm support Anson Huang
2019-04-12 8:41 ` Alexandre Belloni
2019-06-01 21:18 ` Alexandre Belloni
2019-04-11 1:37 ` [PATCH V7 1/4] dt-bindings: fsl: scu: add general interrupt support Anson Huang
2019-04-11 7:32 ` Shawn Guo
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=AM0PR04MB4211816EDBEF23F7B330CCCB80280@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.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=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--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).