Repository navigation
arm64: dts: exynos: google: zumapro-tegu: Add the MAX77779 charger - #161
Conversation
|
Thank you, @W4HO-ham. The node is small and right: 0x69 matches Google's What I checked: it merges cleanly onto today's Three small things:
On merging: this is the top of the stack from #85 through #119, whose own heads are older copies of the same patches. When #96 and #119 are ready I'll merge this one with "Rebase and merge" and close those as merged through it. omarchy-mobile#227 should land first or alongside. #105 will conflict with #119's |
|
Thanks. I changed the message for points 1 and 2: it now says "This node has no interrupt yet", and it has a paragraph saying the gauge waits on the charger through the The charge limit on that boot, through device-tegu's The phone-smoke: teguKernel
Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-audio 0.4.1-1, omamobile-device-tegu 0.2.1-1, omamobile-fingerprint 0.1.8-1, omamobile-firstboot 0.1.0-1, omamobile-gnss 0.2.5-1, omamobile-keyring 20261013-1, omamobile-mirror 0.1.1-1, omamobile-modem 0.1.4-1, omamobile-modem-sit 0.3.3-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-sensors 0.2.1-1, omamobile-shell 0.2.41-1, omarchy 4.0.6-1 |
7dbac6f to
644c02e
Compare
…C port controller The Pixel 9a's MAX77779 sits on hsi2c6 (USI6, pins gpp12-0/1, 950 kHz as stock): its fuel gauge at 0x36 with the board's 2 mOhm shunt, and its USB-C port controller at 0x25, interrupting on gpa8-3 (active low, as stock's max77759tcpc@25). The port is described as a sink with a dual data role and is not linked to the USB controller's role switch yet: the USB controller stays a peripheral, as today. gpa8 becomes an interrupt controller with its four EINT SPIs (44-47). Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
The MAX77779's charger answers at 0x69 on the same bus as its fuel gauge and USB-C port controller. Describe it, and name it as the fuel gauge's power supply, so the max77779-charger driver binds from the device tree and the battery reports charging through it. This node has no interrupt yet; the chip charges on its own, and the driver reports its state and offers charge inhibit. power-supplies is also a device link: the fuel gauge now waits for the charger to probe, so if the charger driver is missing or fails to probe, the battery stays deferred with it. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
|
Rebased onto today's |
644c02e to
a971fc5
Compare
|
Thank you, @W4HO-ham. The rebase changed nothing but the base: both commits are the same patches as With #96 in, I've merged this with "Rebase and merge". That lands #119's commit too (it's the same patch, with the same tree), so I'm closing #119 as merged through this one. #136 carries its own copy of that commit, so it needs a |
One commit on top of #119 (which sits on #96). It describes the MAX77779's charger at 0x69 on
hsi2c6, beside the fuel gauge and the USB-C port controller, and names it as the fuel gauge'spower-supplies, as the binding from #92 shows. The binding takes no interrupt or supplies. With this node the mergedmax77779_chargerbinds from the device tree, so the 9a can charge with a charge limit on the published driver.Tested on the palmtop today. The kernel was this branch at 7dbac6f, built with defconfig + omarchy-mobile's fragment + omarchy-mobile#227 (which turns on
BATTERY_MAX77779andCHARGER_MAX77779and builds in the USB/PMIC path), anduname -rwas7.3.0-rc6-omamobile-push1-g7dbac6f4e65c./sys/class/power_supply:max77779-battery,max77779-charger,tcpm-source-psy-1-0025. The charger's device is1-0069on drivermax77779-charger.charge_behaviour[auto] inhibit-charge, input current limit 500000, constant charge current 1933090. The battery was at capacity 89.inhibit-chargeabove the limit), the charger and the battery went to Not charging. With the limit removed andautowritten back, both went to Charging.tools/kernel-pr-checkagainst #119's head: signed off by the author, subject prefix,checkpatch --strictclean. The DTB built with no warnings.