devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Caesar Wang <caesar.wang@rock-chips.com>
To: heiko@sntech.de, thierry.reding@gmail.com, b.galvani@gmail.com
Cc: cf@rock-chips.com, huangtao@rock-chips.com,
	addy.ke@rock-chips.com, xjq@rock-chips.com,
	linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Caesar Wang <caesar.wang@rock-chips.com>
Subject: [PATCH v2 0/2] This series adds support for Rockchip SoCs integrated PWM.
Date: Sat, 19 Jul 2014 20:55:27 +0800	[thread overview]
Message-ID: <1405774529-26027-1-git-send-email-caesar.wang@rock-chips.com> (raw)

This patch will make applying on the top of Beniamino's submission,
the Beniamino's submission come from [1].

[1]:
https://git.kernel.org/cgit/linux/kernel/git/thierry.reding/linux-pwm.git/log/?h=for-next

Beniamino's submission won't be used from genenation Rockchip SoCs.
So I have to add the new pwm for next genenation Rockchip SoCs.

Tested on RK3288 SDK board.

Changes in v2:
    * address comments from Beniamino Galvani Reding:
      - remove #include <linux/of_address.h>. 
      - of_iomap be removed,and devm_ioremap replace it.
      - remove a line no be used.

Caesar Wang (2):
  [PATCH v2 1/2] pwm: add this patch to introduce for rk-pwm and vop-pwm

  [PATCH v2 2/2] pwm: add this patch to support the new pwm of Rockchip SoCs

 .../devicetree/bindings/pwm/pwm-rockchip.txt       | 13 +--
 drivers/pwm/pwm-rockchip.c                         | 97 ++++++++++++++++++----
 2 files changed, 87 insertions(+), 23 deletions(-)

-- 
1.9.1

             reply	other threads:[~2014-07-19 12:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-19 12:55 Caesar Wang [this message]
2014-07-19 12:55 ` [PATCH v2 1/2] pwm: add this patch to introduce for rk-pwm and vop-pwm Caesar Wang
2014-07-21  8:57   ` Thierry Reding
2014-07-21 10:39     ` caesar
2014-07-19 12:55 ` [PATCH v2 2/2] pwm: add this patch to support the new pwm of Rockchip SoCs Caesar Wang
2014-07-21  8:50   ` Thierry Reding
     [not found]     ` <53CD0E82.6030901@rock-chips.com>
2014-07-21 13:27       ` Thierry Reding
2014-07-21 14:10         ` caesar
2014-07-25 10:29         ` caesar
2014-07-27  4:59           ` Doug Anderson
     [not found]             ` <53D50601.1020106@rock-chips.com>
2014-07-28  4:01               ` Doug Anderson
2014-07-28 11:19                 ` caesar
     [not found]                   ` <53D631B6.1050603-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2014-07-28 16:58                     ` Olof Johansson
2014-07-29  9:35                       ` caesar
2014-07-29 10:23                       ` Thierry Reding
2014-07-29 10:22                   ` Thierry Reding
2014-07-29 11:09                     ` caesar
2014-07-29 11:38                       ` Thierry Reding
2014-07-29 14:17                         ` caesar
2014-07-29 10:25             ` 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=1405774529-26027-1-git-send-email-caesar.wang@rock-chips.com \
    --to=caesar.wang@rock-chips.com \
    --cc=addy.ke@rock-chips.com \
    --cc=b.galvani@gmail.com \
    --cc=cf@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=xjq@rock-chips.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).