From: Chris Zhong <zyw@rock-chips.com>
To: dianders@chromium.org, heiko@sntech.de
Cc: huangtao@rock-chips.com, cf@rock-chips.com,
zhangqing@rock-chips.com, Chris Zhong <zyw@rock-chips.com>,
devicetree@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH 0/2] regulator: get voltage & duty table from dts for st-pwm
Date: Wed, 17 Sep 2014 21:07:58 +0800 [thread overview]
Message-ID: <1410959280-29662-1-git-send-email-zyw@rock-chips.com> (raw)
get voltage & duty table from device tree might be better, other platforms can also use this
driver without any modify.
Tested on a rk3288 sdk board as logic voltage regulator.
Chris Zhong (2):
regulator: st-pwm: get voltage and duty table from dts
dt-bindings: add devicetree bindings for st-pwm regulator
.../devicetree/bindings/regulator/st-pwm.txt | 35 +++++++++
drivers/regulator/Kconfig | 1 -
drivers/regulator/st-pwm.c | 80 ++++++++++----------
3 files changed, 77 insertions(+), 39 deletions(-)
create mode 100644 Documentation/devicetree/bindings/regulator/st-pwm.txt
--
1.7.9.5
next reply other threads:[~2014-09-17 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:07 Chris Zhong [this message]
2014-09-17 13:07 ` [PATCH 1/2] regulator: st-pwm: get voltage and duty table from dts Chris Zhong
2014-09-17 15:15 ` Heiko Stübner
2014-09-17 16:51 ` Mark Brown
2014-09-17 16:54 ` Doug Anderson
2014-09-18 1:37 ` Chris Zhong
2014-09-18 3:36 ` Doug Anderson
2014-09-17 18:28 ` Doug Anderson
2014-09-17 21:26 ` Lee Jones
2014-09-17 13:08 ` [PATCH 2/2] dt-bindings: add devicetree bindings for st-pwm regulator Chris Zhong
2014-09-17 18:16 ` Doug Anderson
2014-09-17 18:35 ` Mark Brown
2014-09-17 19:46 ` Mark Rutland
2014-09-17 21:22 ` Lee Jones
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=1410959280-29662-1-git-send-email-zyw@rock-chips.com \
--to=zyw@rock-chips.com \
--cc=broonie@kernel.org \
--cc=cf@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=zhangqing@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
all inboxes | Powered by JetHome®