From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH/RFC v10 03/19] DT: leds: Add led-sources property Date: Tue, 20 Jan 2015 18:40:10 +0100 Message-ID: <20150120174010.GA2900@amd> References: <54B3F1EF.4060506@samsung.com> <54B4DA81.7060900@samsung.com> <54B8D4D0.3000904@samsung.com> <54B933D0.1090004@samsung.com> <54BE7DAB.80702@samsung.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring Cc: Jacek Anaszewski , linux-leds@vger.kernel.org, "linux-media@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , Kyungmin Park , Bartlomiej Zolnierkiewicz , Bryan Wu , Richard Purdie , sakari.ailus@iki.fi, Sylwester Nawrocki , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Liam Girdwood , Mark Brown List-Id: devicetree@vger.kernel.org On Tue 2015-01-20 11:29:16, Rob Herring wrote: > On Tue, Jan 20, 2015 at 10:09 AM, Jacek Anaszewski > wrote: > > On 01/16/2015 04:52 PM, Jacek Anaszewski wrote: > >> > >> On 01/16/2015 02:48 PM, Rob Herring wrote: > > [...] > > >>> You may want to add something like led-output-cnt or led-driver-cnt in > >>> the parent so you know the max list size. > >> > >> > >> Why should we need this? The number of current outputs exposed by the > >> device is fixed and can be specified in a LED device bindings > >> documentation. > >> > > > > OK. The led-output-cnt property should be put in each sub-node, as the > > number of the current outputs each LED can be connected to is variable. > > Sorry, I meant this for the parent node meaning how many outputs the > driver IC has. I did say maybe because you may always know this. It > can make it easier to allocate memory for led-sources knowing the max > size up front. Umm. Not sure if that kind of "help" should go to the device tree. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html