[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568F51FF.7000102@nvidia.com>
Date: Fri, 8 Jan 2016 11:36:55 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Rob Herring <robh@...nel.org>
CC: <pawel.moll@....com>, <mark.rutland@....com>,
<ijc+devicetree@...lion.org.uk>, <galak@...eaurora.org>,
<linus.walleij@...aro.org>, <gnurou@...il.com>,
<lee.jones@...aro.org>, <broonie@...nel.org>,
<a.zummo@...ertech.it>, <alexandre.belloni@...e-electrons.com>,
<lgirdwood@...il.com>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-gpio@...r.kernel.org>,
<rtc-linux@...glegroups.com>, <swarren@...dia.com>,
<treding@...dia.com>
Subject: Re: [PATCH 1/6] DT: mfd: add device-tree binding doc fro PMIC max77620/max20024
Thanks Rob for review.
I have taken care of all comment except following which I have query.
On Friday 08 January 2016 04:42 AM, Rob Herring wrote:
> + - maxim,low-battery-reset-enable: Enable low battery reset.
> + - maxim,low-battery-reset-disable: Disable low battery reset.
> Why not boolean? Not present means keep default value? I'd prefer
> boolean or tristate of not present, 0 to disable, or 1 to enable.
>
>
Here, the properties are boolean. I will add this on the description.
I like to enable or disable with the DT and properties are not there
then left to default.
So added two properties for enable and disable. If properties are there,
do the activity.
Here tristate is also possible:
maxim,low-battery-reset: tristate, low battery reset control. 0 for
disable, 1 for enable and
absence of this will leave
configuration on default.
Does it look fine?
Powered by blists - more mailing lists