[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <42c00dfb-bb45-405c-a1d2-516ece137826@kernel.org>
Date: Fri, 3 Jun 2016 13:04:53 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>, robh+dt@...nel.org,
corbet@....net, lars@...afoo.de
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-iio@...r.kernel.org,
linux-hwmon@...r.kernel.org, Jean Delvare <khali@...ux-fr.org>,
Guenter Roeck <linux@...ck-us.net>
Subject: Re: [PATCH 2/3] iio: adc: ina3221: Add support for IIO ADC driver for
TI INA3221
On 03/06/16 12:31, Laxman Dewangan wrote:
>
> On Friday 03 June 2016 03:46 PM, Jonathan Cameron wrote:
>> On 03/06/16 11:06, Jonathan Cameron wrote:
>>>
>>> Code looks good, bu these more fundamental bits need sorting.
>> Another minor point - why do the power calculations in driver?
>> no hardware support for it, so why not just leave it to userspace?
>
> Device supports the bus and shunt voltage monitoring. So even no current. Also the warning/critical limit is for the voltage across shunt.
>
> So should we only expose the shunt/bus voltage, no power/current?
>
> I am thinking that user space should not know the platform and hence shunt resistance and so exposing the current and power on bus is better option.
>
I'd go for current and voltage rather than current and power, but
otherwise agree.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists