From: Chris Zhong <zyw@rock-chips.com>
To: heiko@sntech.de, dianders@chromium.org, broonie@kernel.org
Cc: linux-rockchip@lists.infradead.org,
Chris Zhong <zyw@rock-chips.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Liam Girdwood <lgirdwood@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Kumar Gala <galak@codeaurora.org>,
Zhang Qing <zhangqing@rock-chips.com>,
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 v2 0/2] add the dvs support for rk808
Date: Thu, 11 Dec 2014 11:16:40 +0800 [thread overview]
Message-ID: <1418267802-13159-1-git-send-email-zyw@rock-chips.com> (raw)
rk808 has a dvs function, there are 3 pins for dvs, dvs1 & dvs2 & dvsok.
Normally, the voltage of DCDC1/DCDC2 are controlled by BUCKn_ON_VSEL, when
we pull dvs1/dvs2 pin to active, they would be controlled by BUCKn_DVS_VSEL.
And the dvsok pin is used to indicate whether regulating has been completed.
When dvs1/dvs2 pin change, dvsok would be pull down, and it would be pull up
once the regulating is complete.
Changes in v2:
- increase description about dvs pins
- modify the multiline commenting
Chris Zhong (2):
mfd: dt-bindings: add the description about dvs gpio for rk808
regulator: rk808: add dvs support
Documentation/devicetree/bindings/mfd/rk808.txt | 13 +-
drivers/regulator/rk808-regulator.c | 192 ++++++++++++++++++++++--
2 files changed, 192 insertions(+), 13 deletions(-)
--
1.9.1
next reply other threads:[~2014-12-11 3:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 3:16 Chris Zhong [this message]
2014-12-11 3:16 ` [PATCH v2 1/2] mfd: dt-bindings: add the description about dvs gpio " Chris Zhong
2014-12-11 22:05 ` Doug Anderson
2014-12-12 13:06 ` Mark Brown
2014-12-11 3:16 ` [PATCH v2 2/2] regulator: rk808: add dvs support Chris Zhong
2014-12-11 22:05 ` Doug Anderson
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=1418267802-13159-1-git-send-email-zyw@rock-chips.com \
--to=zyw@rock-chips.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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
Powered by JetHome