Slackware inside Pandora.


I don't know if the battery can charge, I have a lot of:
Code:
bq27xxx_battery_setup
bq27xxx_battery_setup: dm_regs=00000000
bq27xxx_battery_settings
bq27xxx_battery_settings: power_supply_get_battery_info failed ret=0

A lot of these:
power_supply bq27000-battery: driver failed to report `status' property: -1
power_supply bq27000-battery: uevent: failed to send synthetic uevent: -1
...
 
I don't know if the battery can charge, I have a lot of:
Code:
bq27xxx_battery_setup
bq27xxx_battery_setup: dm_regs=00000000
bq27xxx_battery_settings
bq27xxx_battery_settings: power_supply_get_battery_info failed ret=0

A lot of these:
power_supply bq27000-battery: driver failed to report `status' property: -1
power_supply bq27000-battery: uevent: failed to send synthetic uevent: -1
...
This can be ignored. There is only a bq27500 fuel gauge inside the Pandora and the bq27000 is reported wrongly by a kernel bug.

This is a design flaw in the omap3 device tree where the HDQ driver is enabled by default. Even if it is not wired up physically. And the HDQ driver assumes that there is a potentially removable bq27000 battery fuel gauge (e.g. for omap3 based Nokia or OpenMoko devices). So even on a Pandora this creates a /sys/class/power_supply/bq27000 in anticipatory obedience...
This has been fixed in the latest Letux kernels (e.g. letux-6.12.37).

The "driver failed to report `status' property: -1" is a different bug which has been submitted for upstream Linux: https://patchew.org/linux/bc405a6f782792dc41e01f9ddf9eadca3589fcdc.1753101969.git.hns@goldelico.com/.

So for monitoring charging activity, please look at /sys/class/power_supply/bq27500-1-0/status.
And/or /sys/class/power_supply/twl4030_ac/status resp. cat /sys/class/power_supply/twl4030_usb/status
Post automatically merged:

Another thing: my usb <-> ethernet adapters don't work on the 1GHz. Nothing happens in the syslogs when I plug them. Works fine on the CC 600MHz. I'll check that in detail later.
Unfortunately I have no 1GHz Pandora to test or debug such issues.
Post automatically merged:

Ok, because I see strange things on both my 1GHz and CC 600MHz.
When I charge with the AC adapter, as soon as the Pandora OS goes screen blank, charge stops.
Also, when the units are off, when I plug the AC, they don't wake up. Before, they self-powered on as soon as AC delivered power.
Hm. Such charging behavior may come from user-space helper code.
The question is what you mean by "units are off". Screen blanked? Suspended to RAM? Really powered off (like poweroff in the boot menu). Each state has different triggers for wakeup.
 
Last edited:
Linux-SWAT said:
Ok, because I see strange things on both my 1GHz and CC 600MHz.
When I charge with the AC adapter, as soon as the Pandora OS goes screen blank, charge stops.
Also, when the units are off, when I plug the AC, they don't wake up. Before, they self-powered on as soon as AC delivered power.
Hm. Such charging behavior may come from user-space helper code.
The question is what you mean by "units are off". Screen blanked? Suspended to RAM? Really powered off (like poweroff in the boot menu). Each state has different triggers for wakeup.
Totally off.
Post automatically merged:

After
Code:
 cpufreq-set -g performance
I get
Code:
                  The governor "performance" may decide which speed to use
                  within this range.
 current CPU frequency is 600 MHz (asserted by call to hardware).
I guess that more battery will be drained ?
Post automatically merged:

Thanks for your answers, btw.
 
Oh, I can't use 1GHz on my 1GHz !!!

Code:
# cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 300 us.
  hardware limits: 300 MHz - 800 MHz
  available frequency steps: 300 MHz, 600 MHz, 800 MHz
  available cpufreq governors: conservative, ondemand, userspace, powersave, performance
  current policy: frequency should be within 300 MHz and 800 MHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 300 MHz:82.89%, 600 MHz:3.10%, 800 MHz:14.01%, 1000 MHz:0.00%  (1285)

BTW, what happened to the OPPs ? Operating points. They are now handled by the governors ?
 
Last edited:
Back
Top