From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
Cc: Pavel Machek <pavel@ucw.cz>,
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, nekit1000@gmail.com, mpartap@gmx.net,
merlijn@wizzup.org
Subject: Re: droid 4: connection refused from voltage_now
Date: Fri, 6 Jul 2018 04:23:15 -0700 [thread overview]
Message-ID: <20180706112315.GD112168@atomide.com> (raw)
In-Reply-To: <20180706111628.mvh46mg6ctqia3iz@earth.universe>
* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [180706 11:19]:
> 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!
> > > >
> > > > 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...
> > >
> > > Ha! What exactly that "connection refused" means? Is it ECONNREFUSED (111)?
> > > 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)
> >
> > It seems to be -110:
> > Jul 4 11:48:29 devuan kernel: [ 2908.602600] cpcap_adc cpcap_adc.0: error reading ADC: -110
> > Jul 4 11:48:29 devuan kernel: [ 2908.608123] cpcap_battery cpcap_battery.0: cpcap_battery_get_current failed: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.922576] cpcap_adc cpcap_adc.0: error reading ADC: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.928100] cpcap_battery cpcap_battery.0: cpcap_charger_battery_temperature failed: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.936340] power_supply battery: driver 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.
Hmm yeah maybe first try to increase the timeout value a bit
and see if that helps.
If increasing the timeout does not help, try reverting commit
9d965236fe9b ("iio: adc: cpcap: Remove hung interrupt quirk").
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: droid 4: connection refused from voltage_now
Date: Fri, 6 Jul 2018 04:23:15 -0700 [thread overview]
Message-ID: <20180706112315.GD112168@atomide.com> (raw)
In-Reply-To: <20180706111628.mvh46mg6ctqia3iz@earth.universe>
* Sebastian Reichel <sebastian.reichel@collabora.co.uk> [180706 11:19]:
> 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!
> > > >
> > > > 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...
> > >
> > > Ha! What exactly that "connection refused" means? Is it ECONNREFUSED (111)?
> > > 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)
> >
> > It seems to be -110:
> > Jul 4 11:48:29 devuan kernel: [ 2908.602600] cpcap_adc cpcap_adc.0: error reading ADC: -110
> > Jul 4 11:48:29 devuan kernel: [ 2908.608123] cpcap_battery cpcap_battery.0: cpcap_battery_get_current failed: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.922576] cpcap_adc cpcap_adc.0: error reading ADC: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.928100] cpcap_battery cpcap_battery.0: cpcap_charger_battery_temperature failed: -110
> > Jul 4 11:48:30 devuan kernel: [ 2908.936340] power_supply battery: driver 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.
Hmm yeah maybe first try to increase the timeout value a bit
and see if that helps.
If increasing the timeout does not help, try reverting commit
9d965236fe9b ("iio: adc: cpcap: Remove hung interrupt quirk").
Regards,
Tony
next prev parent reply other threads:[~2018-07-06 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 17:11 droid 4: connection refused from voltage_now Pavel Machek
2018-07-04 17:11 ` Pavel Machek
2018-07-04 19:45 ` Ladislav Michl
2018-07-04 19:45 ` Ladislav Michl
2018-07-04 19:52 ` Pavel Machek
2018-07-04 19:52 ` Pavel Machek
2018-07-06 11:16 ` Sebastian Reichel
2018-07-06 11:16 ` Sebastian Reichel
2018-07-06 11:23 ` Tony Lindgren [this message]
2018-07-06 11:23 ` Tony Lindgren
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=20180706112315.GD112168@atomide.com \
--to=tony@atomide.com \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=pavel@ucw.cz \
--cc=sebastian.reichel@collabora.co.uk \
/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.