From: Rob Herring <robh@kernel.org>
To: Tero Kristo <t-kristo@ti.com>
Cc: wim@linux-watchdog.org, linux@roeck-us.net,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCHv4 1/4] dt-bindings: watchdog: Add support for TI K3 RTI watchdog
Date: Fri, 20 Mar 2020 16:59:35 -0600 [thread overview]
Message-ID: <20200320225935.GA30036@bogus> (raw)
In-Reply-To: <20200312095808.19907-2-t-kristo@ti.com>
On Thu, 12 Mar 2020 11:58:05 +0200, Tero Kristo wrote:
> TI K3 SoCs contain an RTI (Real Time Interrupt) module which can be
> used to implement a windowed watchdog functionality. Windowed watchdog
> will generate an error if it is petted outside the time window, either
> too early or too late.
>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
> v4:
> * changed license to dual
> * added documentation for missing properties
> * added ref to watchdog.yaml
> * renamed main_rti0 to watchdog0 in example
>
> .../bindings/watchdog/ti,rti-wdt.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/watchdog/ti,rti-wdt.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-03-20 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 9:58 [PATCHv4 0/4] watchdog: add K3 RTI watchdog support Tero Kristo
2020-03-12 9:58 ` [PATCHv4 1/4] dt-bindings: watchdog: Add support for TI K3 RTI watchdog Tero Kristo
2020-03-20 22:59 ` Rob Herring [this message]
2020-06-18 16:09 ` Jan Kiszka
2020-06-22 6:45 ` Tero Kristo
2020-03-12 9:58 ` [PATCHv4 2/4] watchdog: reset last_hw_keepalive time at start Tero Kristo
2020-03-12 9:58 ` [PATCHv4 3/4] watchdog: Add K3 RTI watchdog support Tero Kristo
2020-03-12 9:58 ` [PATCHv4 4/4] arm64: dts: ti: k3-j721e-main: Add MAIN domain watchdog entries Tero Kristo
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=20200320225935.GA30036@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=t-kristo@ti.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 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.