From: Rhyland Klein <rklein@nvidia.com>
To: Anton Vorontsov <cbou@mail.ru>,
David Woodhouse <dwmw2@infradead.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>
Cc: <devicetree-discuss@lists.ozlabs.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Rhyland Klein <rklein@nvidia.com>
Subject: [RFC 0/3] Add DT Binding for Power-Supply supplied-nodes property
Date: Fri, 15 Feb 2013 18:36:53 -0500 [thread overview]
Message-ID: <1360971416-30717-1-git-send-email-rklein@nvidia.com> (raw)
This series is an attempt to define a common way for devicetree
initialized power_supplies to define their list of supplicants
in a common manner.
Instead of relying on custom properties which contain is list of
strings, use the much more direct method of phandles to reference
the supplicants and define a common function which can retrieve them
automatically.
Rhyland Klein (3):
power_supply: Define Binding for supplied-nodes
power: power_supply: Add core support for supplied_nodes
power: power_supply: add support for getting supplied-nodes from dt
.../bindings/power_supply/power_supply.txt | 17 ++++
drivers/power/power_supply_core.c | 82 +++++++++++++++++++-
include/linux/power_supply.h | 10 +++
3 files changed, 107 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power_supply/power_supply.txt
--
1.7.9.5
next reply other threads:[~2013-02-15 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 23:36 Rhyland Klein [this message]
2013-02-15 23:36 ` [RFC 1/3] power_supply: Define Binding for supplied-nodes Rhyland Klein
2013-02-16 22:38 ` Anton Vorontsov
2013-02-18 6:04 ` Rajanikanth HV
2013-02-15 23:36 ` [RFC 2/3] power: power_supply: Add core support for supplied_nodes Rhyland Klein
2013-02-15 23:36 ` [RFC 3/3] power: power_supply: add support for getting supplied-nodes from dt Rhyland Klein
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=1360971416-30717-1-git-send-email-rklein@nvidia.com \
--to=rklein@nvidia.com \
--cc=cbou@mail.ru \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.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®