From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: <jic23@kernel.org>, <corbet@lwn.net>, <lars@metafoo.de>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 1/3] iio: adc: ina3221: Add DT binding details
Date: Fri, 3 Jun 2016 14:32:38 +0530 [thread overview]
Message-ID: <575147AE.30209@nvidia.com> (raw)
In-Reply-To: <20160603020759.GA23947@rob-hp-laptop>
On Friday 03 June 2016 07:37 AM, Rob Herring wrote:
> On Wed, Jun 01, 2016 at 06:04:12PM +0530, Laxman Dewangan wrote:
>> +
>> +enable-power-monitor: Boolean, Enable power monitoring of the device.
>> +
>> +enable-continuous-mode: Boolean. Device support oneshot and continuous
>> + mode for the channel data conversion. Presence
>> + of this property will enable the continuous
>> + mode from boot.
>> +
>> +enable-warning-alert: Boolean, Enable the alert signal when shunt
>> + current cross the warning threshold on any of
>> + the channel. Absence of this property will not
>> + enable the warning alert.
>> +
>> +enable-critical-alert: Boolean, Enable the alert signal when shunt
>> + current cross the critical threshold on any
>> + of the channel. Absence of this property will
>> + not enable the critical alert.
> Seems like these would be a user decision.
In some of platform, we want this to be from driver init itself. That's
why it is there.
But I will move this to sysfs if this is something user level policy.
WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Rob Herring <robh@kernel.org>
Cc: jic23@kernel.org, corbet@lwn.net, lars@metafoo.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/3] iio: adc: ina3221: Add DT binding details
Date: Fri, 3 Jun 2016 14:32:38 +0530 [thread overview]
Message-ID: <575147AE.30209@nvidia.com> (raw)
In-Reply-To: <20160603020759.GA23947@rob-hp-laptop>
On Friday 03 June 2016 07:37 AM, Rob Herring wrote:
> On Wed, Jun 01, 2016 at 06:04:12PM +0530, Laxman Dewangan wrote:
>> +
>> +enable-power-monitor: Boolean, Enable power monitoring of the device.
>> +
>> +enable-continuous-mode: Boolean. Device support oneshot and continuous
>> + mode for the channel data conversion. Presence
>> + of this property will enable the continuous
>> + mode from boot.
>> +
>> +enable-warning-alert: Boolean, Enable the alert signal when shunt
>> + current cross the warning threshold on any of
>> + the channel. Absence of this property will not
>> + enable the warning alert.
>> +
>> +enable-critical-alert: Boolean, Enable the alert signal when shunt
>> + current cross the critical threshold on any
>> + of the channel. Absence of this property will
>> + not enable the critical alert.
> Seems like these would be a user decision.
In some of platform, we want this to be from driver init itself. That's
why it is there.
But I will move this to sysfs if this is something user level policy.
next prev parent reply other threads:[~2016-06-03 9:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 12:34 [PATCH 1/3] iio: adc: ina3221: Add DT binding details Laxman Dewangan
2016-06-01 12:34 ` Laxman Dewangan
2016-06-01 12:34 ` [PATCH 2/3] iio: adc: ina3221: Add support for IIO ADC driver for TI INA3221 Laxman Dewangan
2016-06-01 12:34 ` Laxman Dewangan
2016-06-03 10:06 ` Jonathan Cameron
2016-06-03 10:16 ` Jonathan Cameron
2016-06-03 11:31 ` Laxman Dewangan
2016-06-03 11:31 ` Laxman Dewangan
2016-06-03 12:04 ` Jonathan Cameron
2016-06-03 12:04 ` Jonathan Cameron
2016-06-03 12:03 ` Laxman Dewangan
2016-06-03 12:03 ` Laxman Dewangan
2016-06-03 11:26 ` Laxman Dewangan
2016-06-03 11:26 ` Laxman Dewangan
2016-06-03 12:09 ` Jonathan Cameron
2016-06-03 12:17 ` Laxman Dewangan
2016-06-03 12:17 ` Laxman Dewangan
2016-06-03 13:29 ` Guenter Roeck
2016-06-03 14:14 ` Laxman Dewangan
2016-06-03 14:14 ` Laxman Dewangan
2016-06-03 15:17 ` Andrew F. Davis
2016-06-03 15:17 ` Andrew F. Davis
2016-06-07 22:30 ` Guenter Roeck
2016-06-08 15:04 ` Andrew F. Davis
2016-06-08 15:04 ` Andrew F. Davis
2016-06-08 15:37 ` Laxman Dewangan
2016-06-08 15:37 ` Laxman Dewangan
2016-06-01 12:34 ` [PATCH 3/3] iio: adc: ina3221: Add sysfs details " Laxman Dewangan
2016-06-01 12:34 ` Laxman Dewangan
2016-06-03 10:26 ` Jonathan Cameron
2016-06-03 2:07 ` [PATCH 1/3] iio: adc: ina3221: Add DT binding details Rob Herring
2016-06-03 2:07 ` Rob Herring
2016-06-03 9:02 ` Laxman Dewangan [this message]
2016-06-03 9:02 ` Laxman Dewangan
2016-06-03 10:19 ` Jonathan Cameron
2016-06-03 10:19 ` Jonathan Cameron
2016-06-03 11:48 ` Laxman Dewangan
2016-06-03 11:48 ` Laxman Dewangan
2016-06-03 12:11 ` Jonathan Cameron
2016-06-03 12:21 ` Laxman Dewangan
2016-06-03 12:21 ` Laxman Dewangan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=575147AE.30209@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.