From: Laxman Dewangan <ldewangan@nvidia.com>
To: J Keerthy <j-keerthy@ti.com>
Cc: "b-cousson@ti.com" <b-cousson@ti.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
Stephen Warren <swarren@nvidia.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>,
"lee.jones@linaro.org" <lee.jones@linaro.org>
Subject: Re: [PATCH v2 1/2] ARM: dts: add dtsi for palmas
Date: Mon, 10 Jun 2013 14:55:21 +0530 [thread overview]
Message-ID: <51B59B81.8040208@nvidia.com> (raw)
In-Reply-To: <1370855059-5342-2-git-send-email-j-keerthy@ti.com>
On Monday 10 June 2013 02:34 PM, J Keerthy wrote:
> Adds palmas mfd and palmas regulator nodes.
>
> Signed-off-by: Graeme Gregory <gg@slimlogic.co.uk>
> Signed-off-by: J Keerthy <j-keerthy@ti.com>
> ---
> arch/arm/boot/dts/palmas.dtsi | 98 +++++++++++++++++++++++++++++++++++++++++
Hi Keerthy,
Can you please add documentation for dt binding:
Documentation/devicetree/bindings/mfd
Most of time we refer from this document for dt population.
Thanks,
Laxman
next prev parent reply other threads:[~2013-06-10 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 9:04 [PATCH v2 0/2] ARM: dts: Add palmas dtsi J Keerthy
2013-06-10 9:04 ` [PATCH v2 1/2] ARM: dts: add dtsi for palmas J Keerthy
2013-06-10 9:25 ` Laxman Dewangan [this message]
2013-06-10 9:24 ` J, KEERTHY
2013-06-10 16:29 ` Stephen Warren
2013-06-11 4:10 ` J, KEERTHY
2013-06-10 9:04 ` [PATCH v2 2/2] ARM: dts: OMAP5: add palmas node and omap specific palmas regulator properties J Keerthy
2013-06-10 10:05 ` Lee Jones
2013-06-10 10:16 ` J, 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=51B59B81.8040208@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gg@slimlogic.co.uk \
--cc=grant.likely@secretlab.ca \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=swarren@nvidia.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