From: Guenter Roeck <linux@roeck-us.net>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: wim@linux-watchdog.org, robh+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-watchdog@vger.kernel.org,
devicetree@vger.kernel.org, andy.gross@linaro.org
Subject: Re: [v3,3/3] arm64: dts: qcom: pm8916: Add PON watchdog node
Date: Sat, 15 Dec 2018 08:27:16 -0800 [thread overview]
Message-ID: <20181215162716.GA18695@roeck-us.net> (raw)
In-Reply-To: <1542962678-13697-3-git-send-email-loic.poulain@linaro.org>
On Fri, Nov 23, 2018 at 09:44:38AM +0100, Loic Poulain wrote:
> Add watchdog child node to the PM8916 PON device.
>
> Signed-off-by: Loic Poulain <loic.poulain@linaro.org>
Acked-by: Guenter Roeck <linux@roeck-us.net>
... with the assumption that this patch will be pushed through
an arm tree.
Guenter
> ---
> v2: Add interrupts and timeout-sec props
> v3: no change
>
> arch/arm64/boot/dts/qcom/pm8916.dtsi | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/pm8916.dtsi b/arch/arm64/boot/dts/qcom/pm8916.dtsi
> index a05ebaf..3230b88 100644
> --- a/arch/arm64/boot/dts/qcom/pm8916.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pm8916.dtsi
> @@ -32,6 +32,12 @@
> bias-pull-up;
> linux,code = <KEY_POWER>;
> };
> +
> + watchdog {
> + compatible = "qcom,pm8916-wdt";
> + interrupts = <0x0 0x8 6 IRQ_TYPE_EDGE_RISING>;
> + timeout-sec = <60>;
> + };
> };
>
> pm8916_gpios: gpios@c000 {
next prev parent reply other threads:[~2018-12-15 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 8:44 [PATCH v3 1/3] watchdog: Add pm8916 watchdog driver Loic Poulain
2018-11-23 8:44 ` [PATCH v3 2/3] dt-bindings: watchdog: Add Qualcomm PM8916 watchdog Loic Poulain
2018-11-27 1:49 ` Rob Herring
2018-12-15 16:26 ` [v3,2/3] " Guenter Roeck
2018-11-23 8:44 ` [PATCH v3 3/3] arm64: dts: qcom: pm8916: Add PON watchdog node Loic Poulain
2018-12-15 16:27 ` Guenter Roeck [this message]
2018-11-23 16:36 ` [PATCH v3 1/3] watchdog: Add pm8916 watchdog driver 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=20181215162716.GA18695@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andy.gross@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=loic.poulain@linaro.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 NNTP newsgroup(s).