From: Zev Weiss <zev@bewilderbeest.net>
To: Andrew Jeffery <andrew@aj.id.au>,
Conor Dooley <conor+dt@kernel.org>,
Guenter Roeck <linux@roeck-us.net>, Joel Stanley <joel@jms.id.au>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"Milton D. Miller II" <mdmii@outlook.com>,
Rob Herring <robh+dt@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org, openbmc@lists.ozlabs.org
Cc: "Eddie James" <eajames@linux.ibm.com>,
"Ivan Mikhaylov" <i.mikhaylov@yadro.com>,
"Thomas Weißschuh" <linux@weissschuh.net>
Subject: Re: [PATCH 0/2] watchdog: aspeed: Add aspeed,reset-mask property
Date: Fri, 27 Oct 2023 04:00:47 -0700 [thread overview]
Message-ID: <5db80b63-65da-407c-a019-048dea8c1a89@hatter.bewilderbeest.net> (raw)
In-Reply-To: <20230922104231.1434-4-zev@bewilderbeest.net>
On Fri, Sep 22, 2023 at 03:42:32AM PDT, Zev Weiss wrote:
>Hello,
>
>These patches add a new aspeed,reset-mask DT property for the Aspeed
>watchdog timer, which specifies exactly which peripherals should be
>reset by the watchdog timer.
>
>This series is a replacement for a patch I sent earlier [0], though
>using an entirely different (DT-based) approach and hence not exactly
>a v2.
>
>I've tested these patches on ast2500 hardware and a qemu ast2600
>model; test results on actual ast2600 hardware would be welcome.
>
>
>Thanks,
>Zev
>
>
>[0] https://lore.kernel.org/linux-watchdog/20230922013542.29136-2-zev@bewilderbeest.net/
>
>Zev Weiss (2):
> dt-bindings: watchdog: aspeed-wdt: Add aspeed,reset-mask property
> watchdog: aspeed: Add support for aspeed,reset-mask DT property
>
> .../bindings/watchdog/aspeed-wdt.txt | 18 +++-
> drivers/watchdog/aspeed_wdt.c | 11 +++
> include/dt-bindings/watchdog/aspeed-wdt.h | 92 +++++++++++++++++++
> 3 files changed, 120 insertions(+), 1 deletion(-)
> create mode 100644 include/dt-bindings/watchdog/aspeed-wdt.h
>
Ping...Guenter, if we stick with the simpler approach in this version of
the patches (which I'm fine with and seems to have passed muster with
Rob & Joel) does this look okay as is?
Thanks,
Zev
prev parent reply other threads:[~2023-10-27 11:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 10:42 [PATCH 0/2] watchdog: aspeed: Add aspeed,reset-mask property Zev Weiss
2023-09-22 10:42 ` [PATCH 1/2] dt-bindings: watchdog: aspeed-wdt: " Zev Weiss
2023-09-22 22:51 ` Rob Herring
2023-09-25 2:42 ` Andrew Jeffery
2023-09-26 0:04 ` Zev Weiss
2023-09-26 0:35 ` Guenter Roeck
2023-09-26 0:57 ` Andrew Jeffery
2023-09-22 10:42 ` [PATCH 2/2] watchdog: aspeed: Add support for aspeed,reset-mask DT property Zev Weiss
2023-10-11 9:26 ` Joel Stanley
2023-10-11 18:19 ` Zev Weiss
2023-10-27 11:00 ` Zev Weiss [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=5db80b63-65da-407c-a019-048dea8c1a89@hatter.bewilderbeest.net \
--to=zev@bewilderbeest.net \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=i.mikhaylov@yadro.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linux@weissschuh.net \
--cc=mdmii@outlook.com \
--cc=openbmc@lists.ozlabs.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).