From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758883Ab2FUOuu (ORCPT ); Thu, 21 Jun 2012 10:50:50 -0400 Received: from moutng.kundenserver.de ([212.227.17.10]:49701 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755192Ab2FUOut (ORCPT ); Thu, 21 Jun 2012 10:50:49 -0400 From: Arnd Bergmann To: Mark Brown Subject: Re: [PATCH V3 2/3] regulator: dt: regulator match by regulator-compatible Date: Thu, 21 Jun 2012 14:50:35 +0000 User-Agent: KMail/1.12.2 (Linux/3.5.0-rc1+; KDE/4.3.2; x86_64; ; ) Cc: Stephen Warren , Laxman Dewangan , lrg@ti.com, rob.herring@calxeda.com, grant.likely@secretlab.ca, linus.walleij@linaro.org, lee.jones@linaro.org, devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org References: <1340194987-23654-1-git-send-email-ldewangan@nvidia.com> <4FE23A1B.2000809@wwwdotorg.org> <20120620233507.GC4037@opensource.wolfsonmicro.com> In-Reply-To: <20120620233507.GC4037@opensource.wolfsonmicro.com> MIME-Version: 1.0 Message-Id: <201206211450.35713.arnd@arndb.de> Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:xafuBZry9o0Od0UZxac07uermq+iMZGoefOVh19PFxa AQ4b1Ob0KA0yDncCZg7LYFsG4/xT5J0RyPrC/j/6Ho947eMpZE iKacKLrdn5XcWKUcx8s+yWuYXzFXNZX7uuSqfuyCRjLlIL2oqp B0R0Xy5fJnH4LCbiyABNZMnLvEu3KO6AU0+3wafOdB5BJVVRFn VA2IlZ9q9Uuv4NGH9z9Si248imurY/ifrN2NIj/xhkQ78mYB5O GAPv0xq26xmGCYGymfPyAhIFTPt0EfyS95n//0GNswvBcHFM+1 Lsj57ZEC9sZIFxcQUFs1Pp3xAqDT2Xd7KFboAH6iWV3iKC254e ISxJmvecPA+VcRrvvzvA= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 20 June 2012, Mark Brown wrote: > On Wed, Jun 20, 2012 at 03:01:15PM -0600, Stephen Warren wrote: > > The problem is that dtc has no named constants. Using raw integers > > instead of names would make the .dts file rather unreadable. The issue > > is much more accute for regulators than say GPIOs or IRQs because > > there's likely no relative order to the set of regulators defined by the > > documentation, unlike for GPIOs/IRQs where the integer (often) is the > > object's primary ID. > > Well, there are actually a lot of chips which do provide useful indexes > - for example the wm831x devices just have a bunch of DCDCs and a bunch > of LDOs which can usefully be referred to as DCDCn or LDOn. They will > hopefully not need to use this interface. It's just that there's also a > large class of devices we need to cater for which don't have any such > regularity in their register map, this biding > mechanism is for them. Ok, now it all makes sense. Thanks for bearing with me being a little slow on this topic. It seems that the drivers that are changed to use this could also try to describe the individual regulators completely, by moving the contents of e.g. ab8500_regulator_info into the device tree, but having the string identifier with an in-kernel table makes sense when there is only one such table. Arnd