From: caesar <caesar.wang@rock-chips.com>
To: thierry.reding@gmail.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, rdunlap@infradead.org
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
cf@rock-chips.com, addy.ke@rock-chips.com, xjq@rock-chips.com,
huangtao@rock-chips.com, hj@rock-chips.com,
caesar <caesar.wang@rock-chips.com>
Subject: [PATCH 0/2] This series adds support for Rockchip SoCs integrated PWM.
Date: Thu, 17 Jul 2014 14:08:12 +0800 [thread overview]
Message-ID: <1405577294-19336-1-git-send-email-caesar.wang@rock-chips.com> (raw)
This patch would be 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 next genenation RK SoCs.
So we have to add support to the new pwm version and VOP_PWM for next genenation RK SoCs.
Tested on RK3288 SDK board.
caesar (2):
[PATCH 1/2] pwm: add this series patch to introduce for rk-pwm and vop-pwm
[PATCH 2/2] pwm: add this series patch to support for rk-pwm and vop-pwm.
.../devicetree/bindings/pwm/pwm-rockchip.txt | 13 ++-
drivers/pwm/pwm-rockchip.c | 108 +++++++++++++++++----
2 files changed, 96 insertions(+), 25 deletions(-)
--
1.9.1
mZ
next reply other threads:[~2014-07-17 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 6:08 caesar [this message]
2014-07-17 6:08 ` [PATCH 1/2] pwm: add this series patch to introduce for rk-pwm and vop-pwm caesar
2014-07-17 6:08 ` [PATCH 2/2] pwm: add this series patch to support " caesar
2014-07-17 19:24 ` Beniamino Galvani
2014-07-18 5:05 ` caesar
2014-07-18 10:03 ` Thierry Reding
2014-07-18 11:04 ` caesar
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=1405577294-19336-1-git-send-email-caesar.wang@rock-chips.com \
--to=caesar.wang@rock-chips.com \
--cc=addy.ke@rock-chips.com \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hj@rock-chips.com \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@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).