From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] pwm: Changes for v4.12-rc1
Date: Tue, 9 May 2017 17:59:11 +0200 [thread overview]
Message-ID: <20170509155911.31267-1-thierry.reding@gmail.com> (raw)
Hi Linus,
The following changes since commit c1ae3cfa0e89fa1a7ecc4c99031f5e9ae99d9201:
Linux 4.11-rc1 (2017-03-05 12:59:56 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git tags/pwm/for-4.12-rc1
for you to fetch changes up to 97512ceafaacf8cdb96d6a36ae55e8335c0a9e55:
Merge branch 'for-4.12/drivers' into for-next (2017-04-13 17:41:50 +0200)
Thanks,
Thierry
----------------------------------------------------------------
pwm: Changes for v4.12-rc1
Adds a new driver for the PWM controller found on MediaTek SoCs and
extends support for the Atmel PWM controller to include the SAMA5D2.
Some existing drivers have been migrated to the atomic API and a few
others see miscellaneous improvements.
----------------------------------------------------------------
Andy Shevchenko (1):
pwm: lpss: Split Tangier configuration
Boris Brezillon (2):
pwm: atmel-hlcdc: Convert to the atomic PWM API
pwm: atmel-hlcdc: Implement the suspend/resume hooks
Claudiu Beznea (2):
pwm: atmel: Switch to atomic PWM
pwm: atmel: Enable PWM on sama5d2
David Wu (1):
pwm: rockchip: State of PWM clock should synchronize with PWM enabled state
Hans de Goede (1):
pwm: lpss: Set enable-bit before waiting for update-bit to go low
John Crispin (2):
dt-bindings: pwm: Add MediaTek PWM bindings
pwm: Add MediaTek PWM support
Laxman Dewangan (5):
pwm: tegra: Use DIV_ROUND_CLOSEST_ULL() instead of local implementation
pwm: tegra: Increase precision in PWM rate calculation
pwm: tegra: Add DT binding details to configure pin in suspends/resume
pwm: tegra: Add support to configure pin state in suspends/resume
pwm: tegra: Read PWM clock source rate in driver init
Sven Van Asbroeck (1):
pwm: pca9685: Fix GPIO-only operation
Thierry Reding (3):
pwm: tegra: Avoid potential overflow for short periods
Merge branch 'for-4.11/fixes' into for-next
Merge branch 'for-4.12/drivers' into for-next
kbuild test robot (1):
pwm: mediatek: Don't explicitly set .owner
.../devicetree/bindings/pwm/atmel-pwm.txt | 1 +
.../devicetree/bindings/pwm/nvidia,tegra20-pwm.txt | 45 ++++
.../devicetree/bindings/pwm/pwm-mediatek.txt | 34 +++
drivers/pwm/Kconfig | 9 +
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-atmel-hlcdc.c | 260 +++++++++----------
drivers/pwm/pwm-atmel.c | 276 ++++++++++-----------
drivers/pwm/pwm-lpss-pci.c | 10 +-
drivers/pwm/pwm-lpss-platform.c | 1 +
drivers/pwm/pwm-lpss.c | 19 +-
drivers/pwm/pwm-lpss.h | 1 +
drivers/pwm/pwm-mediatek.c | 219 ++++++++++++++++
drivers/pwm/pwm-pca9685.c | 112 ++++++---
drivers/pwm/pwm-rockchip.c | 40 ++-
drivers/pwm/pwm-tegra.c | 37 ++-
15 files changed, 742 insertions(+), 323 deletions(-)
create mode 100644 Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
create mode 100644 drivers/pwm/pwm-mediatek.c
reply other threads:[~2017-05-09 15:59 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=20170509155911.31267-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=torvalds@linux-foundation.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).