Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #63870 > unrolled thread

Bug#927163: linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel gauge driver

Back to article view | Back to linux.debian.kernel

Contents

  Bug#927163: linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel gauge driver Marcus Lundblad <ml@update.uu.se> - 2019-04-15 21:30 +0200
    Bug#927163: linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel gauge driver Bernhard Übelacker <bernhardu@mailbox.org> - 2019-04-18 12:10 +0200

#63870 — Bug#927163: linux-image-4.19.0-4-amd64: Missing modules for AXP288 power fuel gauge driver

Package: src:linux
Version: 4.19.28-2
Severity: wishlist

Dear Maintainer,

In #895129 axp288_fuel_gauge was included as a module for x86 platforms.
After that the battery icon was actually showing on my Cherrytrail tablet.
But since then, this has again stopped working (and I'm not sure it was
actually reporting a correct state), and also it never detected the AC power
being connected. I believe there are still some missing stuff to get this
working.

Looking at a commit for ARM I can see this:
https://salsa.debian.org/kernel-team/linux/commit/0138e6bc4eedd8c10ad637e742a4fe6c625c6def

There seems to be some additional things in there.

AXP20X_ADC, CHARGER_AXP20X, BATTERY_AXP20X, GPIO_AXP209,
AXP288_CHARGER, EXTCON_AXP288, AXP288_ADC

Also, looking at the kernel source, there seems to be a case where
the axp288_fuel_gauge module waits for axp288_adc to load (this module
is currently not built for x86):

https://github.com/torvalds/linux/blob/dc4060a5dc2557e6b5aa813bf5b73677299d62d2/drivers/power/supply/axp288_fuel_gauge.c#L774

This probing code was appearantly added late 2017 (so, possibly that code
wasn't in the kernel that was first released in Debian with the
axp288_fuel_gauge module on x86, which might possibly explain why I saw
the inaccurate reading (I recall it always reporting 100%).

Thanks,
//Marcus

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=sv_SE.utf8, LC_CTYPE=sv_SE.utf8 (charmap=UTF-8), LANGUAGE=sv_SE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-4-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133
ii  kmod                                    26-1
ii  linux-base                              4.6

Versions of packages linux-image-4.19.0-4-amd64 recommends:
ii  apparmor             2.13.2-10
ii  firmware-linux-free  3.4
ii  irqbalance           1.5.0-3

Versions of packages linux-image-4.19.0-4-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.02+dfsg1-16
pn  linux-doc-4.19          <none>

Versions of packages linux-image-4.19.0-4-amd64 is related to:
ii  firmware-amd-graphics     20190114-1
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20190114-1
ii  firmware-misc-nonfree     20190114-1
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- debconf-show failed

[toc] | [next] | [standalone]

#63890

Hello Marcus Lundblad,
I don't know if it is related - I own a Baytrail
device that contains also these axp devices.
Back in late 2017 I got some help from Hans de Goede,
who worked that time in that area.
There my battery information was also missing with
the stock debian kernel.

He suggested to build a kernel with the config from a
"v4.14-footrail" branch from following repo first.
     https://github.com/jwrdegoede/linux-sunxi/

I could reduce the differences to following:

#        Note on x86 this provides an ACPI OpRegion, so this must be 'y'
#        (builtin) and not a module, as the OpRegion must be available as
#        soon as possible. For the same reason the I2C bus driver options
#        I2C_DESIGNWARE_PLATFORM and I2C_DESIGNWARE_BAYTRAIL must be 'y' too.
#    I2C_DESIGNWARE_PLATFORM=y
#    I2C_DESIGNWARE_BAYTRAIL=y
#    MFD_AXP20X_I2C=y

Could this be relevant for Cherrytrail too?

Kind regards,
Bernhard

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web