Repository navigation
device-raven: load the charger at boot, with its temperature guard - #112
Conversation
Raven's MAX77759 charger ran on the bootloader's settings: a wall charger charged, but at a 4.35 V float voltage (stock 4.45 V, so the battery stopped short of full), a 1.93 A fast charge (above stock's table at 10-20 degC) and with no temperature guard. With raven's battery node (derekross/linux-omarchy-mobile#112), the charger now loads at boot with cheetah's options: default_ilim_ua=500000 keeps charging on without a Type-C driver, and temp_guard applies stock's temperature bands, stopping charging when the gauge has no reading or the battery is out of range. The gauge loads first. The Type-C driver and the PMIC's GPIO stay blacklisted. omamobile-charge-guard is cheetah's status tool; the sysfs names are the same on raven. USB-PLAN section 4 has the read-only register dump and the four gated steps: the stock limits applied, a wall charger still at 1.2-1.4 A into the battery (the chip keeps choosing its own input), the guard stopping charging within one 30 s check without a reading, and the charger loading at boot. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks, this is a model bring-up: a read-only register dump first, each step with its stop and rollback, and the "no reading means no charging" case actually tested. The modprobe options and softdep are cheetah's, line for line, and I'll merge this right after the battery node (kernel #112) and set the version then (device-raven 0.1.26 unless something lands first). C5 can follow in the plan when you've had a full charge. As on the kernel PRs, a |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Smoke report from the build that runs this: derekross/linux-omarchy-mobile#112 (comment). C5 (full charge to 100 %) passed; added to USB-PLAN in this branch. |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for the C5 result and the note on raven's own stock tables in USB-PLAN; a full charge to 100 % closes the plan nicely. Main's checks pass on this head, and device-raven's tests pass merged with the USB-route and haptics PRs. I'll merge this right after the battery node (kernel #112), as |
#112 was squash-merged as "device-raven 0.1.26", but its branch kept the version file at 0.1.25, so main still built 0.1.25 with the charger change in it. A publish would replace the earlier 0.1.25 with different contents under the same version, and phones that already have 0.1.25 wouldn't upgrade to get the charger. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The matrix after the merges since #118, with each cell going by the merged notes: - Pixel 7 (panther): the board file (derekross/linux-omarchy-mobile#108) and the FT3658 touch driver (derekross/linux-omarchy-mobile#109) have merged into the published kernel, so Boot, Storage, Buttons and USB net say "in the published kernel" instead of "in review". Touch stays "no": the driver and the touch rails are published, but the board file has no touch node, and panther's notes end at boot 8 with the controller not answering. BRINGUP-M1's status and NOTES' header say the same. - Pixel 6 Pro (raven), Charging: no -> works. device-raven 0.1.26 (#112, #126) loads the MAX77759 charger at boot with its temperature guard; USB-PLAN section 4 records C0-C5 passed on 2026-10-28, a full charge to 100 % included. The battery node is derekross/linux-omarchy-mobile#112; the runs were on an unpublished integration kernel, and the cell says so. - raven, Torch: still works; the LED's node is now in the published kernel (derekross/linux-omarchy-mobile#113), tested on omamobile-gs101-torch and not yet run from the published kernel. - Pixel 9a (tegu), Fingerprint: no -> WIP. FINGERPRINT-PLAN records F0 and F2-F6b passed on an unpublished kernel: Trusty's TA runs and the HAL sees the sensor; enrollment waits for the factory calibration (F6c). omamobile-fingerprint 0.1.10 (#101) maps Trusty's stores for it. Left as they were: tegu's Charging (the MAX77779 charger driver, derekross/linux-omarchy-mobile#92, is published, but tegu's notes record no run of it), the gs201 HSI2 pin controller (derekross/linux-omarchy-mobile#123, no cell), felix (#35 is a plan) and cheetah (nothing merged for it). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Raven's charger ran on the bootloader's settings: a wall charger charged, but stopped short of full (4.35 V, where stock goes to 4.45 V), used more current than stock allows when the battery is cool, and nothing watched the battery's temperature.
With raven's battery node (derekross/linux-omarchy-mobile#112), the charger now loads at boot with cheetah's options: charging stays on without a Type-C driver, and the temperature guard follows stock's bands and stops charging without a reading.
omamobile-charge-guardis cheetah's status tool. USB-PLAN section 4 has the register dump and the four gated steps on the phone, including a wall charger still charging at 1.2–1.4 A and the guard stopping charging when the gauge's reading went away. Version bump left to you.🤖 Generated with Claude Code