From: AnilKumar Ch <anilkumar-l0cyMroinI0@public.gmane.org>
To: sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
lrg-l0cyMroinI0@public.gmane.org,
broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/3] Add device tree support for AM33XX regulators
Date: Tue, 10 Jul 2012 16:39:41 +0530 [thread overview]
Message-ID: <1341918584-28004-1-git-send-email-anilkumar@ti.com> (raw)
Add device tree support for regulators present on AM33XX family
of devices like AM335X-EVM and AM335X-Bone. TPS65217 regulator
is present on AM335X-Bone and TPS65910 on AM335X-EVM.
First patch adds the device tree support to tps65217 regulator
so that it will take the parameters from tps65217.dtsi file and
convert to tps65217 regulator parameters.
Second patch adds tps65910 device tree data by adding separate
DT tps65910.dtsi file, which contains the generic tps65910 PMIC
DT data.
Third patch adds tps65217 device tree data by adding separate
tps65910.dtsi file, which contains the generic tps65910 PMIC
DT data.
This patch series was tested by adding the I2C slave address to
corresponding .dts files.
Changes form V1:
- Add regulator-compatible data to dt files.
- Separated device tree data addition to am335x-evm/bone dts
from the regulator patches
AnilKumar Ch (3):
regulator: tps65217: Add device tree support
ARM: OMAP2+: AM33XX: Add tps65910 device tree data
ARM: OMAP2+: AM33XX: Add tps65217 device tree data
.../devicetree/bindings/regulator/tps65217.txt | 91 +++++++++++++++
arch/arm/boot/dts/tps65217.dtsi | 84 +++++++++++++
arch/arm/boot/dts/tps65910.dtsi | 123 ++++++++++++++++++++
drivers/mfd/tps65217.c | 67 ++++++++++-
drivers/regulator/tps65217-regulator.c | 1 +
include/linux/mfd/tps65217.h | 3 +-
6 files changed, 366 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/regulator/tps65217.txt
create mode 100644 arch/arm/boot/dts/tps65217.dtsi
create mode 100644 arch/arm/boot/dts/tps65910.dtsi
--
1.7.9.5
next reply other threads:[~2012-07-10 11:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 11:09 AnilKumar Ch [this message]
2012-07-10 11:09 ` [PATCH v2 1/3] regulator: tps65217: Add device tree support AnilKumar Ch
2012-07-12 17:28 ` Mark Brown
[not found] ` <20120712172836.GR7256-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-07-13 5:43 ` AnilKumar, Chimata
2012-07-13 9:54 ` Mark Brown
2012-07-16 12:35 ` AnilKumar, Chimata
[not found] ` <1341918584-28004-1-git-send-email-anilkumar-l0cyMroinI0@public.gmane.org>
2012-07-10 11:09 ` [PATCH v2 2/3] ARM: OMAP2+: AM33XX: Add tps65910 device tree data AnilKumar Ch
2012-07-10 11:09 ` [PATCH v2 3/3] ARM: OMAP2+: AM33XX: Add tps65217 " AnilKumar Ch
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=1341918584-28004-1-git-send-email-anilkumar@ti.com \
--to=anilkumar-l0cymroini0@public.gmane.org \
--cc=broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lrg-l0cyMroinI0@public.gmane.org \
--cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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).