From: Stephen Warren <swarren@wwwdotorg.org>
To: J Keerthy <j-keerthy@ti.com>
Cc: b-cousson@ti.com, devicetree-discuss@lists.ozlabs.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
ldewangan@nvidia.com, grant.likely@secretlab.ca,
swarren@nvidia.com, sameo@linux.intel.com, gg@slimlogic.co.uk,
lee.jones@linaro.org
Subject: Re: [PATCH v4] ARM: dts: OMAP5: Add palmas MFD node and regulator nodes
Date: Wed, 12 Jun 2013 09:51:38 -0600 [thread overview]
Message-ID: <51B8990A.8030506@wwwdotorg.org> (raw)
In-Reply-To: <1371025140-25376-1-git-send-email-j-keerthy@ti.com>
On 06/12/2013 02:19 AM, J Keerthy wrote:
> This patch adds Palmas MFD node and the regulator nodes for OMAP5.
>
> The node definitions are based on: https://lkml.org/lkml/2013/6/6/25
>
> Boot tested on omap5-uevm board.
Reviewed-by: Stephen Warren <swarren@nvidia.com>
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
> + palmas: palmas@48 {
> + reg = <0x48>;
> + interrupts = <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>; /* IRQ_SYS_1N */
> + interrupt-parent = <&gic>;
> + compatible = "ti,palmas";
... although personally I prefer the compatible property to be right at
the top of each node, since it's what implies the schema for the rest of
the node. That's a tiny nit though; feel free to ignore it if the OMAP
files don't follow that convention.
next prev parent reply other threads:[~2013-06-12 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 8:19 [PATCH v4] ARM: dts: OMAP5: Add palmas MFD node and regulator nodes J Keerthy
2013-06-12 15:51 ` Stephen Warren [this message]
2013-06-13 4:09 ` 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=51B8990A.8030506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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=ldewangan@nvidia.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 \
/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