From: Lokesh Vutla <lokeshvutla@ti.com>
To: "Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Tony Lindgren <tony@atomide.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-pwm@vger.kernel.org>,
Sekhar Nori <nsekhar@ti.com>, Vignesh R <vigneshr@ti.com>,
Lokesh Vutla <lokeshvutla@ti.com>
Subject: [PATCH v3 0/5] pwm: omap-dmtimer: Allow for dynamic pwm period updates
Date: Thu, 12 Mar 2020 09:52:05 +0530 [thread overview]
Message-ID: <20200312042210.17344-1-lokeshvutla@ti.com> (raw)
This series fixes minor issues in config callback and allows for on the
fly updates for pwm period and duty cycle. This is mainly intended to
allow pwm omap dmtimer to be used for generating a 1PPS signal that can be
syncronized to PTP clock in CPTS module available in AM335x and AM57xx SoCs.
Series depends on the following series:
- https://patchwork.kernel.org/patch/11379875/
- https://patchwork.kernel.org/project/linux-omap/list/?series=251691
Full dependencies can be seen here:
https://github.com/lokeshvutla/linux/tree/devel/pwm-dynamic-period-updates-v3
Changes since v2:
- Restored the existing behavior on pwm stop. PWM stops immediately when
.stop is called as timer counter stops immediately. If just the
autoreload is disabled as in v2, there is a possibility that pwm is
never stopped.
- Added the above limitation in the driver description
- Rebased on top of v5.6-rc5
Changes since v1:
- Updated commit description in PATCH 1
- Added a brief about PWM generation using OMAP DM timer.
- Updated the pwm stop callback to allow for completing the current pwm
cycle.
- Added the limitaitons of hardware.
- Used hw status instead of relying on pwm framework for state update.
Lokesh Vutla (5):
pwm: omap-dmtimer: Drop unused header file
pwm: omap-dmtimer: Update description for pwm omap dm timer
pwm: omap-dmtimer: Fix pwm enabling sequence
pwm: omap-dmtimer: Do not disable pwm before changing
period/duty_cycle
pwm: omap-dmtimer: Implement .apply callback
drivers/pwm/pwm-omap-dmtimer.c | 219 ++++++++++++------
include/clocksource/timer-ti-dm.h | 3 +-
.../linux/platform_data/pwm_omap_dmtimer.h | 90 -------
3 files changed, 149 insertions(+), 163 deletions(-)
delete mode 100644 include/linux/platform_data/pwm_omap_dmtimer.h
--
2.23.0
next reply other threads:[~2020-03-12 4:23 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 4:22 Lokesh Vutla [this message]
2020-03-12 4:22 ` [PATCH v3 1/5] pwm: omap-dmtimer: Drop unused header file Lokesh Vutla
2020-03-12 6:35 ` Uwe Kleine-König
2020-03-12 4:22 ` [PATCH v3 2/5] pwm: omap-dmtimer: Update description for pwm omap dm timer Lokesh Vutla
2020-03-12 6:35 ` Uwe Kleine-König
2020-03-12 4:22 ` [PATCH v3 3/5] pwm: omap-dmtimer: Fix pwm enabling sequence Lokesh Vutla
2020-03-12 4:22 ` [PATCH v3 4/5] pwm: omap-dmtimer: Do not disable pwm before changing period/duty_cycle Lokesh Vutla
2020-03-12 6:40 ` Uwe Kleine-König
2020-03-12 8:05 ` Lokesh Vutla
2020-03-12 8:47 ` Uwe Kleine-König
2020-03-12 10:44 ` Lokesh Vutla
2020-03-12 14:21 ` Richard Cochran
2020-03-12 17:14 ` Lokesh Vutla
2020-03-18 4:40 ` Lokesh Vutla
2020-03-30 14:14 ` Thierry Reding
2020-03-30 19:16 ` Uwe Kleine-König
2020-03-31 20:45 ` Thierry Reding
2020-04-01 8:22 ` Uwe Kleine-König
2020-04-01 10:22 ` Lokesh Vutla
2020-04-01 11:47 ` Uwe Kleine-König
2020-04-01 18:39 ` Thierry Reding
2020-04-01 20:36 ` Uwe Kleine-König
2020-04-01 18:28 ` Thierry Reding
2020-04-01 20:31 ` Uwe Kleine-König
2020-04-01 21:37 ` Thierry Reding
2020-04-02 14:02 ` Uwe Kleine-König
2020-04-03 8:51 ` Lokesh Vutla
2020-04-03 13:59 ` Uwe Kleine-König
2020-03-31 15:29 ` Lokesh Vutla
2020-03-31 20:10 ` Thierry Reding
2020-04-01 10:15 ` Lokesh Vutla
2020-03-12 4:22 ` [PATCH v3 5/5] pwm: omap-dmtimer: Implement .apply callback Lokesh Vutla
2020-03-13 15:31 ` Tony Lindgren
2020-03-23 11:30 ` [PATCH v3 0/5] pwm: omap-dmtimer: Allow for dynamic pwm period updates Lokesh Vutla
2020-03-30 14:04 ` Thierry Reding
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=20200312042210.17344-1-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=vigneshr@ti.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).