From: Rob Herring <robh@kernel.org>
To: Evan Benn <evanbenn@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
jwerner@chromium.org, xingyu.chen@amlogic.com,
Evan Benn <evanbenn@chromium.org>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
devicetree@vger.kernel.org, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: watchdog: Add ARM smc wdt for mt8173 watchdog
Date: Tue, 5 May 2020 14:09:58 -0500 [thread overview]
Message-ID: <20200505190958.GA22997@bogus> (raw)
In-Reply-To: <20200505131242.v6.1.Id96574f1f52479d7a2f3b866b8a0552ab8c03d7f@changeid>
On Tue, 5 May 2020 13:13:30 +1000, Evan Benn wrote:
> This watchdog can be used on ARM systems with a Secure
> Monitor firmware to forward watchdog operations to
> firmware via a Secure Monitor Call.
>
> Signed-off-by: Evan Benn <evanbenn@chromium.org>
>
> ---
>
> Changes in v6:
> - Don't use dt default
>
> Changes in v5:
> - Change compatible to arm,smc-wdt
>
> Changes in v4:
> - Add arm,smc-id property
>
> Changes in v3:
> - Change name back to arm
>
> Changes in v2:
> - Change name arm > mt8173
>
> .../bindings/watchdog/arm-smc-wdt.yaml | 37 +++++++++++++++++++
> MAINTAINERS | 6 +++
> 2 files changed, 43 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/arm-smc-wdt.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-05-05 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 3:13 [PATCH v6 0/2] Add a watchdog driver that uses ARM Secure Monitor Calls Evan Benn
2020-05-05 3:13 ` [PATCH v6 1/2] dt-bindings: watchdog: Add ARM smc wdt for mt8173 watchdog Evan Benn
2020-05-05 19:09 ` Rob Herring [this message]
2020-05-06 13:45 ` Guenter Roeck
2020-05-05 3:13 ` [PATCH v6 2/2] watchdog: Add new arm_smc_wdt watchdog driver Evan Benn
2020-05-05 20:09 ` Julius Werner
2020-05-06 6:21 ` Xingyu Chen
2020-05-06 13:46 ` Guenter Roeck
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=20200505190958.GA22997@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=evanbenn@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mchehab+huawei@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=xingyu.chen@amlogic.com \
/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 NNTP newsgroup(s).