[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130610080420.GC24958@gmail.com>
Date: Mon, 10 Jun 2013 09:04:20 +0100
From: Lee Jones <lee.jones@...aro.org>
To: "J, KEERTHY" <j-keerthy@...com>
Cc: Stephen Warren <swarren@...dotorg.org>,
"Cousson, Benoit" <b-cousson@...com>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
"linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"ldewangan@...dia.com" <ldewangan@...dia.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"swarren@...dia.com" <swarren@...dia.com>,
"sameo@...ux.intel.com" <sameo@...ux.intel.com>,
"gg@...mlogic.co.uk" <gg@...mlogic.co.uk>
Subject: Re: [PATCH] ARM: dts: add dtsi for palmas
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists