lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Apr 2016 09:38:43 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	"Andrew F. Davis" <afd@...com>
Cc:	Jonathan Cameron <jic23@...nel.org>,
	Hartmut Knaack <knaack.h@....de>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Peter Meerwald <pmeerw@...erw.net>,
	Marc Titinger <mtitinger@...libre.com>,
	linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jean Delvare <jdelvare@...e.de>, linux-hwmon@...r.kernel.org
Subject: Re: [PATCH 1/1] iio: adc: Add driver for the TI INA3221 Triple
 Current/Voltage Monitor

On Mon, Apr 11, 2016 at 10:48:27AM -0500, Andrew F. Davis wrote:
> On 04/10/2016 06:57 AM, Jonathan Cameron wrote:
> > On 08/04/16 19:19, Andrew F. Davis wrote:
> >> The INA3221 is a three-channel, high-side current and bus voltage monitor
> >> with an I2C and SMBUS compatible interface.
> >>
> >> Signed-off-by: Andrew F. Davis <afd@...com>
> > Hi Andrew,
> > 
> > My immediate thought on this one is whether it would be better off in hwmon.
> > I'm not convinced either way from a quick glance at the data sheet, but the
> > question needs to be addressed.
> > 
> 
> I was on the fence with this also, I was leaning towards hwmod until I
> looked onto how the ina2xx driver has been ported to iio. This is almost
> the same part but the ina3x has three monitors vs one. In addition it
> looks like NVIDIA has written a hwmod driver for this part
> (https://github.com/Bogdacutu/STLinux-Kernel/blob/master/drivers/hwmon/ina3221.c)
> but then also ported it over to IIO (although doesn't appear to be
> upstream ready or ever has been submitted for such)
> (https://github.com/SuperPichu/shield-tablet-kernel/blob/master/drivers/staging/iio/meter/ina3221.c)
> So I figured this was the way things are moving, but I have no problem
> working this as a hwmod driver. The IIO work is already done here, I'll
> write the hwmod version also but keep working this, I see no reason we
> cant have both if needed. (unless using this and just using iio_hwmod.c
> if needed is more acceptable?)
> 

You can not have both since they would conflict with each other.
ina2xx has possibly created a bad precedent. I am not inclined to accept
a hwmon driver if an iio driver already exists. If you want an iio driver,
fine with me, but then you (and its users) will have to live with its
limitations when it comes to hardware monitoring.

I don't really mind if things are going all towards iio if that is where
the community wants to go. However, if that is the case, I would suggest
that someone should spend the time to define a clear sense of 'limits'
as well as alert handling in iio, in a way that is exportable to other
subsystems (hwmon and thermal come into mind).

Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ