From: narmstrong@baylibre.com (Neil Armstrong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] pwm: omap: Add PWM support using dual-mode timers
Date: Mon, 2 Nov 2015 12:14:08 +0100 [thread overview]
Message-ID: <56374580.2070704@baylibre.com> (raw)
This patch is based on an earlier patch by NeilBrown which is based on
a older patch from Grant Erickson which provided PWM devices using
the 'legacy' interface.
The pwm driver was renamed to not be confused with the OMAP4 PWM dedicated
hardware and was cleaned with the review from Thierry Reding.
The first patch introduces a way to select to dmtimer clock source via a
clocks binding and a dedicated function wit the legacy fallback.
In order to prepare for the future form of the dmtimer (clksource or whatever),
and less rely on specific bindings the first patch introduces the PWM driver
with all the dmtimer calls into a platform data structure.
The structure is then filled in plat-omap and added as auxdata for the
ti,pwm-dmtimer-omap compatible nodes.
Suggested-by: Tony Lindgren <tony@atomide.com>
RFC Thread : http://lkml.kernel.org/r/562505DB.3010402 at baylibre.com
Neil Armstrong (3):
arm: plat-omap: dmtimer: Add clock source from DT
pwm: Add PWM driver for OMAP using dual-mode timers
arm: plat-omap: Add PWM dmtimer platform data quirks
.../devicetree/bindings/pwm/pwm-omap-dmtimer.txt | 18 ++
arch/arm/mach-omap2/pdata-quirks.c | 23 ++
arch/arm/plat-omap/dmtimer.c | 31 +-
drivers/pwm/Kconfig | 9 +
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-omap-dmtimer.c | 322 +++++++++++++++++++++
include/linux/platform_data/pwm_omap_dmtimer.h | 69 +++++
7 files changed, 472 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-omap-dmtimer.txt
create mode 100644 drivers/pwm/pwm-omap-dmtimer.c
create mode 100644 include/linux/platform_data/pwm_omap_dmtimer.h
--
1.9.1
reply other threads:[~2015-11-02 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56374580.2070704@baylibre.com \
--to=narmstrong@baylibre.com \
--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).