From: Lee Jones <lee.jones@linaro.org>
To: "J, KEERTHY" <j-keerthy@ti.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
"Cousson, Benoit" <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>,
"ldewangan@nvidia.com" <ldewangan@nvidia.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"swarren@nvidia.com" <swarren@nvidia.com>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
"gg@slimlogic.co.uk" <gg@slimlogic.co.uk>
Subject: Re: [PATCH] ARM: dts: add dtsi for palmas
Date: Mon, 10 Jun 2013 09:04:20 +0100 [thread overview]
Message-ID: <20130610080420.GC24958@gmail.com> (raw)
In-Reply-To: <DC88CAD03C0052499C1907B327FC63229EAA39@DBDE04.ent.ti.com>
> Totally agree to all the above concerns. So can we have a custom .dtsi file
> for a board+pmic combination? Or have only the required properties over ridden
> in the board file?
The common approach is to only apply nodes and node properties to the
.dtsi files which are appropriate for _all_ platforms which include
them. Anything that is only relevant to a sub-set of boards should be
in a higher ranking .dtsi file and finally, any settings which are
board specific should be in the board's .dts file.
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-06-10 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:28 [PATCH] ARM: dts: add dtsi for palmas J Keerthy
2013-06-07 11:28 ` J Keerthy
[not found] ` <1370604504-32310-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2013-06-07 12:27 ` Benoit Cousson
2013-06-07 12:27 ` Benoit Cousson
2013-06-07 12:32 ` J, KEERTHY
[not found] ` <51B1D1A9.40702-l0cyMroinI0@public.gmane.org>
2013-06-07 19:22 ` Stephen Warren
2013-06-07 19:22 ` Stephen Warren
2013-06-07 19:56 ` Stephen Warren
2013-06-10 4:03 ` J, KEERTHY
2013-06-10 8:04 ` Lee Jones [this message]
[not found] ` <DC88CAD03C0052499C1907B327FC63229EAA39-yXqyApvAXouIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2013-06-10 9:29 ` Benoit Cousson
2013-06-10 9:29 ` Benoit Cousson
2013-06-10 10:17 ` J, KEERTHY
2013-06-10 16:21 ` Stephen Warren
2013-06-10 16:22 ` Stephen Warren
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=20130610080420.GC24958@gmail.com \
--to=lee.jones@linaro.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=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 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.