linux-kernel - Re: [PATCH v2 3/3] iio: adc: Fix polling of INA219 conversion ready flag

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]

Message-ID: <1598491.c75bYYbHRJ@sbruens-linux>
Date:   Mon, 19 Jun 2017 18:24:56 +0000
From:   Brüns, Stefan <Stefan.Bruens@...h-aachen.de>
To:     Jonathan Cameron <jic23@...nel.org>, "afd@...com" <afd@...com>
CC:     "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Hartmut Knaack <knaack.h@....de>,
        Lars-Peter Clausen <lars@...afoo.de>,
        "Peter Meerwald-Stadler" <pmeerw@...erw.net>
Subject: Re: [PATCH v2 3/3] iio: adc: Fix polling of INA219 conversion ready
 flag

On Mittwoch, 24. Mai 2017 21:56:54 CEST Jonathan Cameron wrote:
> On Wed, 24 May 2017 20:53:35 +0100
> 
> Jonathan Cameron <jic23@...nel.org> wrote:
> > On Wed, 24 May 2017 02:09:07 +0200
> > 
> > Stefan Brüns <stefan.bruens@...h-aachen.de> wrote:
> > > While the INA226 has a conversion ready flag (CVRF) in the R/W
> > > Mask/Enable
> > > register with read-to-clear semantics, the corresponding bit of the
> > > INA219
> > > (CNVR) is part of the bus voltage register. The flag is cleared by
> > > reading
> > > the power register.
> > > 
> > > Signed-off-by: Stefan Brüns <stefan.bruens@...h-aachen.de>
> > 
> > Again, looks good to me, but I would like input form Marc or Andrew
> > who are more familiar with these devices than me!
> > 
> > Ping me in a week or two if nothing is happening and I look to have
> > lost these!
> 
> Ah Marc's old email is bouncing.  If no one has a more up to
> data address I guess we'll be looking at Andrew to have a chance to
> respond (which is more likely if I actually cc him ;)

Ping ;-)

Kind regards,

Stefan