linux-pwm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v3.17-rc1
Date: Fri, 8 Aug 2014 13:22:22 +0200	[thread overview]
Message-ID: <20140808112220.GA21202@ulmo.nvidia.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2586 bytes --]

Hi Linus,

The following changes since commit 7171511eaec5bf23fb06078f59784a3a0626b38f:

  Linux 3.16-rc1 (2014-06-15 17:45:28 -1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git tags/pwm/for-3.17-rc1

for you to fetch changes up to f6306299080bbb1a77ad39494203f5397a5c2630:

  pwm: rockchip: Added to support for RK3288 SoC (2014-08-08 13:12:47 +0200)

Thanks,
Thierry

----------------------------------------------------------------
pwm: Changes for v3.17-rc1

The set of changes for this merge window contains two new drivers: one
for Rockchip SoCs and another for STMicroelectronics STiH4xx SoCs. The
remainder of the changes are the usual small cleanups such as removing
redundant OOM messages, signalling that a PWM chip's operations can
sleep and removing an unneeded dependency.

----------------------------------------------------------------
Ajit Pal Singh (4):
      pwm: sti: Fix PWM prescaler handling
      pwm: sti: Ensure same period values for all channels
      pwm: sti: Sync between enable/disable calls
      pwm: sti: Remove PWM period table

Beniamino Galvani (2):
      pwm: add Rockchip SoC PWM support
      pwm: rockchip: document device tree bindings

Caesar Wang (2):
      pwm: rockchip: document RK3288 SoC compatible
      pwm: rockchip: Added to support for RK3288 SoC

Heikki Krogerus (1):
      pwm: lpss: remove dependency on clk framework

Jingoo Han (1):
      pwm: pwm-tipwmss: remove unnecessary OOM messages

Lee Jones (2):
      pwm: sti: Add new driver for ST's PWM IP
      pwm: sti: Supply Device Tree binding documentation for ST's PWM IP

Shawn Guo (1):
      pwm: imx: set can_sleep flag for imx_pwm

 .../devicetree/bindings/pwm/pwm-rockchip.txt       |  20 +
 Documentation/devicetree/bindings/pwm/pwm-st.txt   |  41 ++
 drivers/pwm/Kconfig                                |  17 +
 drivers/pwm/Makefile                               |   2 +
 drivers/pwm/pwm-imx.c                              |   1 +
 drivers/pwm/pwm-lpss.c                             |  32 +-
 drivers/pwm/pwm-rockchip.c                         | 264 +++++++++++++
 drivers/pwm/pwm-sti.c                              | 418 +++++++++++++++++++++
 drivers/pwm/pwm-tipwmss.c                          |   4 +-
 9 files changed, 774 insertions(+), 25 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/pwm/pwm-rockchip.txt
 create mode 100644 Documentation/devicetree/bindings/pwm/pwm-st.txt
 create mode 100644 drivers/pwm/pwm-rockchip.c
 create mode 100644 drivers/pwm/pwm-sti.c

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

                 reply	other threads:[~2014-08-08 11:22 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=20140808112220.GA21202@ulmo.nvidia.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).