From: Fabrice Gasnier <fabrice.gasnier@st.com>
To: <thierry.reding@gmail.com>, <robh+dt@kernel.org>,
<alexandre.torgue@st.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
benjamin.gaignard@st.com, linux-pwm@vger.kernel.org,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
mcoquelin.stm32@gmail.com, fabrice.gasnier@st.com,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dt-bindings: pwm-stm32: add #pwm-cells
Date: Wed, 19 Jun 2019 11:52:01 +0200 [thread overview]
Message-ID: <1560937925-8990-2-git-send-email-fabrice.gasnier@st.com> (raw)
In-Reply-To: <1560937925-8990-1-git-send-email-fabrice.gasnier@st.com>
STM32 Timers support generic 3 cells PWM bindings to encode PWM number,
period and polarity as defined in pwm.txt.
Fixes: cd9a99c2f8e8 ("dt-bindings: pwm: Add STM32 bindings")
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
---
Documentation/devicetree/bindings/pwm/pwm-stm32.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-stm32.txt b/Documentation/devicetree/bindings/pwm/pwm-stm32.txt
index 3e6d550..a8690bf 100644
--- a/Documentation/devicetree/bindings/pwm/pwm-stm32.txt
+++ b/Documentation/devicetree/bindings/pwm/pwm-stm32.txt
@@ -8,6 +8,8 @@ Required parameters:
- pinctrl-names: Set to "default".
- pinctrl-0: List of phandles pointing to pin configuration nodes for PWM module.
For Pinctrl properties see ../pinctrl/pinctrl-bindings.txt
+- #pwm-cells: Should be set to 3. This PWM chip uses the default 3 cells
+ bindings defined in pwm.txt.
Optional parameters:
- st,breakinput: One or two <index level filter> to describe break input configurations.
@@ -28,6 +30,7 @@ Example:
pwm {
compatible = "st,stm32-pwm";
+ #pwm-cells = <3>;
pinctrl-0 = <&pwm1_pins>;
pinctrl-names = "default";
st,breakinput = <0 1 5>;
--
2.7.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-19 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 9:52 [PATCH 0/5] Add missing pwm-cells to STM32 timers PWM Fabrice Gasnier
2019-06-19 9:52 ` Fabrice Gasnier [this message]
2019-07-09 20:04 ` [PATCH 1/5] dt-bindings: pwm-stm32: add #pwm-cells Rob Herring
2019-06-19 9:52 ` [PATCH 2/5] pwm: stm32: use 3 cells ->of_xlate() Fabrice Gasnier
2019-06-19 11:42 ` Benjamin GAIGNARD
2019-06-19 9:52 ` [PATCH 3/5] ARM: dts: stm32: add pwm cells to stm32mp157c Fabrice Gasnier
2019-06-19 9:52 ` [PATCH 4/5] ARM: dts: stm32: add pwm cells to stm32f429 Fabrice Gasnier
2019-06-19 9:52 ` [PATCH 5/5] ARM: dts: stm32: add pwm cells to stm32f746 Fabrice Gasnier
2019-07-29 7:22 ` [PATCH 0/5] Add missing pwm-cells to STM32 timers PWM Alexandre Torgue
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=1560937925-8990-2-git-send-email-fabrice.gasnier@st.com \
--to=fabrice.gasnier@st.com \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
/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).