Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Fri, 6 Jul 2018 13:16:28 +0200
From:   Sebastian Reichel <sebastian.reichel@collabora.co.uk>
To:     Pavel Machek <pavel@ucw.cz>
Cc:     Ladislav Michl <ladis@linux-mips.org>,
        kernel list <linux-kernel@vger.kernel.org>,
        linux-pm@vger.kernel.org,
        linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
        linux-omap@vger.kernel.org, tony@atomide.com, nekit1000@gmail.com,
        mpartap@gmx.net, merlijn@wizzup.org
Subject: Re: droid 4: connection refused from voltage_now
Message-ID: <20180706111628.mvh46mg6ctqia3iz@earth.universe>
References: <20180704171156.GA3158@amd>
 <20180704194556.GA9189@lenoch>
 <20180704195238.GA13932@amd>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="twaias67dfwhto4x"
Content-Disposition: inline
In-Reply-To: <20180704195238.GA13932@amd>
User-Agent: NeoMutt/20180512
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


--twaias67dfwhto4x
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Jul 04, 2018 at 09:52:38PM +0200, Pavel Machek wrote:
> On Wed 2018-07-04 21:45:56, Ladislav Michl wrote:
> > On Wed, Jul 04, 2018 at 07:11:56PM +0200, Pavel Machek wrote:
> > > Hi!
> > >=20
> > > I started to use droid 4 as my primary phone... so I have battery
> > > monitor running for hours... Once every few days it dies with
> > > "connection refused" error reading battery's "voltage_now". I restart
> > > it and it continues working...
> >=20
> > Ha! What exactly that "connection refused" means? Is it ECONNREFUSED (1=
11)?
> > I have custom at91 based board here with few custom power supply drivers
> > and it sometimes ends with voltage_now of my driver being unreadable.
> > (I modified userspace code and waiting what's in errno in case
> > reading fails)
>=20
> It seems to be -110:
> Jul  4 11:48:29 devuan kernel: [ 2908.602600] cpcap_adc cpcap_adc.0: erro=
r reading ADC: -110
> Jul  4 11:48:29 devuan kernel: [ 2908.608123] cpcap_battery cpcap_battery=
=2E0: cpcap_battery_get_current failed: -110
> Jul  4 11:48:30 devuan kernel: [ 2908.922576] cpcap_adc cpcap_adc.0: erro=
r reading ADC: -110
> Jul  4 11:48:30 devuan kernel: [ 2908.928100] cpcap_battery cpcap_battery=
=2E0: cpcap_charger_battery_temperature failed: -110
> Jul  4 11:48:30 devuan kernel: [ 2908.936340] power_supply battery: drive=
r failed to report `voltage_now' property: -110

The error above is obviously generated by cpcap_adc and only
propageted by cpcap_battery. Have a look for -ETIMEDOUT (-110)
in drivers/iio/adc/cpcap-adc.c.

-- Sebastian

--twaias67dfwhto4x
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAls/T4kACgkQ2O7X88g7
+pqm2BAAlvgPwUmd7FVXUfz9UxlwU+TIq2+FYiiO3zKdFJJDzntBDefAmdZn+kAU
mEwsuQKcOC1buhWj/Qte2/QChtZHHOQOYNjEyR2SnzGZ23NDRc21Zte8uvXzH1hl
bEiwGf0NDYYxyWPr4M+MdVQ8vmgSrwZo9YNtqU2j/xV6DMmU9fLjvFhzBKjD/dL2
U8ZW10k9e1SzONVdytcr68aKFv1VHzt3dqVzONcgGJqttWJeckO+rul8eCuhp183
jILyUS0m97KfCBhVI3dav7sgvYQEOCg4DzqRjNV1c6nyTpDNHS2ThRrIA/4jOfvz
73v5DJKkmcDLwEBA3b30msgoSf9QX24r5gdbQMJ2RPgO0eGuiufabTMZl3NTZJym
MMpNgDQv8NIEWgVIQ2sf28ye+pVAEO6C5xx57dJltiQEuK20ZYRMvHr7JPQXmTCD
Q2UJ/y5CDGgfXM9+C2V+oiBwns58HCMgXtkiIEGpjlnh4ZvBvJ73XiIvLoMy9fPn
CkPFKlvc0uWTz9VMeAEmUXu7XQrUbAWUntUxyibm7Mj8s8tSa0WbaAW/vWWCK7E8
PVB18HGA1kzW4NGGuZ6dGAqvIQEg01fRtqjOsYx/QCh2oQp7VaP3YEX/gYfN8gUH
x40BKXCF9P6ly5zTN9TB5YFItmjzG8dJPHGI523+i1yusMdMOLs=
=olpt
-----END PGP SIGNATURE-----

--twaias67dfwhto4x--