All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Sven Peter <sven@svenpeter.dev>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Hector Martin <marcan@marcan.st>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-watchdog@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] watchdog: Add Apple SoC watchdog driver
Date: Sun, 14 Nov 2021 08:18:16 -0500	[thread overview]
Message-ID: <YZEMmH49D+GZEewi@sunset> (raw)
In-Reply-To: <95dea968-f452-4ba0-9b66-c9bc4269a52c@www.fastmail.com>

> >> + * This HW block has three separate watchdogs. WD0 resets the machine
> >> + * to recovery mode and is not very useful for us. WD1 and WD2 trigger a normal
> >> + * machine reset. WD0 additionally supports a configurable interrupt.
> >
> > Do we have any idea what the difference between WD1 and WD2 is?
> 
> I've never seen macOS write to WD2 when running in our hypervisor and only
> found that one when I was looking at the rest of the MMIO region.
> >From what I can tell it works exactly like WD1.

Makes sense, thanks.

WARNING: multiple messages have this Message-ID (diff)
From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Sven Peter <sven@svenpeter.dev>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Hector Martin <marcan@marcan.st>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Kettenis <mark.kettenis@xs4all.nl>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-watchdog@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] watchdog: Add Apple SoC watchdog driver
Date: Sun, 14 Nov 2021 08:18:16 -0500	[thread overview]
Message-ID: <YZEMmH49D+GZEewi@sunset> (raw)
In-Reply-To: <95dea968-f452-4ba0-9b66-c9bc4269a52c@www.fastmail.com>

> >> + * This HW block has three separate watchdogs. WD0 resets the machine
> >> + * to recovery mode and is not very useful for us. WD1 and WD2 trigger a normal
> >> + * machine reset. WD0 additionally supports a configurable interrupt.
> >
> > Do we have any idea what the difference between WD1 and WD2 is?
> 
> I've never seen macOS write to WD2 when running in our hypervisor and only
> found that one when I was looking at the rest of the MMIO region.
> >From what I can tell it works exactly like WD1.

Makes sense, thanks.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-11-14 13:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13  9:47 [PATCH 1/2] dt-bindings: watchdog: Add Apple Watchdog Sven Peter
2021-11-13  9:47 ` Sven Peter
2021-11-13  9:47 ` [PATCH 2/2] watchdog: Add Apple SoC watchdog driver Sven Peter
2021-11-13  9:47   ` Sven Peter
2021-11-13 11:14   ` Janne Grunau
2021-11-13 11:14     ` Janne Grunau
2021-11-13 11:19     ` Sven Peter
2021-11-13 11:19       ` Sven Peter
2021-11-13 15:24   ` Alyssa Rosenzweig
2021-11-13 15:24     ` Alyssa Rosenzweig
2021-11-14 11:37     ` Sven Peter
2021-11-14 11:37       ` Sven Peter
2021-11-14 13:18       ` Alyssa Rosenzweig [this message]
2021-11-14 13:18         ` Alyssa Rosenzweig
2021-12-02  5:14         ` Hector Martin
2021-12-02  5:14           ` Hector Martin
2021-12-02 11:05           ` Sven Peter
2021-12-02 11:05             ` Sven Peter
2021-11-14 12:42   ` Guenter Roeck
2021-11-14 12:42     ` Guenter Roeck
2021-11-14 13:25     ` Sven Peter
2021-11-14 13:25       ` Sven Peter
2021-11-13 21:07 ` [PATCH 1/2] dt-bindings: watchdog: Add Apple Watchdog Mark Kettenis
2021-11-13 21:07   ` Mark Kettenis
2021-11-14 11:40   ` Sven Peter
2021-11-14 11:40     ` Sven Peter
2021-11-14 11:58     ` Mark Kettenis
2021-11-14 11:58       ` Mark Kettenis
2021-11-29 21:23       ` Rob Herring
2021-11-29 21:23         ` Rob Herring
2021-11-29 21:24 ` Rob Herring
2021-11-29 21:24   ` Rob Herring

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=YZEMmH49D+GZEewi@sunset \
    --to=alyssa@rosenzweig.io \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marcan@marcan.st \
    --cc=mark.kettenis@xs4all.nl \
    --cc=robh+dt@kernel.org \
    --cc=sven@svenpeter.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.