From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v3 0/4] Device tree support for regulators Date: Thu, 27 Oct 2011 10:08:47 +0100 Message-ID: <20111027090847.GC6641@opensource.wolfsonmicro.com> References: <1319702185-16108-1-git-send-email-rnayak@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1319702185-16108-1-git-send-email-rnayak@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Rajendra Nayak Cc: b-cousson@ti.com, patches@linaro.org, tony@atomide.com, devicetree-discuss@lists.ozlabs.org, linux-kernel@vger.kernel.org, grant.likely@secretlab.ca, shawn.guo@freescale.com, linux-omap@vger.kernel.org, lrg@ti.com, linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org On Thu, Oct 27, 2011 at 01:26:21PM +0530, Rajendra Nayak wrote: > v3 is based on the latest devicetree/next and is tested > (with twl adaptaions, which will be posted seperately) > on the OMAP4 panda and OMAP4 sdp boards. Looking at the device bindings I notice that these bindings loose the ability to assign a descriptive name to regulator outputs. This is really useful for making it easy to tie the code and the schematics together - you can make the runing system use the same name as the schematic.