From: Viresh Kumar <viresh.kumar@linaro.org>
To: Quentin Schulz <quentin.schulz@bootlin.com>
Cc: vireshk@kernel.org, shiraz.linux.kernel@gmail.com,
robh+dt@kernel.org, mark.rutland@arm.com,
mturquette@baylibre.com, sboyd@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
thomas.petazzoni@bootlin.com
Subject: Re: [PATCH 1/2] ARM: SPEAr600: add DT description of the watchdog
Date: Fri, 6 Apr 2018 13:26:48 +0530 [thread overview]
Message-ID: <20180406075648.GW3572@vireshk-i7> (raw)
In-Reply-To: <0635969b6ef0fe528a27a8b6493cc3df770e1f60.1523000725.git-series.quentin.schulz@bootlin.com>
On 06-04-18, 09:50, Quentin Schulz wrote:
> The SPEAr600 has a built-in watchdog which already has a DT binding
> described in Documentation/devicetree/bindings/watchdog/sp805-wdt.txt.
>
> Let's add the description of the watchdog device in the SPEAr600 Device
> Tree.
>
> Signed-off-by: Quentin Schulz <quentin.schulz@bootlin.com>
> ---
> arch/arm/boot/dts/spear600.dtsi | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/arm/boot/dts/spear600.dtsi b/arch/arm/boot/dts/spear600.dtsi
> index 00166eb..d7c3096 100644
> --- a/arch/arm/boot/dts/spear600.dtsi
> +++ b/arch/arm/boot/dts/spear600.dtsi
> @@ -213,6 +213,14 @@
> interrupts = <6>;
> status = "disabled";
> };
> +
> + wdt: wdt@fc880000 {
> + compatible = "arm,sp805", "arm,primecell";
> + reg = <0xfc880000 0x1000>;
> + interrupt-parent = <&vic1>;
> + interrupts = <20>;
> + status = "disabled";
> + };
> };
> };
> };
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2018-04-06 7:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 7:50 [PATCH 1/2] ARM: SPEAr600: add DT description of the watchdog Quentin Schulz
2018-04-06 7:50 ` [PATCH 2/2] clk: spear: fix WDT clock definition on SPEAr600 Quentin Schulz
2018-04-06 7:57 ` Viresh Kumar
2018-04-06 20:47 ` Stephen Boyd
2018-04-06 7:56 ` Viresh Kumar [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=20180406075648.GW3572@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=quentin.schulz@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=shiraz.linux.kernel@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vireshk@kernel.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).