From: <Claudiu.Beznea@microchip.com>
To: <thierry.reding@gmail.com>, <corbet@lwn.net>,
<Nicolas.Ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <robh@kernel.org>
Cc: <linux-pwm@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<Claudiu.Beznea@microchip.com>
Subject: [PATCH v6 2/6] pwm: add PWM modes
Date: Mon, 17 Dec 2018 14:03:18 +0000 [thread overview]
Message-ID: <1545055368-23338-3-git-send-email-claudiu.beznea@microchip.com> (raw)
In-Reply-To: <1545055368-23338-1-git-send-email-claudiu.beznea@microchip.com>
From: Claudiu Beznea <claudiu.beznea@microchip.com>
Add PWM normal and complementary modes.
Signed-off-by: Claudiu Beznea <claudiu.beznea@microchip.com>
---
Hi Rob,
In prevous version I had your Acked-by tag on this patch but I removed it
in this version since there are some changes b/w the previous one and this
one. Please see bellow and let me know if you are ok with this.
Thank you,
Claudiu Beznea
Changes in v6:
- remove DT bindings since they were also removed from code
- use 1/3 duty factor ratio
- use '^' symbols to emphasize the beginning of a new period
- use PWMx_y to refrer to output y of PWM x
Documentation/pwm.txt | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt
index 8fbf0aa3ba2d..669fd4c9cc8e 100644
--- a/Documentation/pwm.txt
+++ b/Documentation/pwm.txt
@@ -110,6 +110,28 @@ channel that was exported. The following properties will then be available:
- 0 - disabled
- 1 - enabled
+ mode
+ Get/set PWM channel working mode.
+
+ In the following description PWMx_y refers to output y of PWM with ID x.
+
+ Normal mode - for PWM channels with one output; this should be the
+ default working mode for every PWM channel; output waveforms looks
+ like this:
+ __ __ __ __
+ PWMx __| |____| |____| |____| |__
+ ^ ^ ^ ^
+
+ Complementary mode - for PWM channels with two outputs; output waveforms
+ looks line this:
+ __ __ __ __
+ PWMx_0 __| |____| |____| |____| |__
+ __ ____ ____ ____ __
+ PWMx_1 |__| |__| |__| |__|
+ ^ ^ ^ ^
+
+ Where '^' specifies the beginning of a period.
+
Implementing a PWM driver
-------------------------
--
2.7.4
next prev parent reply other threads:[~2018-12-17 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:03 [PATCH v6 0/9] extend PWM framework to support PWM modes Claudiu.Beznea
2018-12-17 14:03 ` [PATCH v6 1/6] pwm: extend PWM framework with " Claudiu.Beznea
2018-12-17 14:03 ` Claudiu.Beznea [this message]
2018-12-17 14:03 ` [PATCH v6 3/6] pwm: atmel: add pwm capabilities Claudiu.Beznea
2018-12-17 14:03 ` [PATCH v6 4/6] pwm: add push-pull mode support Claudiu.Beznea
2018-12-17 14:03 ` [PATCH v6 5/6] pwm: add documentation for pwm push-pull mode Claudiu.Beznea
2018-12-17 14:03 ` [PATCH v6 6/6] pwm: atmel: add push-pull mode support Claudiu.Beznea
2018-12-17 14:06 ` [PATCH v6 0/9] extend PWM framework to support PWM modes Claudiu.Beznea
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=1545055368-23338-3-git-send-email-claudiu.beznea@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@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).