[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH8PR18MB538137DD102CAA420746CDB8C5CA2@PH8PR18MB5381.namprd18.prod.outlook.com>
Date: Thu, 6 Mar 2025 09:40:50 +0000
From: George Cherian <gcherian@...vell.com>
To: Julius Werner <jwerner@...omium.org>
CC: "linux@...ck-us.net" <linux@...ck-us.net>,
"wim@...ux-watchdog.org"
<wim@...ux-watchdog.org>,
"evanbenn@...omium.org" <evanbenn@...omium.org>,
"kabel@...nel.org" <kabel@...nel.org>,
"krzk@...nel.org" <krzk@...nel.org>,
"mazziesaccount@...il.com" <mazziesaccount@...il.com>,
"thomas.richard@...tlin.com" <thomas.richard@...tlin.com>,
"lma@...omium.org"
<lma@...omium.org>,
"bleung@...omium.org" <bleung@...omium.org>,
"support.opensource@...semi.com" <support.opensource@...semi.com>,
"shawnguo@...nel.org" <shawnguo@...nel.org>,
"s.hauer@...gutronix.de"
<s.hauer@...gutronix.de>,
"kernel@...gutronix.de" <kernel@...gutronix.de>,
"festevam@...il.com" <festevam@...il.com>,
"andy@...nel.org"
<andy@...nel.org>,
"paul@...pouillou.net" <paul@...pouillou.net>,
"alexander.usyskin@...el.com" <alexander.usyskin@...el.com>,
"andreas.werner@....de" <andreas.werner@....de>,
"daniel@...ngy.jp"
<daniel@...ngy.jp>,
"romain.perier@...il.com" <romain.perier@...il.com>,
"avifishman70@...il.com" <avifishman70@...il.com>,
"tmaimon77@...il.com"
<tmaimon77@...il.com>,
"tali.perry1@...il.com" <tali.perry1@...il.com>,
"venture@...gle.com" <venture@...gle.com>,
"yuenn@...gle.com"
<yuenn@...gle.com>,
"benjaminfair@...gle.com" <benjaminfair@...gle.com>,
"maddy@...ux.ibm.com" <maddy@...ux.ibm.com>,
"mpe@...erman.id.au"
<mpe@...erman.id.au>,
"npiggin@...il.com" <npiggin@...il.com>,
"christophe.leroy@...roup.eu" <christophe.leroy@...roup.eu>,
"naveen@...nel.org" <naveen@...nel.org>,
"mwalle@...nel.org"
<mwalle@...nel.org>,
"xingyu.wu@...rfivetech.com"
<xingyu.wu@...rfivetech.com>,
"ziv.xu@...rfivetech.com"
<ziv.xu@...rfivetech.com>,
"hayashi.kunihiko@...ionext.com"
<hayashi.kunihiko@...ionext.com>,
"mhiramat@...nel.org"
<mhiramat@...nel.org>,
"linux-watchdog@...r.kernel.org"
<linux-watchdog@...r.kernel.org>,
"linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"chrome-platform@...ts.linux.dev"
<chrome-platform@...ts.linux.dev>,
"imx@...ts.linux.dev"
<imx@...ts.linux.dev>,
"linux-mips@...r.kernel.org"
<linux-mips@...r.kernel.org>,
"openbmc@...ts.ozlabs.org"
<openbmc@...ts.ozlabs.org>,
"linuxppc-dev@...ts.ozlabs.org"
<linuxppc-dev@...ts.ozlabs.org>,
"patches@...nsource.cirrus.com"
<patches@...nsource.cirrus.com>
Subject: Re: [PATCH v4 1/2] watchdog: Add a new flag WDIOF_STOP_MAYSLEEP
Hi Julius,
>> static const struct watchdog_ops adv_ec_wdt_ops = {
>> diff --git a/drivers/watchdog/arm_smc_wdt.c b/drivers/watchdog/arm_smc_wdt.c
>> index 8f3d0c3a005f..794cf0086912 100644
>> --- a/drivers/watchdog/arm_smc_wdt.c
>> +++ b/drivers/watchdog/arm_smc_wdt.c
>> @@ -90,7 +90,8 @@ static const struct watchdog_info smcwd_info = {
>> .identity = DRV_NAME,
>> .options = WDIOF_SETTIMEOUT |
>> WDIOF_KEEPALIVEPING |
>> - WDIOF_MAGICCLOSE,
>> + WDIOF_MAGICCLOSE |
>> + WDIOF_STOP_MAYSLEEP,
>> };
>
>I don't think this driver can sleep, unless I'm missing something?
The only reason I added to avoid any inadvertent hang in TF-A.
Anyways the approach is going to change so this patch is not
needed anymore.
>`arm_smccc_smc()` does a synchronous call into firmware that always
>returns back to the caller.
Thanks for the insight.
-George
Powered by blists - more mailing lists