Repository navigation
Conversation
… charger driver The merged max77779-charger driver has charge inhibit and no end threshold, so the charge limit wrote nothing. The script now switches charge_behaviour between inhibit-charge and auto by the battery's capacity, from the limit to 5 below, and udev runs it on every battery change.
This was referenced Oct 31, 2026
Owner
This was referenced Nov 9, 2026
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…, the AoC and NFC at boot, and the 9a's own setup-system (derekross#235) Merges the stack derekross#230, derekross#234 and derekross#235: - 0.2.1 (derekross#230): the charge limit works with the published max77779 charger driver, which offers inhibit rather than an end threshold; the script handles both and always falls back to auto on a missing or bad file. While the phone sleeps nothing runs the script (the battery's change events come from a freezable 30 s poll), so a phone asleep on the charger below the limit charges past it until it wakes. - 0.2.2 (derekross#234): the AoC starts at boot from the device tree, hang-safe, gated on the AoC node, under the omamobile-aoc.service alias so the sensor proxy orders after it; the amplifiers load after the AoC is online. Speaker protection stays cheetah-only. - 0.2.3 (derekross#235): NFC at boot, gated on a node that names its clock; the existing sleep hook stops polling before s2idle. The 9a gets its own omamobile-setup-system. Closes derekross#230, closes derekross#234.
derekross
pushed a commit
that referenced
this pull request
Nov 15, 2026
…l, regulator-wlan included (#777) Kernel #230's PCI power-control path needs `regulator-wlan`, which the historical `wifi-controller` overlay doesn't enable. A new `wifi-reviewed-controller` overlay enables the regulator, the PHY and the controller, and leaves the endpoint off. WIFI-PLAN records the 2026-11-13 w0/w1/w2 stages on `7.3.0-rc6-omamobile-bluejay-review-20261111` as overlay combinations. The trials set the same `status` properties directly in the DT, so the overlay file itself hasn't booted. The historical overlay stays for the pinned `c934e316b` path. No descriptor applies these overlays, and their targets exist only in #230's disabled DT. Assisted-by: OpenAI Codex
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
omamobile-tegu-charge-limitwrotecharge_control_end_threshold. That attribute exists only on the bring-up charger module. The mergedmax77779_charger(linux-omarchy-mobile#92) offerscharge_behaviour(auto/inhibit-charge) and no end threshold, so on the published driver the limit did nothing.Now, when there's no threshold, the script holds charging off from the limit (
inhibit-charge) and lets it run again 5 points below (auto), usingmax77779-battery's capacity. A charger with a threshold is still handed the limit directly, as before. With no file or a bad value it ends inauto, so charging is never left inhibited. The udev rule now also runs it on everymax77779-batterychange, which is how it follows the capacity.Tested on the palmtop today on the published charger driver, with the charger node from linux-omarchy-mobile#161 (kernel
7.3.0-rc6-omamobile-push1-g7dbac6f4e65c):/etc/omamobile/charge-limit= 80:charge limit 80 %: inhibit-charge, and the charger and the battery went to Not charging.charge limit 100 %: auto, and Charging came back.I ran the script by hand both times. I didn't verify the udev rule's own run on that boot: udev doesn't log the script's output, so my journal check couldn't show it either way.
test/charge-limitgains thecharge_behaviourcases: at the limit, inside the 5-point band, below it, no file, and a bad file.test/allandtools/pr-checkpass.