Repository navigation
omamobile-device-panther: the charger's policy and the MAX77759 blacklist - #827
Conversation
…list Ship the two modprobe files the Pixel 7 has run with since BATTERY-PLAN D1 (2026-11-01), ahead of the pmic@66 node that lets the charger bind (linux-omarchy-mobile#259): the charger loads at boot with the Pixel 7 Pro's options, a 500 mA input limit without a Type-C source (default_ilim_ua; without it the upstream driver turns charging off at probe) and stock's temperature bands (temp_guard), after the gauge; tcpci_maxim, which would take the USB-C port used for SSH, and the GPIO and NVMEM cells stay blacklisted. Without the node nothing of the PMIC binds and the files change nothing, so this goes first. With it, the charger charges to 4.45 V instead of the bootloader's 4.35 V. The test checks both options together, the gauge first, and the blacklist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, Alejandro, for the quick split. This is exactly the small, inert piece I hoped for. I checked it against the Pixel 7 Pro's files: the charger's two option lines are the 7 Pro's byte for byte, and the blacklist adds One thing before I merge: the version. The package changes while A suggestion for the same push, not a condition: the README row and the file comment point at BATTERY-PLAN's gates B3.3, B3g and D1, but those gates are in #788's plan commit, and #788 lands last, after the kernel. If you move that commit ( After this is merged, the next morning's development publish puts it on phones, and then I'll take #259. |
derekross#577 takes 0.1.16. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The charger step after the Pixel 7 Pro's USB-C-PLAN B3 and B3g: what it gains (charging to 4.45 V instead of ABL's 4350 mV, a 0.3 C fast-charge cap and stock's temperature bands) and what it doesn't (the input stays at 500 mA until Type-C), the facts it rests on (ABL's charger settings read in B3.0, stock's bands matching the guard's tables, the PMIC's interrupt pin), and gates B3.1 to D1, each with its Pass, Stop and Rollback, as asked on derekross#247. B3.1 to B3.3, B3g and D1 passed on 2026-11-01; the results are recorded below them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you. Pushed on top, without rewriting the first commit:
#788 is now the off-mode commit alone. 🤖 Generated with Claude Code |
# Conflicts: # packages/omamobile-device-panther/version
|
Thank you, Alejandro. Both points are in: the package is at 0.1.17, and the plan commit now travels with the files, so the README row and the comment cite gates that are on main. I ran the package test again on your head merged with today's main and it passes, and the published kernel's board file still has only the fuel gauge on that bus, so this changes nothing on a phone until #259's node arrives. I'm merging this as 0.1.17. It goes out with tomorrow morning's development publish, and then I'll take linux-omarchy-mobile#259. One small thing for #788's rebase, nothing to do here: |
derekross#827 took 0.1.17 first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Pixel 7's charger policy, split out of #788 as you asked there: the two modprobe files the Pixel 7 has charged with since 2026-11-01, the Pixel 7 Pro's. On today's kernels they change nothing, since panther has no
pmic@66node and nothing of the MAX77759 but the gauge binds. They have to be in a published package before linux-omarchy-mobile#259: with that node and withoutdefault_ilim_ua, the upstream driver turns charging off at probe.What it adds (device-panther 0.1.17, on top of 0.1.15; #577 takes 0.1.16):
vendor/modprobe.d/omamobile-charger.conf:options max77759_charger default_ilim_ua=500000 temp_guard=1: a 500 mA input limit without a Type-C source, and stock's temperature bands from the gauge;softdep max77759_charger pre: max17042_battery, so the guard's first reading succeeds.vendor/modprobe.d/omamobile-max77759.conf:tcpci_maxim, which would take the USB-C port we use for SSH, and the GPIO and NVMEM cells blacklisted. The charger itself isn't, so omamobile-device-panther: off-mode charging instead of starting the phone on its cable #788's off-mode charging hasmax77759-charger/onlineto watch.installstages both. The test checks both options together, the gauge first, the three blacklisted modules and the charger not blacklisted. It usesgrep -cvx … >/dev/nullwhere omamobile-device-panther: off-mode charging instead of starting the phone on its cable #788 had thegrep -qvxpipe thattests/grep-q-pipescaught.On the phone: these are the same two files the Pixel 7 has run since BATTERY-PLAN D1 (2026-11-01), on test kernels with linux-omarchy-mobile#259's node: the charger loaded at boot with
default_ilim_ua=500000,tcpci_maximand the GPIO and NVMEM cells stayed out, and the battery reached 100 %. #788's smoke report was taken with them. BATTERY-PLAN (panther): the charger, gates B3 to D1 and their results, moved here from #788, records them: the plan and the results of B3.1-B3.3, B3g and D1 from 2026-11-01, which until now were only in my tree. Its status line says this package ships the files from 0.1.17.Checks:
packages/omamobile-device-panther/test/all,tests/grep-q-pipesandtools/pr-checkpass.🤖 Generated with Claude Code