From: benjamin.gaignard@linaro.org (Benjamin Gaignard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 5/8] IIO: add bindings for STM32 timer trigger driver
Date: Fri, 20 Jan 2017 10:15:06 +0100 [thread overview]
Message-ID: <1484903709-11650-6-git-send-email-benjamin.gaignard@st.com> (raw)
In-Reply-To: <1484903709-11650-1-git-send-email-benjamin.gaignard@st.com>
Define bindings for STM32 timer trigger
version 8:
- reword "reg" parameter description
version 4:
- remove triggers enumeration from DT
- add reg parameter
version 3:
- change file name
- add cross reference with mfd bindings
version 2:
- only keep one compatible
- add DT parameters to set lists of the triggers:
one list describe the triggers created by the device
another one give the triggers accepted by the device
Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
Acked-by: Jonathan Cameron <jic23@kernel.org>
Acked-by: Rob Herring <robh@kernel.org>
---
.../bindings/iio/timer/stm32-timer-trigger.txt | 23 ++++++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
diff --git a/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt b/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
new file mode 100644
index 0000000..55a653d
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/timer/stm32-timer-trigger.txt
@@ -0,0 +1,23 @@
+STMicroelectronics STM32 Timers IIO timer bindings
+
+Must be a sub-node of an STM32 Timers device tree node.
+See ../mfd/stm32-timers.txt for details about the parent node.
+
+Required parameters:
+- compatible: Must be "st,stm32-timer-trigger".
+- reg: Identify trigger hardware block.
+
+Example:
+ timers at 40010000 {
+ #address-cells = <1>;
+ #size-cells = <0>;
+ compatible = "st,stm32-timers";
+ reg = <0x40010000 0x400>;
+ clocks = <&rcc 0 160>;
+ clock-names = "clk_int";
+
+ timer at 0 {
+ compatible = "st,stm32-timer-trigger";
+ reg = <0>;
+ };
+ };
--
1.9.1
next prev parent reply other threads:[~2017-01-20 9:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 9:15 [PATCH v9 0/8] Add PWM and IIO timer drivers for STM32 Benjamin Gaignard
2017-01-20 9:15 ` [PATCH v9 1/8] MFD: add bindings for STM32 Timers driver Benjamin Gaignard
2017-01-20 9:15 ` [PATCH v9 2/8] MFD: add " Benjamin Gaignard
2017-01-20 9:15 ` [PATCH v9 3/8] dt-bindings: pwm: Add STM32 bindings Benjamin Gaignard
2017-01-20 9:15 ` [PATCH v9 4/8] pwm: add driver for STM32 plaftorm Benjamin Gaignard
2017-01-20 9:15 ` Benjamin Gaignard [this message]
2017-01-20 9:15 ` [PATCH v9 6/8] IIO: add STM32 timer trigger driver Benjamin Gaignard
2017-01-20 9:15 ` [PATCH v9 7/8] ARM: dts: stm32: add Timers driver for stm32f429 MCU Benjamin Gaignard
2017-01-20 10:04 ` Alexandre Torgue
2017-01-20 9:15 ` [PATCH v9 8/8] ARM: dts: stm32: Enable pwm1 and pwm3 for stm32f469-disco Benjamin Gaignard
2017-01-20 10:03 ` Alexandre Torgue
2017-01-23 12:12 ` [GIT PULL] Immutable branch between MFD, ARM, IIO and PWM due for the v4.10 merge window Lee Jones
2017-01-24 6:42 ` Olof Johansson
2017-01-24 8:12 ` Lee Jones
2017-01-24 19:54 ` Olof Johansson
2017-01-25 10:08 ` Lee Jones
2017-01-25 10:55 ` Thierry Reding
2017-01-25 15:33 ` Lee Jones
2017-01-25 18:23 ` Jonathan Cameron
2017-01-25 16:40 ` Lee Jones
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=1484903709-11650-6-git-send-email-benjamin.gaignard@st.com \
--to=benjamin.gaignard@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).