From: "Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
To: lgirdwood@gmail.com, broonie@kernel.org, sre@kernel.org,
lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org,
"Paweł Chmiel" <pawel.mikolaj.chmiel@gmail.com>
Subject: [PATCH v2 0/3] power: supply: max8998-charger:
Date: Sat, 14 Jul 2018 14:26:50 +0200 [thread overview]
Message-ID: <1531571213-30593-1-git-send-email-pawel.mikolaj.chmiel@gmail.com> (raw)
This patch series compose of 3 patches.
First patch, fixes platform data retrieval issue in max8998 charger
driver, which could cause NULL pointer dereference.
Second patch, updates max8998 charger driver, so it's possible to parse
devicetree for configuration.
Third patch, updates max8998 documentation, so it includes new node
and properties, needed for charger.
All patches has been tested on, Samsung Galaxy S (i9000) phone.
Changes from v1:
- Removed unneeded Fixes tag
- Correct description of all charger values
- Added missing property unit for charger properties
- Removed already applied patch
Paweł Chmiel (2):
power: supply: max8998-charger: Parse device tree for required data.
dt-bindings: mfd: max8998: Add charger subnode binding
Tomasz Figa (1):
power: supply: max8998-charger: Fix platform data retrieval
Documentation/devicetree/bindings/mfd/max8998.txt | 24 +++++++++++
drivers/power/supply/max8998_charger.c | 52 ++++++++++++++++++++++-
2 files changed, 75 insertions(+), 1 deletion(-)
--
2.7.4
next reply other threads:[~2018-07-14 12:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 12:26 Paweł Chmiel [this message]
2018-07-14 12:26 ` [PATCH v2 1/3] power: supply: max8998-charger: Fix platform data retrieval Paweł Chmiel
2018-07-14 12:26 ` [PATCH v2 2/3] power: supply: max8998-charger: Parse device tree for required data Paweł Chmiel
2018-07-14 12:26 ` [PATCH v2 3/3] dt-bindings: mfd: max8998: Add charger subnode binding Paweł Chmiel
2018-07-16 18:00 ` Rob Herring
2018-07-16 18:59 ` Paweł Chmiel
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=1531571213-30593-1-git-send-email-pawel.mikolaj.chmiel@gmail.com \
--to=pawel.mikolaj.chmiel@gmail.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-pm@vger.kernel.org \
--cc=mark.rutland@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).