From: Randy Dunlap <rdunlap@infradead.org>
To: Bharat Bhushan <bbhushan2@marvell.com>,
wim@linux-watchdog.org, linux@roeck-us.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, sgoutham@marvell.com
Subject: Re: [PATCH 2/2 v10] Watchdog: Add marvell GTI watchdog driver
Date: Mon, 31 Jul 2023 21:54:04 -0700 [thread overview]
Message-ID: <ec7616b0-706a-faa9-fc0b-ce6ae746137b@infradead.org> (raw)
In-Reply-To: <20230801044623.9275-2-bbhushan2@marvell.com>
On 7/31/23 21:46, Bharat Bhushan wrote:
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index ee97d89dfc11..87ac222b436e 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -1797,6 +1797,19 @@ config OCTEON_WDT
> from the first interrupt, it is then only poked when the
> device is written.
>
> +config MARVELL_GTI_WDT
> + tristate "Marvell GTI Watchdog driver"
> + depends on ARCH_THUNDER || (COMPILE_TEST && 64BIT)
> + default y
> + select WATCHDOG_CORE
> + help
> + Marvell GTI hardware supports watchdog timer. First timeout
> + works as watchdog pretimeout and installed interrupt handler
> + will be called on first timeout. Hardware can generate interrupt
> + to SCP on second timeout but it is not enabled, So second
enabled, so second
> + timeout is ignored. If device poke does not happen then system
> + will reboot on third timeout.
All Kconfig help text should be indented with one tab + 2 spaces
according to coding-style.rst.
--
~Randy
prev parent reply other threads:[~2023-08-01 4:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 4:46 [PATCH 1/2 v10] dt-bindings: watchdog: marvell GTI system watchdog driver Bharat Bhushan
2023-08-01 4:46 ` [PATCH 2/2 v10] Watchdog: Add marvell GTI " Bharat Bhushan
2023-08-01 4:54 ` Randy Dunlap [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=ec7616b0-706a-faa9-fc0b-ce6ae746137b@infradead.org \
--to=rdunlap@infradead.org \
--cc=bbhushan2@marvell.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=sgoutham@marvell.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 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).