From: Keerthy <j-keerthy@ti.com>
To: rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, rob@landley.net,
sameo@linux.intel.com, lee.jones@linaro.org,
grant.likely@linaro.org, lgirdwood@gmail.com, broonie@kernel.org
Cc: j-keerthy@ti.com, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: [PATCH 0/4] [PATCH v2 0/4] MFD: TPS65218: Drivers for TPS65218 PMIC.
Date: Thu, 6 Feb 2014 11:20:10 +0530 [thread overview]
Message-ID: <1391665814-18814-1-git-send-email-j-keerthy@ti.com> (raw)
The TPS65218 chip is a power management IC for Portable Navigation Systems
and Tablet Computing devices. It contains the following components:
- Regulators.
- Over Temperature warning and Shut down.
This patch adds support for TPS65218 mfd device. At this time only
the regulator functionality is made available.
The series is boot tested on am43x-epos-evm board.
Changes in v2:
* Introduced register cache for interrupt mask register.
* regulator_map_voltage_linear_range instead of custom functions.
* Fixed couple of more minor comments.
Keerthy (4):
mfd: DT bindings for TPS65218 PMIC
MFD: TPS65218: Add driver for the TPS65218 PMIC
Regulators: TPS65218: Add Regulator driver for TPS65218 PMIC
ARM: dts: TPS65218: Add dts nodes of TPS65218 PMIC
Documentation/devicetree/bindings/mfd/tps65218.txt | 58 ++++
.../devicetree/bindings/regulator/tps65218.txt | 22 ++
arch/arm/boot/dts/am43x-epos-evm.dts | 40 +++
drivers/mfd/Kconfig | 15 +
drivers/mfd/Makefile | 1 +
drivers/mfd/tps65218.c | 281 ++++++++++++++++++
drivers/regulator/Kconfig | 9 +
drivers/regulator/Makefile | 1 +
drivers/regulator/tps65218-regulator.c | 304 ++++++++++++++++++++
include/linux/mfd/tps65218.h | 284 ++++++++++++++++++
10 files changed, 1015 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mfd/tps65218.txt
create mode 100644 Documentation/devicetree/bindings/regulator/tps65218.txt
create mode 100644 drivers/mfd/tps65218.c
create mode 100644 drivers/regulator/tps65218-regulator.c
create mode 100644 include/linux/mfd/tps65218.h
--
1.7.9.5
next reply other threads:[~2014-02-06 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 5:50 Keerthy [this message]
2014-02-06 5:50 ` [PATCH v2 1/4] mfd: DT bindings for TPS65218 PMIC Keerthy
2014-02-06 5:50 ` [PATCH v2 2/4] MFD: TPS65218: Add driver for the " Keerthy
2014-02-06 14:37 ` Lee Jones
2014-02-06 17:09 ` Keerthy
2014-02-07 11:12 ` Lee Jones
2014-02-07 13:41 ` Keerthy
2014-02-06 5:50 ` [PATCH v2 3/4] Regulators: TPS65218: Add Regulator driver for " Keerthy
2014-02-07 13:58 ` Keerthy
[not found] ` <52F4E685.4060605-l0cyMroinI0@public.gmane.org>
2014-02-07 17:27 ` Mark Brown
2014-02-14 20:21 ` Mark Brown
2014-02-18 8:22 ` Keerthy
2014-02-06 5:50 ` [PATCH 4/4] ARM: dts: AM43x: Add dts nodes of " 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=1391665814-18814-1-git-send-email-j-keerthy@ti.com \
--to=j-keerthy@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.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).