[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<PH8PR18MB538122CE6706872B8A836A94C5CB2@PH8PR18MB5381.namprd18.prod.outlook.com>
Date: Wed, 5 Mar 2025 10:34:49 +0000
From: George Cherian <gcherian@...vell.com>
To: Marek BehĂșn <kabel@...nel.org>
CC: "linux@...ck-us.net" <linux@...ck-us.net>,
"wim@...ux-watchdog.org"
<wim@...ux-watchdog.org>,
"jwerner@...omium.org" <jwerner@...omium.org>,
"evanbenn@...omium.org" <evanbenn@...omium.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
From: Marek BehĂșn <kabel@...nel.org>
Sent: Wednesday, March 5, 2025 3:48 PM
To: George Cherian <gcherian@...vell.com>
Cc: linux@...ck-us.net; wim@...ux-watchdog.org; jwerner@...omium.org; evanbenn@...omium.org; krzk@...nel.org; mazziesaccount@...il.com; thomas.richard@...tlin.com; lma@...omium.org; bleung@...omium.org; support.opensource@...semi.com; shawnguo@...nel.org; s.hauer@...gutronix.de; kernel@...gutronix.de; festevam@...il.com; andy@...nel.org; paul@...pouillou.net; alexander.usyskin@...el.com; andreas.werner@....de; daniel@...ngy.jp; romain.perier@...il.com; avifishman70@...il.com; tmaimon77@...il.com; tali.perry1@...il.com; venture@...gle.com; yuenn@...gle.com; benjaminfair@...gle.com; maddy@...ux.ibm.com; mpe@...erman.id.au; npiggin@...il.com; christophe.leroy@...roup.eu; naveen@...nel.org; mwalle@...nel.org; xingyu.wu@...rfivetech.com; ziv.xu@...rfivetech.com; hayashi.kunihiko@...ionext.com; mhiramat@...nel.org; linux-watchdog@...r.kernel.org; linux-kernel@...r.kernel.org; linux-arm-kernel@...ts.infradead.org; chrome-platform@...ts.linux.dev; imx@...ts.linux.dev; linux-mips@...r.kernel.org; openbmc@...ts.ozlabs.org; linuxppc-dev@...ts.ozlabs.org; patches@...nsource.cirrus.com
Subject: Re: [PATCH v4 1/2] watchdog: Add a new flag WDIOF_STOP_MAYSLEEP
> Hi George,
>
> why is armada_37xx_wdt also here?
> The stop function in that driver may not sleep.
Marek,
Thanks for reviewing.
Since the stop function has a regmap_write(), I thought it might sleep.
Now that you pointed it out, I assume that it is an MMIO based regmap being used for armada.
I will update the same in the next version
>
> Marek
-George
Powered by blists - more mailing lists