From: Keerthy <j-keerthy@ti.com>
To: broonie@kernel.org, tony@atomide.com, robh+dt@kernel.org,
mark.rutland@arm.com, lee.jones@linaro.org
Cc: nm@ti.com, devicetree@vger.kernel.org, nikita@compulab.co.il,
j-keerthy@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] regulator: tps65218: Clean ups
Date: Wed, 11 May 2016 11:18:03 +0530 [thread overview]
Message-ID: <1462945691-904-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.
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.
Keerthy (8):
mfd: tps65218: Remove redundant read wrapper
Documentation: regulator: tps65218: Updates according to changes with
parsing
mfd: tps65218: Use mfd_add_devices instead of of_platform_populate
regulator: tps65218: Remove all the compatibles
ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles
ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles
ARM: dts: AM437X-CM-T43: Remove redundant regulator compatibles
ARM: dts: AM43X-EPOS-EVM: Remove redundant regulator compatibles
.../devicetree/bindings/regulator/tps65218.txt | 88 +++++++++++---
arch/arm/boot/dts/am437x-cm-t43.dts | 6 -
arch/arm/boot/dts/am437x-gp-evm.dts | 6 -
arch/arm/boot/dts/am437x-sk-evm.dts | 5 -
arch/arm/boot/dts/am43x-epos-evm.dts | 7 --
drivers/mfd/tps65218.c | 24 ++--
drivers/regulator/tps65218-regulator.c | 134 ++++++++-------------
include/linux/mfd/tps65218.h | 2 -
8 files changed, 127 insertions(+), 145 deletions(-)
--
1.9.1
next reply other threads:[~2016-05-11 5:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 5:48 Keerthy [this message]
2016-05-11 5:48 ` [PATCH 1/8] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-05-11 5:48 ` [PATCH 2/8] Documentation: regulator: tps65218: Update examples Keerthy
[not found] ` <1462945691-904-3-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-05-16 14:48 ` Rob Herring
2016-05-17 3:22 ` Keerthy
2016-05-11 5:48 ` [PATCH 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-03 11:08 ` Keerthy
2016-06-06 9:00 ` Lee Jones
2016-06-08 15:50 ` Lee Jones
2016-06-08 16:09 ` Keerthy
2016-05-11 5:48 ` [PATCH 4/8] regulator: tps65218: Remove all the compatibles Keerthy
2016-05-11 10:21 ` Mark Brown
2016-05-11 5:48 ` [PATCH 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles Keerthy
[not found] ` <1462945691-904-6-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-05-12 17:08 ` Tony Lindgren
2016-05-11 5:48 ` [PATCH 6/8] ARM: dts: AM437X-SK-EVM: " Keerthy
2016-05-11 5:48 ` [PATCH 7/8] ARM: dts: AM437X-CM-T43: " Keerthy
2016-05-11 5:48 ` [PATCH 8/8] ARM: dts: AM43X-EPOS-EVM: " 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=1462945691-904-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nikita@compulab.co.il \
--cc=nm@ti.com \
--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).