From: Heiko Stuebner <heiko@sntech.de>
To: sre@kernel.org, dbaryshkov@gmail.com, dwmw2@infradead.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, robh+dt@kernel.org,
mark.rutland@arm.com, pawel.moll@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
dianders@chromium.org, heiko@sntech.de
Subject: [PATCH v4 0/3] gpio-charger: add devicetree support
Date: Tue, 23 Sep 2014 22:42:13 +0200 [thread overview]
Message-ID: <1411504936-21026-1-git-send-email-heiko@sntech.de> (raw)
This series adds devicetree support to the gpio-charger and fixes a small
issue with the return value of gpio_get_value.
changes since v3:
- remove of_match_ptr. All used of_xx function have stubs for !OF
and of_device_id also is always defined, so no need for of_match_ptr
changes since v2:
- fix (hopefully all) issues pointed out by Doug Anderson
- add missing of_node assignment to charger
changes since v1:
- adapt binding example to show how the charger fits into the
power-supplies structure
Heiko Stuebner (3):
dt-bindings: document gpio-charger bindings
power: gpio-charger: add device tree support
power: gpio-charger: do not use gpio value directly
.../bindings/power_supply/gpio-charger.txt | 27 ++++++++
drivers/power/gpio-charger.c | 74 +++++++++++++++++++++-
2 files changed, 98 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power_supply/gpio-charger.txt
--
2.1.0
next reply other threads:[~2014-09-23 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 20:42 Heiko Stuebner [this message]
2014-09-23 20:42 ` [PATCH v4 1/3] dt-bindings: document gpio-charger bindings Heiko Stuebner
2014-09-23 20:42 ` [PATCH v4 2/3] power: gpio-charger: add device tree support Heiko Stuebner
2014-09-23 20:42 ` [PATCH v4 3/3] power: gpio-charger: do not use gpio value directly Heiko Stuebner
2014-10-26 12:06 ` [PATCH v4 0/3] gpio-charger: add devicetree support Heiko Stübner
2014-10-27 15:55 ` Sebastian Reichel
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=1411504936-21026-1-git-send-email-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=dbaryshkov@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sre@kernel.org \
/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).