krzk changed the topic of #linux-exynos to: Linux Samsung SoC Exynos | https://exynos.wiki.kernel.org | This channel is logged: https://libera.irclog.whitequark.org/linux-exynos
psydroid has joined #linux-exynos
antoine62[m] has joined #linux-exynos
AntoniAloyTorren has joined #linux-exynos
mszyprow has joined #linux-exynos
cmeerw has joined #linux-exynos
cmeerw has quit [Ping timeout: 272 seconds]
mszyprow has quit [Read error: Connection reset by peer]
Peng_Fan has quit [Quit: Connection closed for inactivity]
rando25902 has quit [Quit: leaving]
<Grimler> Hi, @krzk after 7fbf6b731b ("power: supply: max17042: Do not enforce (incorrect) interrupt trigger type") and 8a45f33bd3 ("ARM: dts: exynos: correct fuel gauge interrupt trigger level on Midas family") I am seeing lots of "max17042 12-0036: SOC threshold INTR" messages on exynos4412-i9300.
<Grimler> Changing back to `IRQ_TYPE_EDGE_FALLING` for i930{0,5} (in exynos4412-galaxy-s3.dtsi) works to silence the message. Would this be an acceptable patch or should this be fixed, properly, somewhere else?
cmeerw has joined #linux-exynos
<krzk> Grimler: if the interrupt level is edge, such patch would be good, but interrupt is not edge, AFAIK :)
<krzk> Therefore this should be fixed differently.
<krzk> Or rather - real cause should be found.
short-bike has joined #linux-exynos
<krzk> Grimler: interrupt line should be pulled by external resistor, so it might mean that fuel gauge is reporting error all the time
short-bike has left #linux-exynos [and on that note...]
<krzk> Grimler: if you boot with my patch reverted, what is visible in "grep . /sys/class/power_supply/*/*"?
<krzk> Grimler: can you try following patch and report what it prints?
<krzk> Grimler: I wonder why the interrupt happens - DTS should be correct so I suspect the fuel gauge
<Grimler> Here's the grep output: https://paste.sr.ht/~grimler/1f2de17f3adda24af3979edcaae354c244860019, AAA debug output and full dmesg
<Grimler> @krzk The max17042 and/or max77693 driver could be improved for i9300, charging does not work and the battery percentage is not reported correctly (the latter seem to be fixable with https://github.com/Midas-Mainline/android_kernel_samsung_smdk4412/commit/1287ea6219ef4ebc461214e67d6b98ee99023b3e)
<Viciouss> @krzk @Grimler it's the same for the n8010, I also noticed all the messages after the patch
<Viciouss> the vendor kernel has IRQF_TRIGGER_FALLING set in the config
<Grimler> Viciouss: I guess it is the same on i9100 then as well
<Grimler> > he vendor kernel has IRQF_TRIGGER_FALLING set
<Grimler> Could you link to where this is set? I failed to find the related code on downstream kernel for i9300
cmeerw has quit [Ping timeout: 272 seconds]