New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 839123 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 807753
Owner: ----
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

cros_usbpd_charger: support "current_now"?

Project Member Reported by briannorris@chromium.org, May 2 2018

Issue description

https://buganizer.corp.google.com/issues/71489288#comment143

Noticed:
0502/133236:INFO:daemon.cc(796)] On AC (USB_PD, 0.000A at 4.3V, max 3.0A at 5.0V) with battery at 36% (displayed as 35%), 3.331/9.327Ah at 2.232A, 2h32m6s until full
[0502/133306:INFO:daemon.cc(796)] On AC (USB_PD, 0.000A at 4.3V, max 3.0A at 5.0V) with battery at 36% (displayed as 35%), 3.350/9.327Ah at 2.241A, 2h31m7s until full
[0502/133336:INFO:daemon.cc(796)] On AC (USB_PD, 0.000A at 4.3V, max 3.0A at 5.0V) with battery at 36% (displayed as 35%), 3.369/9.327Ah at 2.250A, 2h31m11s until full


Particularly, we're claiming 0A charging, which is confusing. I've seen the same on Kevin and Eve.

It looks like this is because powerd defaults to 0 for values it can't find in sysfs, and sysfs doesn't have this file because drivers/power/cros_usbpd-charger.c doesn't support it.

Should we support it?
 
Mergedinto: 807753
Status: Duplicate (was: Untriaged)
think we can dupe to here: crbug.com/807753

Sign in to add a comment