From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Sangbeom Kim <sbkim73@samsung.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-samsung-soc@vger.kernel.org,
Sachin Kamat <sachin.kamat@linaro.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Subject: [PATCH v3 0/2] regulator: s5m8767: Use GPIO for controlling Buck9/eMMC
Date: Fri, 24 Jan 2014 14:37:56 +0100 [thread overview]
Message-ID: <1390570678-30686-1-git-send-email-k.kozlowski@samsung.com> (raw)
Hi,
This is third version of patch adding GPIO control over Buck9 regulator
in s5m8767 regulator driver.
Previously the patch was part of larger patchset from which all other patches
were applied.
Changes since v2:
1. Use only one DT property ("s5m8767,pmic-ext-control-gpios");
suggested by Mark Brown.
Changes since v1:
1. Use ena_gpio of regulator core, as suggested by Mark Brown.
This patchset is based on next tree: next-20140122.
Best regards,
Krzysztof
Krzysztof Kozlowski (2):
regulator: s5m8767: Use GPIO for controlling Buck9/eMMC
regulator: s5m8767: Document new binding for Buck9 GPIO control
.../bindings/regulator/s5m8767-regulator.txt | 13 ++-
drivers/regulator/s5m8767.c | 87 +++++++++++++++++++-
include/linux/mfd/samsung/core.h | 3 +-
include/linux/mfd/samsung/s5m8767.h | 7 ++
4 files changed, 105 insertions(+), 5 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-01-24 13:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 13:37 Krzysztof Kozlowski [this message]
2014-01-24 13:37 ` [PATCH v3 1/2] " Krzysztof Kozlowski
2014-01-24 16:03 ` Lee Jones
2014-01-27 20:25 ` Mark Brown
2014-02-07 12:40 ` Krzysztof Kozlowski
2014-02-07 12:52 ` Mark Brown
2014-01-24 13:37 ` [PATCH v3 2/2] regulator: s5m8767: Document new binding for Buck9 GPIO control Krzysztof Kozlowski
2014-01-27 20:25 ` Mark Brown
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=1390570678-30686-1-git-send-email-k.kozlowski@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=sameo@linux.intel.com \
--cc=sbkim73@samsung.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®