From: Yannick Fertre <yannick.fertre@st.com>
To: Wim Van Sebroeck <wim@iguana.be>,
Guenter Roeck <linux@roeck-us.net>,
Rob Herring <robh+dt@kernel.org>,
Alexandre TORGUE <alexandre.torgue@st.com>,
Benjamin Gaignard <benjamin.gaignard@st.com>,
Yannick Fertre <yannick.fertre@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-watchdog@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Philippe Cornu <philippe.cornu@st.com>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v3 1/5] dt-bindings: Document STM32 IWDG bindings
Date: Wed, 22 Mar 2017 16:04:39 +0100 [thread overview]
Message-ID: <1490195083-25117-2-git-send-email-yannick.fertre@st.com> (raw)
In-Reply-To: <1490195083-25117-1-git-send-email-yannick.fertre@st.com>
From: Yannick Fertre <yfertre.stm32@gmail.com>
This adds documentation of device tree bindings for the STM32 IWDG
(Independent WatchDoG).
Change-Id: Idadacc806d00205fe9af2e8606af229b4b760558
Signed-off-by: Yannick Fertre <yannick.fertre@st.com>
---
.../devicetree/bindings/watchdog/st,stm32-iwdg.txt | 15 +++++++++++++++
1 file changed, 15 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt
diff --git a/Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt b/Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt
new file mode 100644
index 0000000..036b040
--- /dev/null
+++ b/Documentation/devicetree/bindings/watchdog/st,stm32-iwdg.txt
@@ -0,0 +1,15 @@
+STM32 Independent WatchDoG (IWDG)
+---------------------------------
+
+Required properties:
+- compatible: "st,stm32-iwdg"
+- reg: physical base address and length of the registers set for the device
+- clocks: must contain a single entry describing the clock input
+
+Example:
+
+iwdg@40003000 {
+ compatible = "st,stm32-iwdg";
+ reg = <0x40003000 0x400>;
+ clocks = <&clk_lsi>;
+};
--
1.9.1
next prev parent reply other threads:[~2017-03-22 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 15:04 [PATCH v3 0/5] STM32 Independant watchdog Yannick Fertre
2017-03-22 15:04 ` Yannick Fertre [this message]
2017-03-29 1:40 ` [PATCH v3 1/5] dt-bindings: Document STM32 IWDG bindings Rob Herring
2017-03-29 3:15 ` Guenter Roeck
2017-03-22 15:04 ` [PATCH v3 2/5] drivers: watchdog: Add STM32 IWDG driver Yannick Fertre
2017-03-29 3:15 ` Guenter Roeck
2017-03-30 15:10 ` Yannick FERTRE
2017-03-22 15:04 ` [PATCH v3 3/5] ARM: dts: stm32: Add watchdog support for STM32F429 SoC Yannick Fertre
2017-03-22 15:04 ` [PATCH v3 4/5] ARM: dts: stm32: Add watchdog support for STM32F429 eval board Yannick Fertre
2017-03-22 15:04 ` [PATCH v3 5/5] ARM: configs: Add watchdog support in STM32 defconfig Yannick Fertre
2017-03-23 17:28 ` Alexandre Torgue
2017-03-29 3:00 ` [PATCH v3 0/5] STM32 Independant watchdog 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=1490195083-25117-2-git-send-email-yannick.fertre@st.com \
--to=yannick.fertre@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcoquelin.stm32@gmail.com \
--cc=philippe.cornu@st.com \
--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).