From: Aisheng Dong <aisheng.dong@nxp.com>
To: Anson Huang <anson.huang@nxp.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@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>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
Andy Gross <andy.gross@linaro.org>,
"heiko@sntech.de" <heiko@sntech.de>,
"horms+renesas@verge.net.au" <horms+renesas@verge.net.au>,
"arnd@arndb.de" <arnd@arndb.de>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"jagan@amarulasolutions.com" <jagan@amarulasolutions.com>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"enric.balletbo@collabora.com" <enric.balletbo@collabora.com>,
"marc.w.gonzalez@free.fr" <marc.w.gonzalez@free.fr>,
"olof@lixom.net" <olof@lixom.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>
Cc: dl-linux-imx <linux-imx@nxp.com>
Subject: RE: [PATCH V7 1/3] watchdog: imx_sc: Add i.MX system controller watchdog support
Date: Fri, 8 Mar 2019 02:25:48 +0000 [thread overview]
Message-ID: <AM0PR04MB4211321FEC8827FD105F7028804D0@AM0PR04MB4211.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DB3PR0402MB391641F558061A561162136CF54C0@DB3PR0402MB3916.eurprd04.prod.outlook.com>
[...]
> >
> > > > As I replied in another mail, it actually does not depend on SCU.
> > > > Let's wait for Rob's comment on whether we could move watchdog Out
> > > > of SCU node.
> > >
> > > Per previous discussion, the dependency here is to prevent enabling
> > > this module for platform without IMX SCU, although it does NOT use
> > > SCU IPC call, but the SMC call trap into ARM-Trusted-Firmware will
> > > eventually call SCU API, so it still depends on IMX SCU hardware, I
> > > am NOT very sure if it is correct to remove it here.
> > >
> >
> > Then it's ATF depends on SCU, not this virtual watchdog based on ARM
> > SIP, right?
>
> But we don't have ATF driver in Linux kernel..., I am confused, anyway, if
> Guenter agrees, I can remove this dependency here.
>
So far the only thing that watchdog depends on SCU driver is that it needs
SCU driver to create a platform devices for it.
We need wait Rob's feedback, if he agree moved the watchdog node
Out of SCU, we can remove this dependency.
Regards
Dong Aisheng
> Anson.
>
> >
> > Regards
> > Dong Aisheng
> >
> > > >
> > > > > + depends on HAVE_ARM_SMCCC
> > > > > + select WATCHDOG_CORE
> > > > > + help
> > > > > + This is the driver for the system controller watchdog
> > > > > + on the NXP i.MX SoCs with system controller inside.
> > > > > + If you have one of these processors and wish to have
> > > > > + watchdog support enabled, say Y, otherwise say N.
> > > > > +
prev parent reply other threads:[~2019-03-08 2:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:06 [PATCH V7 1/3] watchdog: imx_sc: Add i.MX system controller watchdog support Anson Huang
2019-03-06 1:06 ` [PATCH V7 2/3] arm64: defconfig: add support for i.MX system controller watchdog Anson Huang
2019-03-06 16:06 ` Guenter Roeck
2019-03-06 1:06 ` [PATCH V7 3/3] firmware: imx: imx-scu: register build-in child devices Anson Huang
2019-03-06 16:05 ` Guenter Roeck
2019-03-07 0:46 ` Anson Huang
2019-03-07 12:26 ` Aisheng Dong
2019-03-06 16:06 ` [PATCH V7 1/3] watchdog: imx_sc: Add i.MX system controller watchdog support Guenter Roeck
2019-03-07 13:33 ` Aisheng Dong
2019-03-07 13:56 ` Anson Huang
2019-03-07 13:59 ` Aisheng Dong
2019-03-07 14:13 ` Anson Huang
2019-03-08 2:25 ` Aisheng Dong [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=AM0PR04MB4211321FEC8827FD105F7028804D0@AM0PR04MB4211.eurprd04.prod.outlook.com \
--to=aisheng.dong@nxp.com \
--cc=andy.gross@linaro.org \
--cc=anson.huang@nxp.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=enric.balletbo@collabora.com \
--cc=festevam@gmail.com \
--cc=heiko@sntech.de \
--cc=horms+renesas@verge.net.au \
--cc=jagan@amarulasolutions.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-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marc.w.gonzalez@free.fr \
--cc=maxime.ripard@bootlin.com \
--cc=olof@lixom.net \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=will.deacon@arm.com \
--cc=wim@linux-watchdog.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).