From: Chen-Yu Tsai <wens@csie.org>
To: Samuel Ortiz <sameo@linux.intel.com>,
Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH v10 0/2] mfd: axp20x: Add DT binding documentation
Date: Fri, 20 Feb 2015 19:19:26 +0800 [thread overview]
Message-ID: <1424431168-25157-1-git-send-email-wens@csie.org> (raw)
Hi everyone,
This is v10 of the axp20x series. v10 reverts back to the DT bindings
from v8. This is the binding currently supported by the kernel drivers
since 3.18. Mark Brown raised concern on the needless changes to
active regulator bindings in v9.
Maxime, I dropped your Acked-by because of all the changes I've made.
Please have a look again.
Mark (Brown), please take a look at the regulator bits in the second
patch. If it looks good, could you give your Acked-by?
I hope we can get this series merged so we can move on to adding
AXP221 support.
Regards,
ChenYu
Changes since v9:
- Revert to bindings in v8
- Dropped new patches in v9
- x-powers,dcdc-workmode default changed to "current hardware setting",
matching the regulator driver.
- Reorganized regulator related properties into separate section.
This should make it easier to read and also update for newer PMICs.
- Regulator nodes should only be listed if they are to be managed by
the OS.
Carlo Caione (2):
mfd: AXP20x: Add bindings documentation
dt-bindings: add vendor-prefix for X-Powers
Documentation/devicetree/bindings/mfd/axp20x.txt | 96 ++++++++++++++++++++++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
2 files changed, 97 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/axp20x.txt
--
2.1.4
next reply other threads:[~2015-02-20 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 11:19 Chen-Yu Tsai [this message]
2015-02-20 11:19 ` [PATCH v10 1/2] mfd: AXP20x: Add bindings documentation Chen-Yu Tsai
2015-03-06 16:48 ` Chen-Yu Tsai
2015-03-09 9:29 ` Lee Jones
[not found] ` <1424431168-25157-2-git-send-email-wens-jdAy2FN1RRM@public.gmane.org>
2015-03-25 18:33 ` Maxime Ripard
2015-03-26 8:26 ` Lee Jones
[not found] ` <1424431168-25157-1-git-send-email-wens-jdAy2FN1RRM@public.gmane.org>
2015-02-20 11:19 ` [PATCH v10 2/2] dt-bindings: add vendor-prefix for X-Powers Chen-Yu Tsai
[not found] ` <1424431168-25157-3-git-send-email-wens-jdAy2FN1RRM@public.gmane.org>
2015-03-26 8:26 ` 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=1424431168-25157-1-git-send-email-wens@csie.org \
--to=wens@csie.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@free-electrons.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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).