From: Harini Katakam <harinik@xilinx.com>
To: wim@iguana.be, grant.likely@linaro.org, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
rob@landley.net
Cc: michals@xilinx.com, linux-watchdog@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, harinikatakamlinux@gmail.com,
harini.katakam@xilinx.com, Harini Katakam <harinik@xilinx.com>
Subject: [PATCH v3 2/2] devicetree: Add Cadence WDT devicetree bindings documentation
Date: Mon, 14 Jul 2014 17:46:09 +0530 [thread overview]
Message-ID: <1405340169-2820-2-git-send-email-harinik@xilinx.com> (raw)
In-Reply-To: <1405340169-2820-1-git-send-email-harinik@xilinx.com>
Add cadence-wdt bindings documentation.
Signed-off-by: Harini Katakam <harinik@xilinx.com>
---
v3 changes:
- Change reset property type and improve description.
- Improve description of clocks and interrupts.
- Use watchdog@ in the example.
- Use only cdns compatible string for now.
v2:
No changes
---
.../devicetree/bindings/watchdog/cadence-wdt.txt | 27 ++++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/cadence-wdt.txt
diff --git a/Documentation/devicetree/bindings/watchdog/cadence-wdt.txt b/Documentation/devicetree/bindings/watchdog/cadence-wdt.txt
new file mode 100644
index 0000000..ab23e38
--- /dev/null
+++ b/Documentation/devicetree/bindings/watchdog/cadence-wdt.txt
@@ -0,0 +1,27 @@
+Zynq Watchdog Device Tree Bindings
+-------------------------------------------
+
+Required properties:
+- compatible : Should be "cdns,wdt-r1p2".
+- clocks : Input clock specifier. This should be the ref clk.
+- reg : Physical base address and size of WDT registers map.
+- interrupts : Property with a value describing the interrupt
+ number. This interrupt is used for indication
+ when the watchdog times out.
+- interrupt-parent : Must be core interrupt controller.
+
+Optional properties
+- reset : If this property exists, then a reset is done
+ when watchdog times out.
+- timeout-sec : Watchdog timeout value (in seconds).
+
+Example:
+ watchdog@f8005000 {
+ compatible = "xlnx,zynq-wdt-r1p2";
+ clocks = <&clkc 45>;
+ interrupt-parent = <&intc>;
+ interrupts = <0 9 1>;
+ reg = <0xf8005000 0x1000>;
+ reset;
+ timeout-sec = <10>;
+ };
--
1.7.9.5
next prev parent reply other threads:[~2014-07-14 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 12:16 [PATCH v3 1/2] watchdog: Add Cadence WDT driver Harini Katakam
2014-07-14 12:16 ` Harini Katakam [this message]
2014-07-14 13:35 ` [PATCH v3 2/2] devicetree: Add Cadence WDT devicetree bindings documentation Michal Simek
2014-07-14 15:07 ` Mark Rutland
2014-07-15 6:39 ` Harini Katakam
2014-07-15 8:59 ` Mark Rutland
2014-07-15 9:04 ` Harini Katakam
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=1405340169-2820-2-git-send-email-harinik@xilinx.com \
--to=harinik@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=harini.katakam@xilinx.com \
--cc=harinikatakamlinux@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michals@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=wim@iguana.be \
/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).