From: Sander Vanheule <sander@svanheule.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] watchdog: Add Realtek Otto watchdog timer
Date: Thu, 18 Nov 2021 18:15:41 +0100 [thread overview]
Message-ID: <e311fa3e7a187ca32920534310b0a0cbd3b6526f.camel@svanheule.net> (raw)
In-Reply-To: <62050743-bc11-cc21-c6ae-0be9d7b5633c@roeck-us.net>
Hi Guenter,
On Wed, 2021-11-17 at 04:42 -0800, Guenter Roeck wrote:
> On 11/16/21 11:13 PM, Sander Vanheule wrote:
> > Hi Guenter,
> >
> > On Tue, 2021-11-16 at 21:20 -0800, Guenter Roeck wrote:
> > > On Thu, Nov 04, 2021 at 10:32:13AM +0100, Sander Vanheule wrote:
> > > > Realtek MIPS SoCs (platform name Otto) have a watchdog timer with
> > > > pretimeout notifitication support. The WDT can (partially) hard reset,
> > > > or soft reset the SoC.
> > > >
> > > > This driver implements all features as described in the devicetree
> > > > binding, except the phase2 interrupt, and also functions as a restart
> > > > handler. The cpu reset mode is considered to be a "warm" restart, since
> > > > this mode does not reset all peripherals. Being an embedded system
> > > > though, the "cpu" and "software" modes will still cause the bootloader
> > > > to run on restart.
> > > >
> > > > It is not known how a forced system reset can be disabled on the
> > > > supported platforms. This means that the phase2 interrupt will only fire
> > > > at the same time as reset, so implementing phase2 is of little use.
> > > >
> > > > Signed-off-by: Sander Vanheule <sander@svanheule.net>
> > >
> > > Reviewed-by: Guenter Roeck <linux@roeck-us.net>
> >
> > Thank you for the review! In the meantime, I was preparing a v4 of this series with some
> > small changes (see inline below). Could you let me know if I can keep your Reviewed-by
> > with those changes?
> >
>
> I think it would be better to re-review it.
I sent out the v4 a bit later than expected, because I hit a regression for the irqchip on
this platform:
https://lore.kernel.org/all/bbe5506a2458b2d6049bd22a5fda77ae6175ddec.camel@svanheule.net/
Best,
Sander
prev parent reply other threads:[~2021-11-18 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 9:32 [PATCH v3 0/2] Add Realtek Otto WDT support Sander Vanheule
2021-11-04 9:32 ` [PATCH v3 1/2] dt-bindings: watchdog: Realtek Otto WDT binding Sander Vanheule
2021-11-17 5:21 ` Guenter Roeck
2021-11-04 9:32 ` [PATCH v3 2/2] watchdog: Add Realtek Otto watchdog timer Sander Vanheule
2021-11-17 5:20 ` Guenter Roeck
2021-11-17 7:13 ` Sander Vanheule
2021-11-17 12:42 ` Guenter Roeck
2021-11-17 12:59 ` Sander Vanheule
2021-11-18 17:15 ` Sander Vanheule [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=e311fa3e7a187ca32920534310b0a0cbd3b6526f.camel@svanheule.net \
--to=sander@svanheule.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--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®