From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: AnilKumar Ch <anilkumar@ti.com>
Cc: sameo@linux.intel.com, lrg@ti.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
grant.likely@secretlab.ca
Subject: Re: [PATCH 1/3] regulator: tps65217: Add device tree support
Date: Mon, 25 Jun 2012 13:12:20 +0100 [thread overview]
Message-ID: <20120625121220.GA30406@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1340625878-32336-2-git-send-email-anilkumar@ti.com>
[-- Attachment #1: Type: text/plain, Size: 529 bytes --]
On Mon, Jun 25, 2012 at 05:34:36PM +0530, AnilKumar Ch wrote:
> This commit adds device tree support for tps65217 pmic. And usage
> details are added to device tree documentation.
>
> Driver is tested by using kernel module with regulator set and get
> APIs.
This needs to be updated for the patches Laxman recently posted for the
regulator-compatible property (which are currently blocked on review
from the ST Ericcsson guys but I'll probably apply them in the next
couple of days if I don't hear back from them).
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-25 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:04 [PATCH 0/3] Add device tree support for AM33XX regulators AnilKumar Ch
2012-06-25 12:04 ` AnilKumar Ch
2012-06-25 12:04 ` [PATCH 1/3] regulator: tps65217: Add device tree support AnilKumar Ch
2012-06-25 12:04 ` AnilKumar Ch
2012-06-25 12:12 ` Mark Brown [this message]
2012-06-25 12:28 ` AnilKumar, Chimata
2012-06-25 12:04 ` [PATCH 2/3] ARM: OMAP2+: AM33XX: Add tps65217 device tree data AnilKumar Ch
2012-06-25 12:04 ` AnilKumar Ch
2012-06-25 12:04 ` [PATCH 3/3] ARM: OMAP2+: AM33XX: Add tps65910 " AnilKumar Ch
2012-06-25 12:04 ` 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=20120625121220.GA30406@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=anilkumar@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sameo@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.