From: Tero Kristo <t-kristo@ti.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: <wim@linux-watchdog.org>, <linux-watchdog@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv3 3/4] watchdog: Add K3 RTI watchdog support
Date: Wed, 1 Apr 2020 20:01:53 +0300 [thread overview]
Message-ID: <7e15714e-efed-56ae-7ca7-fbfac031326c@ti.com> (raw)
In-Reply-To: <422f7335-9774-9ec1-6b0f-f22f811746cf@roeck-us.net>
On 01/04/2020 18:55, Guenter Roeck wrote:
> On 4/1/20 5:44 AM, Tero Kristo wrote:
>> On 05/03/2020 00:06, Guenter Roeck wrote:
>>> On Wed, Mar 04, 2020 at 12:42:14PM +0200, Tero Kristo wrote:
>>>> Texas Instruments K3 SoCs contain an RTI (Real Time Interrupt) module
>>>> which can be used as a watchdog. This IP provides a support for
>>>> windowed watchdog mode, in which the watchdog must be petted within
>>>> a certain time window. If it is petted either too soon, or too late,
>>>> a watchdog error will be triggered.
>>>>
>>>> Signed-off-by: Tero Kristo <t-kristo@ti.com>
>>>
>>> Reviewed-by: Guenter Roeck <linux@roeck-us.net>
>>
>> Whats the plan for merging this one + the DT binding doc? I can't see this in linux-next yet at least, I do see the watchdog core change from this series though.
>>
>
> It is in my watchdog-next branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git.
>
> Wim usually picks it up from there.
>
> The core patch didn't depend on DT approval, so I (and Wim) picked it up
> earlier.
Ok thanks for clarification, I thought there was something like that
going in the background but decided to double check.
-Tero
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next prev parent reply other threads:[~2020-04-01 17:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 20:04 [PATCHv2 0/4] watchdog: add TI K3 SoC " Tero Kristo
2020-03-02 20:04 ` [PATCHv2 1/4] dt-bindings: watchdog: Add support for TI K3 RTI watchdog Tero Kristo
2020-03-10 19:37 ` Rob Herring
2020-03-11 7:48 ` Tero Kristo
2020-03-02 20:04 ` [PATCHv2 2/4] watchdog: reset last_hw_keepalive time at start Tero Kristo
2020-03-03 21:12 ` Guenter Roeck
2020-03-02 20:04 ` [PATCHv2 3/4] watchdog: Add K3 RTI watchdog support Tero Kristo
2020-03-03 21:18 ` Guenter Roeck
2020-03-04 6:57 ` Tero Kristo
2020-03-04 9:23 ` Guenter Roeck
2020-03-04 10:42 ` [PATCHv3 " Tero Kristo
2020-03-04 22:06 ` Guenter Roeck
2020-04-01 12:44 ` Tero Kristo
2020-04-01 15:55 ` Guenter Roeck
2020-04-01 17:01 ` Tero Kristo [this message]
2020-03-04 10:44 ` [PATCHv2 " Tero Kristo
2020-03-02 20:04 ` [PATCHv2 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=7e15714e-efed-56ae-7ca7-fbfac031326c@ti.com \
--to=t-kristo@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--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®