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>
Subject: Re: [PATCH v3 0/5] pwm: omap-dmtimer: Allow for dynamic pwm period updates
Date: Mon, 23 Mar 2020 17:00:13 +0530 [thread overview]
Message-ID: <09dac13d-44b0-80c6-fdbb-54bfc6f48e36@ti.com> (raw)
In-Reply-To: <20200312042210.17344-1-lokeshvutla@ti.com>
Hi All,
On 12/03/20 9:52 AM, Lokesh Vutla wrote:
> 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
Gentle ping on this series :) The above dependencies are merged into timer tree
and below is the immutable branch:
https://git.linaro.org/people/dlezcano/linux.git/log/?h=timers/drivers/timer-ti-dm
Thanks and regards,
Lokesh
next prev parent reply other threads:[~2020-03-23 11:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 4:22 [PATCH v3 0/5] pwm: omap-dmtimer: Allow for dynamic pwm period updates Lokesh Vutla
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 ` Lokesh Vutla [this message]
2020-03-30 14:04 ` [PATCH v3 0/5] pwm: omap-dmtimer: Allow for dynamic pwm period updates 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=09dac13d-44b0-80c6-fdbb-54bfc6f48e36@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).