Repository navigation
Conversation
|
Thank you, Alejandro. This is a careful node: it's the Pixel 7 Pro's Two things decide when it can go in, and both are on the omarchy-mobile side:
One small suggestion while you wait: |
…its charger Describe the MAX77759's PMIC at 0x66 on USI13, as on the Pixel 7 Pro: its interrupt on gpa9-4, low, with a pull-up, as in the Pixel 7's live device tree, its GPIO cell, and the battery as its monitored-battery, so that the charger cell can bind. Give the battery the charger limits: 4.45 V, the top of stock's float voltage tiers, and 0.3 C, the lowest charge current stock allows from 10 to 46 degC at any tier (1283100 uA of 4277 mAh), rounded down to the charger step 0x13, 1266720 uA. The Type-C port controller stays undescribed. The charger driver keeps charging off at probe unless it is given a default input limit, which the device package sets. Note the PCA9468 direct charger at 0x57 on this bus in the comment, as stock's charging tree has it. Tested on a Pixel 7 since 2026-11-01, with the device package's default_ilim_ua=500000 and temp_guard=1: the charger probed at mode 5 with a 4450 mV float voltage, 1266720 uA fast charge and a 500 mA input limit, went from constant current into constant voltage and reached 100 %. The guard applied stock's band at room temperature, stopped charging while the gauge gave no reading and resumed after it. Assisted-by: LLM Signed-off-by: Alejandro Garcia <skipper.pelygro@gmail.com>
edb90ff to
eb0f5e0
Compare
|
Thank you. You're right about the current: it's now The device package's two files are now omarchy-mobile#827, split out of #788, so this waits for that one to be published. 🤖 Generated with Claude Code |
|
Thank you, Alejandro. The current is now the step itself, and the message says where the number comes from. I ran our gate again on today's So this is ready on its own side. I'll merge it once #827 has its version and is in a published device-panther, so no Pixel 7 meets this node without the charger's options. |
The MAX77759's PMIC on the Pixel 7, so that its charger binds, as on the Pixel 7 Pro. Today panther describes only the fuel gauge on that bus, so charging stays as ABL left it: a 4.35 V float voltage, which stops at about 92 %. There is also no
max77759-chargersupply, which omarchy-mobile#788's off-mode charging needs to power off once the cable is out.The change, in
gs201-panther.dtsonly:pmic@66with its interrupt on gpa9-4 (low, pulled up, as in the Pixel 7's live device tree), its GPIO cell, and the battery as itsmonitored-battery.google,chg-cv-limits4.2/4.3/4.45 V);The device package goes first. Without a Type-C source, the upstream driver turns charging off at probe unless it gets
default_ilim_ua. omarchy-mobile#827 ships the Pixel 7 Pro's two files for that:options max77759_charger default_ilim_ua=500000 temp_guard=1, after the gauge;tcpci_maxim,gpio_max77759andnvmem_max77759.Without this node those files change nothing. This should merge after omarchy-mobile#827 is published.
Tested on a Pixel 7 from slot B. Every test kernel since 2026-11-01 has carried this node, and the phone has charged with it every day since. The steps, from
device/panther/BATTERY-PLAN.mdin omarchy-mobile#827:1-0066was unbound, and the charger read as ABL left it.tcpci_maximand the GPIO and NVMEM cells stayed out, and the battery reached 100 %.The commit in my test kernels was the same, except for a change to the file's header comment, which I left out here so it doesn't conflict with #181.
Checks:
tools/kernel-pr-check --build OUT --merge origin/omamobilepasses:omamobile317d87d;dtbs_check, no new warnings.🤖 Generated with Claude Code