[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <54882789.2010700@samsung.com>
Date: Wed, 10 Dec 2014 11:59:21 +0100
From: Sylwester Nawrocki <s.nawrocki@...sung.com>
To: Jacek Anaszewski <j.anaszewski@...sung.com>
Cc: Sakari Ailus <sakari.ailus@....fi>, linux-leds@...r.kernel.org,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
kyungmin.park@...sung.com, b.zolnierkie@...sung.com, pavel@....cz,
cooloney@...il.com, rpurdie@...ys.net, robh+dt@...nel.org,
pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
Andrzej Hajda <a.hajda@...sung.com>,
Lee Jones <lee.jones@...aro.org>,
Chanwoo Choi <cw00.choi@...sung.com>,
devicetree@...r.kernel.org
Subject: Re: [PATCH/RFC v9 06/19] DT: Add documentation for the mfd Maxim
max77693
On 10/12/14 11:02, Jacek Anaszewski wrote:
>>>> +Optional properties:
>>>> >>> +- maxim,fleds : Array of current outputs in order: fled1, fled2.
s/current outputs/LED current regulator outputs used/ ?
>>>> >>> + Note: both current outputs can be connected to a single led
s/led/LED ? And there seem to be other similar occurrences that would
need to be put in upper case.
>>>> >>> + Possible values:
>>>> >>> + MAX77693_LED_FLED_UNUSED - the output is left disconnected,
>>>> >>> + MAX77693_LED_FLED_USED - a diode is connected to the output.
As noted below, I would simply use 0/1 for these.
>>> >>
>>> >> As you have a LED sub-nodes for each LED already, isn't this redundant?
>> >
>> > Well, it seems so :)
>
> I agreed here recklessly. This property allows to describe the
> situation when one LED is connected to both outputs. Single sub-node
> can describe two type of designs: one LED connected to a single
> output or one LED connected to both outputs. Therefore additional
> property is needed to assess what is the actual case.
How about renaming "maxim,fleds" to "maxim,active-outputs" ?
And simply using 0 and 1 to indicate if one is used or not, rather
than defining macros for these true/false values ?
--
Regards,
Sylwester
--
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