From: Pavan Kondeti <quic_pkondeti@quicinc.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Pavankumar Kondeti <quic_pkondeti@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
<linux-arm-msm@vger.kernel.org>, <linux-watchdog@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Mukesh Ojha <quic_mojha@quicinc.com>
Subject: Re: [PATCH] watchdog: qcom: Start the watchdog in probe
Date: Wed, 31 Jan 2024 11:46:44 +0530 [thread overview]
Message-ID: <cfaaed23-8f59-4447-af0b-b94b35ce68ba@quicinc.com> (raw)
In-Reply-To: <1a996038-bcc7-4c0f-8f27-ca36a2eb9d3d@roeck-us.net>
On Tue, Jan 30, 2024 at 10:01:15PM -0800, Guenter Roeck wrote:
> On 1/30/24 20:15, Pavankumar Kondeti wrote:
> > When CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED is enabled, kernel can pet the
> > watchdog until user space takes over. Make use of this feature and
> > start the watchdog in probe.
> >
> > Signed-off-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
> > ---
> > drivers/watchdog/qcom-wdt.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/watchdog/qcom-wdt.c b/drivers/watchdog/qcom-wdt.c
> > index 9e790f0c2096..4fb5dbf5faee 100644
> > --- a/drivers/watchdog/qcom-wdt.c
> > +++ b/drivers/watchdog/qcom-wdt.c
> > @@ -276,12 +276,16 @@ static int qcom_wdt_probe(struct platform_device *pdev)
> > watchdog_init_timeout(&wdt->wdd, 0, dev);
> > /*
> > + * Kernel can pet the watchdog until user space takes over.
> > + * Start the watchdog here to make use of this feature.
> > +
>
> No, that is not what CONFIG_WATCHDOG_HANDLE_BOOT_ENABLED is about.
> Please see its description.
>
> NACK.
>
Thanks for taking a look Guenter. I thought of using
WATCHDOG_HANDLE_BOOT_ENABLED and infiniite open timeout as a hint to start
the watchdog in probe. After seeing your NACK for this patch, I guess
that would also would have been rejected.
Do you think we can revive this [1] to add support for watchdog pet from
the kernel? It would be helpful in cases where the user space has no
support for watchdog pet (say minimal ramdisk).
[1]
https://lore.kernel.org/linux-watchdog/20210924133509.3454834-1-f.suligoi@asem.it/#t
next prev parent reply other threads:[~2024-01-31 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 4:15 Pavankumar Kondeti
2024-01-31 6:01 ` Guenter Roeck
2024-01-31 6:16 ` Pavan Kondeti [this message]
2024-01-31 6:37 ` Guenter Roeck
2024-01-31 6:51 ` Pavan Kondeti
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=cfaaed23-8f59-4447-af0b-b94b35ce68ba@quicinc.com \
--to=quic_pkondeti@quicinc.com \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=quic_mojha@quicinc.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
all inboxes | Powered by JetHome®