From: Keerthy <j-keerthy@ti.com>
To: <dmitry.torokhov@gmail.com>, <linus.walleij@linaro.org>,
<gnurou@gmail.com>, <lee.jones@linaro.org>, <broonie@kernel.org>,
<tony@atomide.com>
Cc: <linux-omap@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-input@vger.kernel.org>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <j-keerthy@ti.com>
Subject: [PATCH v4 0/6] mfd: tps65218: Clean ups
Date: Tue, 28 Jun 2016 14:52:03 +0530 [thread overview]
Message-ID: <1467105729-28249-1-git-send-email-j-keerthy@ti.com> (raw)
The series cleans up mainly the regulator driver and implements
the device tree parsing using the regulator framework. Removes
all the redundant compatibles for the individual regulators.
Adds platform_device_id table for the gpio and power button modules.
One of the patch removes redundant read wrapper and makes
use of regmap_read wherever necessary.
The series is checked for all the regulator registrations on
am437x-gp-evm and am437x-sk-evm.
Boot log on am437x-sk-evm: http://pastebin.ubuntu.com/18016754/
Changes in v4:
For gpio-tps65218 reatined the compatible table.
Fixed missing ';' in the power button patch.
Fixed comments on the Documentation patch.
Split the Device Tree patches to a separate series.
Changes in v3:
Missed making corresponding changes in the power button and gpio
drivers. Added couple of patches to fix them to use mfd_cell way
of parsing.
Keerthy (6):
mfd: tps65218: Remove redundant read wrapper
Documentation: regulator: tps65218: Update examples
input: tps65218-pwrbutton: Add platform_device_id table
gpio: tps65218-gpio: Add platform_device_id table
mfd: tps65218: Use mfd_add_devices instead of of_platform_populate
regulator: tps65218: Remove all the compatibles
.../devicetree/bindings/regulator/tps65218.txt | 87 ++++++++++---
drivers/gpio/gpio-tps65218.c | 10 +-
drivers/input/misc/tps65218-pwrbutton.c | 10 +-
drivers/mfd/tps65218.c | 32 ++---
drivers/regulator/tps65218-regulator.c | 134 ++++++++-------------
include/linux/mfd/tps65218.h | 2 -
6 files changed, 152 insertions(+), 123 deletions(-)
--
1.9.1
next reply other threads:[~2016-06-28 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 9:22 Keerthy [this message]
2016-06-28 9:22 ` [PATCH v4 1/6] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-06-28 9:22 ` [PATCH v4 2/6] Documentation: regulator: tps65218: Update examples Keerthy
2016-06-28 9:22 ` [PATCH v4 3/6] input: tps65218-pwrbutton: Add platform_device_id table Keerthy
2016-06-28 9:22 ` [PATCH v4 4/6] gpio: tps65218-gpio: " Keerthy
2016-06-28 9:22 ` [PATCH v4 5/6] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-28 10:56 ` Lee Jones
2016-06-28 9:22 ` [PATCH v4 6/6] regulator: tps65218: Remove all the compatibles Keerthy
2016-06-28 10:26 ` Keerthy
2016-06-28 12:27 ` [PATCH v4 0/6] mfd: tps65218: Clean ups Keerthy
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=1467105729-28249-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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).