Skip to content

omamobile-device-tegu 0.2.3: NFC at boot, and the 9a's own setup-system - #235

Merged
derekross merged 3 commits into
derekross:mainfrom
W4HO-ham:device-tegu-nfc-setup
Nov 1, 2026
Merged

derekross merged 3 commits into
derekross:mainfrom
W4HO-ham:device-tegu-nfc-setup

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

Stacked on #234 (0.2.2) and #230 (0.2.1); the third commit is this one.

NFC at boot. With the NFC clock pad in clk-exynos-clkout (linux-omarchy-mobile#104's rework, coming there next) and #105's node naming clocks = <&pmu_system_controller 0>, omamobile-tegu-graphics-start loads nxp_nci_i2c as its last hang-safe step and waits for nfc0. The step only runs for a node that names its clock. A bring-up DTB without one leaves NFC to its own scripts, so the palmtop's daily integration boot is unaffected. The guard file's comment says so, and the test covers all three cases: with the clock, a failed load, and without the clock.

omamobile-setup-system for the 9a. This is the 7 Pro's script with the 9a's list. It enables omamobile-sensor-proxy and omamobile-nfc-open. It leaves out the fingerprint service (its first start writes secure storage), speaker protection (the 7 Pro's CS35L41s), and the GNSS socket, because a session starts the modem, whose link still hangs the SoC after some minutes. omamobile-firstboot runs it at install, as on the 7 Pro.

Tested on the palmtop today, kernel 7.3.0-rc6-omamobile-push1-gb45a0d400e49 (#96 + the clkout rework + #105's two DT commits), with this package installed and omamobile-setup-system run once. At boot, with nothing by hand:

  • omamobile-tegu-graphics: "up: GPU, display, haptics, torch, NFC".
  • pmu-clkout0 enabled with consumer 1-0008.
  • nfc0 with all six protocols.
  • neard and omamobile-nfc-open active, and nfc0 already in polling mode.
  • 0 nxp-nci I2C errors.

test/all and tools/pr-check pass.

… 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.
With the kernel branch tegu-dt-aoc the device tree enables Trusty, the GSA and the AoC, so the AoC start gets its wants link and answers to omamobile-aoc.service, which the sensor proxy and the fingerprint service name. Trusty and the TAS2572 amplifier driver are blacklisted too, and the amplifiers load once the AoC is online.
With the NFC clock pad in clk-exynos-clkout and the node in the device tree, the graphics start loads nxp_nci_i2c as its last hang-safe step and waits for nfc0. A 9a omamobile-setup-system, as the 7 Pro's, enables the sensor proxy and the NFC link opener; not fingerprint, speaker protection or GNSS yet.
@derekross
derekross merged commit 38f0789 into derekross:main Nov 1, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thanks! I merged the stack through this PR as one squash ("omamobile-device-tegu 0.2.3: the charge limit on the kernel's charger, the AoC and NFC at boot, and the 9a's own setup-system"), which closes #230 and #234 too. Gating the NFC step on a node that names its clock is a nice way to leave the daily integration boot alone, and the existing sleep hook already stops polling before s2idle.

From the #230 review, one thing worth a README sentence later: the battery's change events come from a 30 s poll on a freezable workqueue, so while the phone is asleep nothing runs the charge-limit script, and a phone asleep on the charger below the limit will charge past it until it wakes. The threshold version didn't have that gap; a sleep hook that sets inhibit-charge when the level is already at the limit would close it.

The AoC step (#234) is what I hoped: hang-safe, a condition on the AoC node, the omamobile-aoc.service alias so the sensor proxy orders after it, and speaker protection staying off on the 9a through its own condition.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants