[Letux-kernel] Charging on GTA04

[H. Nikolaus Schaller]

Hi Marek,

> Am 27.06.2016 um 22:41 schrieb Belisko Marek <marek.belisko at gmail.com>:
> 
> Hi Nikolaus,
> 
> On Mon, Jun 27, 2016 at 10:35 PM, H. Nikolaus Schaller
> <hns at goldelico.com> wrote:
>> Hi Marek,
>> 
>>> Am 27.06.2016 um 22:26 schrieb Belisko Marek <marek.belisko at gmail.com>:
>>> 
>>> Hi Nikolaus,
>>> 
>>> I build fresh 4.7-rc5-letux (make mrproper ARCH=arm; make
>>> letux_defconfig ARCH=arm) boot device and twl4030_usb is reporting:
>>> root at letux:~# cat /sys/class/power_supply/twl4030_usb/status
>>> Charging
>>> root at letux:~# cat /sys/class/power_supply/twl4030_usb/voltage_now
>>> 4961175
>>> root at letux:~# cat /sys/class/power_supply/twl4030_usb/current_now
>>> 509352
>> 
>> looks good!
>> 
>>> 
>>> genric-adc-battery has bug that despite of fact that twl4030 report
>>> charging generic adc-batt report discharging.
>> 
>> Yes, but that is not the real problem.
> I think I know what the problem is but need to look for solution ;)

Fine!

>> 
>>> Also eth gadget works
>>> for me. Strange.
>> 
>> Indeed. Hm...
>> 
>> The strange thing is that it does not work for me for 4.6.0 or 4.7-rc*
>> But 4.3 worked immediately.
>> 
>> Well, does WiFi work for you? On my devices it is broken. And that
>> might disturb something.
> Yes wifi is up and running.
> root at letux:~# ifconfig -a
> lo        Link encap:Local Loopback
>          inet addr:127.0.0.1  Mask:255.0.0.0
>          inet6 addr: ::1/128 Scope:Host
>          UP LOOPBACK RUNNING  MTU:65536  Metric:1
>          RX packets:160 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1
>          RX bytes:15200 (14.8 KiB)  TX bytes:15200 (14.8 KiB)
> 
> usb0      Link encap:Ethernet  HWaddr 52:1d:8d:38:91:ad
>          inet addr:192.168.0.202  Bcast:192.168.0.255  Mask:255.255.255.0
>          inet6 addr: fe80::501d:8dff:fe38:91ad/64 Scope:Link
>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 B)  TX bytes:544 (544.0 B)
> 
> wlan0     Link encap:Ethernet  HWaddr 00:19:88:15:bd:c8
>          BROADCAST MULTICAST  MTU:1500  Metric:1
>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>          collisions:0 txqueuelen:1000
>          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Ok. It is interesting that on all my devices wifi is broken.
So the theory that it disturbs charging might be true.

I have not yet tried to remove the libertas drivers completely and evaluate the
boot process in that case.

> 
>> 
>> And does HDQ / bq27000 work for you?
> bq2700 seems to be broken:
> cat /sys/class/power_supply/bq27000-battery/*
> cat: /sys/class/power_supply/bq27000-battery/capacity: No such device
> cat: /sys/class/power_supply/bq27000-battery/capacity_level: No such device
> cat: /sys/class/power_supply/bq27000-battery/charge_full: No such device
> cat: /sys/class/power_supply/bq27000-battery/charge_full_design: No such device
> cat: /sys/class/power_supply/bq27000-battery/charge_now: No such device
> cat: /sys/class/power_supply/bq27000-battery/current_now: No such device
> cat: /sys/class/power_supply/bq27000-battery/cycle_count: No such device
> cat: /sys/class/power_supply/bq27000-battery/device: Is a directory
> cat: /sys/class/power_supply/bq27000-battery/energy_now: No such device
> cat: /sys/class/power_supply/bq27000-battery/health: No such device
> cat: /sys/class/power_supply/bq27000-battery/manufacturer: No such device
> cat: /sys/class/power_supply/bq27000-battery/power: Is a directory
> cat: /sys/class/power_supply/bq27000-battery/power_avg: No such device
> 0
> cat: /sys/class/power_supply/bq27000-battery/status: No such device
> cat: /sys/class/power_supply/bq27000-battery/subsystem: Is a directory
> cat: /sys/class/power_supply/bq27000-battery/technology: No such device
> cat: /sys/class/power_supply/bq27000-battery/temp: No such device
> cat: /sys/class/power_supply/bq27000-battery/time_to_empty_avg: No such device
> cat: /sys/class/power_supply/bq27000-battery/time_to_empty_now: No such device
> cat: /sys/class/power_supply/bq27000-battery/time_to_full_now: No such device
> Battery
> POWER_SUPPLY_NAME=bq27000-battery
> POWER_SUPPLY_PRESENT=0
> cat: /sys/class/power_supply/bq27000-battery/voltage_now: No such device
> 
> not sure how to verify hdq.

I have added some printk and enabled DEBUG in omap_hdq and other places
and I see hdq rx timeouts. Needs further debugging.

> 
> BR,
> 
> marek

BR,
Nikolaus