Skip to content

device/tegu: SLEEP-PLAN S1 result, the drain is the SoC floor - #166

Closed
W4HO-ham wants to merge 23 commits into
derekross:mainfrom
W4HO-ham:sleep-s1-results
Closed

W4HO-ham wants to merge 23 commits into
derekross:mainfrom
W4HO-ham:sleep-s1-results

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

S1 of the sleep plan (#144) ran tonight on the palmtop. The cable-out baseline is 311 mA awake with the screen off and 302 mA asleep (two 30-minute systemctl suspend rounds through power-ab --suspend systemd, #157): sleep saves nothing over the awake screen-off state. A 60 s test shows the CPUs do sleep (timekeeping suspended for the whole minute, one deep-state entry per CPU), and pulling the radios apart with the cable in and the charger's buck off shows Bluetooth, NFC and Wi-Fi cost nothing measurable. What stays on is MIF, the buses and the always-on rails; our kernel has no system idle state for this SoC. MIF at 421 MHz in sleep (tegu-mif-sleep.ko) saves 60-75 mA by the gauge's coulomb counter, matching the 10-28 figure, and the palmtop loads it at boot from a hand unit until the policy lands properly.

Two corrections: the 2026-10-27 "140 mA asleep" figure doesn't hold up against 10-28 (434-445 mA as-is, cable out) or tonight and is retired; and a direct rtcwake -m freeze failed to wake for the second time in two days while every systemctl suspend cycle has woken, so the plan, the notes and the agent gotchas now say to sleep only through systemd. Next is S2 (the four rails) and a cable-out power-ab run with the module loaded.

Docs only: SLEEP-PLAN, NOTES and AGENTS.md. tools/pr-check passes.

Record the baseline (311 mA awake with the screen off, 302 mA asleep, cable out), the proof that the CPUs sleep, the radio elimination (nothing), the MIF-in-sleep saving (60-75 mA, module loaded at boot by a hand unit) and the coulomb-counter method. Note that a direct rtcwake freeze failed to wake again, so every sleep test goes through systemctl suspend; add that to the agent gotchas. Retire the 2026-10-27 140 mA figure.
@derekross

Copy link
Copy Markdown
Owner

Thanks for this. It's a clear S1, and retiring a figure that didn't hold up is exactly what the notes should do. The 302-against-311 mA result is a useful answer: the floor is below the CPUs, so MIF, SICD and the rails are the right next targets. I checked the systemd count against the 10-27 record, and it matches.

A few things before I merge, all docs:

  1. Some of tonight's measurements used steps that aren't in the runbook: the cable-in method with the charger buck off through CHG_CNFG_00, its dead-man restore, the gauge's QH reads, and the direct freeze. Could you add the exact commands as a short method block in S1 (the write, what the dead-man restores and when, the read-back afterwards, and the gauge read)? S2 will probably reuse them, and then they'll have an Expect, a Stop and a Rollback like the rest. Going forward, please put a step like the charger write into the runbook before it runs.
  2. The NFC gotcha just above your new line still ends "so stop polling by hand first" for a sleep written straight to /sys/power/state, which now reads like permission for the path you're ruling out. Could you point that clause at the new rule?
  3. tools/power-ab defaults to --suspend rtcwake, which is a direct freeze, and a detached cable-out run is the worst place for a hang. Please have the new line say to use power-ab --suspend systemd on the 9a.

Smaller things: "What's measured" and S1's Expect still say about 140 mA. The AGENTS line says two direct freezes out of about six, while the plan's numbers give two of five. And the hand unit that loads tegu-mif-sleep at boot deserves a rollback line and the commit it was built from. One thought on the cause: the systemd path also runs the Wi-Fi sleep hook, so the hang might come from Wi-Fi through the freeze rather than from the entry method. Your rule covers both, so it's the right call meanwhile.

#100 merged today, so this now needs a small hand-merge with main (and later #137) in AGENTS.md and at the top of the tegu NOTES. I can do that at merge time.

# Conflicts:
#	AGENTS.md
#	device/tegu/NOTES.md
… rule points at systemd

S1 gets the buck-off, dead-man, read-back and coulomb-counter steps with Expect, Stop and Rollback; the 140 mA expectation becomes the S1 figure; the hand unit for tegu-mif-sleep names its commit and rollback; the direct-freeze count reads two of five and says the Wi-Fi hook may be the real difference. AGENTS's NFC clause no longer allows a direct write, and power-ab runs with --suspend systemd on the 9a.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

All in at 510a4e6, on top of a merge of main (AGENTS keeps every bullet, main's NFC line first and the new rule after it; NOTES keeps the new S1 entry at the top, then the sections #131, #125 and #100 added). Mergeable again.

  1. S1 has a method block now, "S1 method, cable in": the buck-off write (i2cset -f -y 24 0x69 0xbc 0x00), the dead-man first (--on-active=600 for awake measurements; --on-calendar= for sleeps, since monotonic timers don't run in suspend, plus the script's own EXIT restore), the read-back (0xbc must read 0x05, then the battery's current and status), the gauge read (i2cget -f -y 24 0x36 0x4d w, QH, 2.5 mAh per count, with the 60 s check against current_now), each with Expect, Stop and Rollback, and the direct freeze named as the thing not to do. It also says the charger write ran tonight before it was written down, which is not the order the plan asks for, and that from now on such a step goes into the runbook first.
  2. The NFC gotcha's last clause now says a sleep written to /sys/power/state "is ruled out anyway (the next entry: sleep only through systemctl suspend)", so it no longer reads as permission.
  3. The AGENTS line and S1 both say power-ab runs with --suspend systemd on the 9a, because its default --suspend rtcwake is a direct freeze and a detached cable-out run is the worst place for a hang.
  4. "What's measured" and S1's Expect read about 300 mA, with the 140 mA named as retired. The AGENTS count is two of five, matching the plan. The hand unit for tegu-mif-sleep names the commit it was built from (adbca4c88a21, the one the plan already cites), the rollback (systemctl disable --now tegu-mif-sleep; rmmod tegu_mif_sleep) and that the module needs rebuilding at every kernel push. Your thought about the Wi-Fi hook is in both places: a direct freeze goes down with Wi-Fi loaded and un-prepared, so the hang may come from Wi-Fi through the freeze rather than the entry method, and the rule covers both.

…o the rule is attendance, not the entry path

The 2026-10-30 cable-out run with tegu-mif-sleep loaded never woke from its 30-minute systemctl suspend. Three no-wakes now, on both entry paths, with and without the module: the plan tallies them, the hand unit is disabled, and the agent rule asks for attended sleeps and no boot-time module until the hang is understood.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

A correction at b265200, from this morning: a 30-minute systemctl suspend with tegu-mif-sleep loaded (cable out, power-ab --suspend systemd) never woke either, not from the RTC and not from the power key, so the entry method isn't the cause as the branch said. The plan now tallies the three no-wakes (two direct freezes, one systemd sleep with the module) against the sleeps that woke (35 short and six longer systemd ones, two 10-minute direct ones with the module), says no single factor explains it, disables the boot-time hand unit, and keeps the rule to attended sleeps and --suspend systemd for the hooks. The AGENTS line says the same. The cable-out figure with the module is still missing; the next cheap test is a cable-in 30-minute systemd sleep with the module and a kmsg stream to the laptop.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

One more line at 485be76: the cheap test ran. A cable-in 30-minute systemctl suspend with tegu-mif-sleep loaded, alarm logged as armed, woke on the RTC to the second (IRQ 56, the PMIC). So neither the module nor the 30-minute systemd sleep is enough on its own to reproduce the no-wake; the cable being out is the one difference left to this morning's failed run, and that's the next attended probe.

@W4HO-ham

W4HO-ham commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor Author

The cable-out figure with the module is in at 97858da: the run repeated this afternoon with tegu-mif-sleep loaded woke on its alarm, 273 mA awake with the screen off and 259.7 mA asleep (130.0 mAh of charge_now over 1802 s), about 40 mA under yesterday's 302 mA without the module, in line with the coulomb-counter estimate for a gauge this coarse. It also means none of module, 30-minute systemd sleep or cable-out reproduces the no-wake by itself; sleeps stay attended and the boot unit stays off.

…leep, 260 mA

The repeated cable-out run with tegu-mif-sleep loaded woke on its alarm: 273 mA awake with the screen off, 260 mA asleep, about 40 mA below the previous day's figure without the module. None of the suspected factors reproduces the no-wake alone.
@derekross

Copy link
Copy Markdown
Owner

Thank you, everything from this morning is in, and the method block is exactly what I hoped for: S2 can now reuse it as written. And thanks for the two follow-ups the same day. Retracting "the systemd path always wakes" as soon as it didn't is what keeps these notes trustworthy.

The correction reached SLEEP-PLAN's S1 and AGENTS, but not two older spots, so they now say the opposite: the new NOTES entry still says systemctl suspend "has woken every time" and that the module "is loaded at boot by a hand unit now", and SLEEP-PLAN's status line still says "s2idle works (RTC and power-key wakes)". Could you add a 10-30 bullet to the NOTES entry (the cable-out no-wake with the module, the hand unit disabled, the cable-in run that woke, sleep tests attended) and a word about the three no-wakes in the status line? Two small ones while you're there: the AGENTS count of longer systemd sleeps that woke is seven now with this morning's cable-in run, and the "Next" after the method block and S1's "repeat with tegu-mif-sleep loaded" should say "attended", since that's the configuration that didn't wake.

One question: does your palmtop have the omamobile-sleep toggle on? If so, it sleeps unattended every night, and the new rule should say whether that's fine without the module (so far every sleep without it has woken). Optional: the NFC bullet you edited still says omamobile-tegu-nfc isn't in the repository, and #152 ships it now. I'll merge this before #165 and resolve the NOTES top at merge.

… every spot

The NOTES entry no longer says the systemd path has woken every time or that the module loads at boot; a 2026-10-30 bullet carries the cable-out no-wake, the disabled unit, the cable-in wake and the afternoon's 260 mA. The status line names the three no-wakes and attended sleeps, the S1 repeat and Next say attended, the AGENTS count is seven longer systemd wakes, the nightly auto-sleep without the module is said to be fine, and the NFC hook is in the repository since derekross#152.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

All in at 80e6659, point by point:

  1. NOTES: the 10-29 entry no longer says the systemd path has woken every time or that the module loads at boot. A 2026-10-30 bullet carries the cable-out run with the module that never woke (reset by hand), the hand unit disabled, the cable-in 30-minute systemd sleep with the module that woke on its alarm, and the afternoon's repeat of the cable-out run with the module loaded by hand, which woke and read 273 mA awake with the screen off and 260 mA asleep; sleep tests stay attended.
  2. The status line now says three test sleeps have never woken (two direct freezes, one 30-minute systemd sleep with the module) and that sleep tests are attended.
  3. AGENTS counts seven longer systemd sleeps that woke (two 30-minute and four 240 s on 10-29, the cable-in 30-minute one on 10-30), and names the afternoon's cable-out run as the eighth.
  4. The S1 repeat and the Next both say attended, with the reason: that is the configuration that once didn't wake.
  5. Your toggle question: yes, the palmtop has omamobile-sleep on, so it sleeps unattended every night through the systemd path without the module. Every systemd-path sleep without the module has woken (the 35 short ones on 10-27 and the longer ones above), and the two no-wakes without the module were both direct freezes, so the rule now says nightly auto-sleep without the module goes on as before; the module stays off at boot.
  6. The NFC bullet says omamobile-tegu-nfc ships with omamobile-device-tegu since omamobile-device-tegu 0.2.0: the Pixel 9a's bring-up as a package #152.

Mergeable against main; the NOTES top is yours at merge, as you said.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

A correction to my toggle answer at c8d10bf: checking the palmtop just now, omamobile-sleep is off (omarchy-toggle-enabled returns 1), since this afternoon's shell reinstall shipped it off; so the palmtop isn't sleeping unattended at present, and the plan and the AGENTS line now say that, with the on-period record (systemd-path sleeps without the module all woke) kept and turning it back on left to the owner.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

One more data point at 6a3a489, from the #183 proof run: cable in, tegu-mif-sleep still loaded from the drain run, a forced 10-minute systemd sleep; the owner's power-key press and tap did not wake it, the kernel came up once at about 112 s and went back to s2idle, and only the RTC alarm ended it. The power key woke s2idle on 10-27 without the module, so the next cheap test is a key press during a sleep without the module and then with it. A key wake that doesn't register would look just like an alarm that doesn't, which would tie the module to the three no-wakes after all.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Merged main after #137: its NFC line is taken as merged (my small clause edit on it dropped, the new sleep rule follows it), so this is mergeable again.

…nd the root went read-only

The forced 10-minute sleep on 2026-10-30 woke on its alarm but the UFS link never came back (link startup failed, Host init failed, ufshcd_wl_resume failed), every disk read then failed and ext4 went emergency read-only; a sysrq reset recovered it. A palmtop that seems never to wake may have woken with dead storage, so the plan and the agent rules now say to check dmesg for the UFS failure after every sleep and reset from the kernel if it shows.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The afternoon's second data point turned into the finding of the day, at f3047ae. The forced 10-minute sleep did wake on its RTC alarm, but UFS did not: pstore's console has exynos-ufshc 13200000.ufs: link startup failed 1 and ufshcd_host_reset_and_restore: Host init failed 1 five times, then ufshcd_wl_resume failed: 1, and from the first write after resume I/O error, dev sda with hostbyte 0x07 and ext4 going emergency_ro (spm_lvl 5, rpm_lvl 3). The palmtop kept answering SSH from memory for an hour while nothing on disk could be read: systemctl suspend and reboot did nothing, df and coredumpctl returned EIO, the power key's interrupt count rose but the shell could not light the screen. A sysrq b reset brought it back with a clean ext4 journal recovery; everything written earlier in the day was there.

So a "never wakes, power key dead" palmtop may be awake with dead storage, and the three no-wake records can't tell the two apart (none had a console). It's 1 failure in about 50 systemd-path resumes after kernel #83's 32 of 32. The plan and the AGENTS line now say: after every s2idle check dmesg for the UFS failure first, reset from the kernel if it shows, and keep unattended sleep off. The AGENTS NFC/sleep lines you'll hand-merge got one more bullet from this.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Pushed tonight's cycles onto this branch. Attended 30-second RTC-woken s2idle cycles with the cable in, on the daily boot with the modem never loaded: cycles 1 to 5 all woke with link startup failed, Host init failed, I/O error and ufshcd_err_handler all zero, one suspend entry and exit each, root writable, and the power key and Wi-Fi host-wake disarmed again on resume. /sys/power/suspend_stats read success=5, every failure counter zero.

The sixth cycle of that boot didn't come back, and this time the palmtop left the USB bus entirely, so it isn't the dead-storage shape of the afternoon (which kept answering SSH from memory while nothing on disk could be read). It needs a forced restart before anything can be read; the console should be in pstore afterwards.

Two things that follow. The afternoon failure was also late in a long boot (uptime 10801 s) and tonight's hang came after five sleeps, so the next question is whether the failure follows the count of sleeps in a boot rather than any single sleep. And the three dark no-wakes left no ext4 recovery line in their next boot's journal (checked across 25 boots tonight: no boot recovered a journal), so they weren't dead storage either, which fits a hang like this one.

Also in this push: the open-questions list now names the sixth-sleep question and what to run next, which is the cycles again from a fresh boot with the kmsg stream to the laptop and the sleeps counted.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

A correction to my comment above, from reading the afternoon's own console rather than my memory of it. The failing suspend was the third of that boot (entries at 387.7 s, 4746.9 s and 10798.6 s; the third one's resume failed), not a late one, and the 25 seconds before it hold nothing but PAM and audit lines from an SSH login: no ACPM timeout, no thermal error, no UFS warning. I had tied that failure to ACPM timeouts; those are from a different boot of the same day and the link is withdrawn. So the sleep-count idea doesn't fit either: the afternoon was the third sleep of its boot at about 3 h of uptime, tonight's hang the sixth at about 10 minutes. All that both share is that neither was the first sleep of its boot. The plan now says this.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

One more from reading the running device tree, which matters for S2 now that a GNSS session works: the three GNSS rails and the fingerprint rail are declared with labels and no consumer at all, so nothing names them as a supply and that is exactly why they carry regulator-always-on. Dropping that property therefore doesn't move the cost to whoever uses the rail; it just lets the core's unused-rail cleanup switch all four off about 30 s after late init. Still a valid one-boot measurement and still worth doing, but it can't be the shipped policy: GNSS needs its three for a session and the sensor needs LDO15S for an operation. The policy S2 should lead to is a consumer, each path claiming its rails while in use, which needs a supply property and driver support on both sides. So the order is: measure, then decide whether the number justifies that work. The plan says this now.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Lined the three resumes of that boot up on their suspend entry, and the failure is narrower than "UFS didn't resume".

clean (387.7 s) clean (4746.9 s) failed (10798.6 s)
wl resume begins +0.754 +0.741 +0.717
dme-set attr-id 0x4021 +0.803 +0.800 never
Power mode changed to FAST series_B G_4 L_2 +0.859 +0.866 never
link startup failed 1 - - +1.198, +1.655, +2.143, +2.622, +3.058
reset_and_restore 0 0 1

So it is link startup itself: it never reached the first DME set, each attempt took about 430-490 ms (the UIC timeout) and five in a row used up ufshcd_host_reset_and_restore(). The clean resumes bring the whole link up in 50 to 90 ms. The irq 73 disarm (Wi-Fi host wake) lands either side of the DME set in the clean runs, so its ordering against the UFS resume isn't the difference.

That points the next run at the link-startup path, which at spm_lvl 5 is a full re-init: the PHY power-on and the release of the device reset line that gs101_ufs_suspend() asserts, rather than anything in hibern8. One sample against two clean resumes in that boot and five clean cycles tonight, so I'm treating it as a direction, not a conclusion.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Added one more open question with its answer half-done: the record says we have never read which PMIC event ends an early RTC cycle, and the driver names the register. s5m_check_pending_alarm_interrupt() reads S2MPG14_PMIC_STATUS2 on zumapro (S2MPG12_PMIC_STATUS2 on gs201) and takes the alarm from RTCA0E, bit 2, with RTCA1E as bit 1. So after an early wake that register says whether the alarm fired at all and its other bits name what else the PMIC latched; a single register read through the chip's regmap in debugfs, not a whole dump.

Noticed while reading kernel #149, which fixes the same readback for gs101's S2MPG10. Worth saying for anyone following that PR: zumapro's and gs201's cases are already correct in our tree, so #149 doesn't change what the 9a or the 7 Pro report.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The failing Tests job here is the paused-tick check in test/owl-idle, not anything in this branch: it is false for one second in every ten by construction. #207 fixes it, and this should go green once that is in.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Two things from this morning, pushed.

Ten of ten 30-second RTC-woken cycles on the daily boot woke with the storage counters, the ACPM timeout count and the watchdog count all zero, and suspend_stats reading success=10 fail=0.

More useful than the count: the reason every earlier hang left no kernel evidence is that printk suspends the consoles at the freeze, so nothing reached ramoops past that line. It needs no boot argument, /sys/module/printk/parameters/console_suspend is writable and echo N keeps the console alive through s2idle. The whole run is in a streamed log with all ten entry and exit pairs and the wake-irq disarms. So the next hang should leave its last words, which is what the 10-30 night could not give us.

@derekross

Copy link
Copy Markdown
Owner

Thanks for the steady stream of runs, and especially for reading your own console back and withdrawing the ACPM link, and for the console_suspend find. Before I merge, could you do one consistency pass?

  1. The 10-30 NOTES bullet still says the nightly auto-sleep goes on as before; the toggle is off, and unattended sleep should stay off.
  2. The status line and the AGENTS line should count the sixth-cycle hang and mention the UFS resume failure, rather than "three" and "s2idle works".
  3. Please record what pstore held after that forced restart, and how the 30-second cycles entered sleep (systemctl suspend or rtcwake), since the rule depends on it.
  4. The CLKGATE test needs its commands in the runbook (Expect, Stop, Rollback), not in a runner outside git.
  5. A question on the PMIC STATUS2 read: is that register cleared on read? A userspace read could take the alarm away from the RTC driver.

There's also a doubled "the shell's the shell's" in AGENTS.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Consistency pass done and pushed, on today's main.

  1. The 10-30 NOTES bullet now says the auto-sleep toggle is off since the shell reinstall and that unattended sleep stays off.
  2. The status line counts four sleeps that never woke (two direct freezes, the 30-minute systemd sleep with the module, and the sixth 30-second cycle of 10-30 that left the USB bus) plus the one that woke with UFS dead, and says "usually works" with the ten clean 10-31 cycles behind it. The AGENTS line now names both bad endings, the read-only root and the hang off the bus.
  3. Recorded: after the forced restart /sys/fs/pstore held nothing from the hung boot, and the kept console has that boot's bootloader log and the next boot's with no kernel lines from the hang, because printk had suspended the consoles. Every 30-second cycle, that night and this morning, went rtcwake -m no -s 30 then systemctl suspend, so the sleep hooks ran each time; none was a direct write to /sys/power/state.
  4. The clock-gating test is now an S3 runbook step with Expect, Stop and Rollback, and the console_suspend write as its first line.
  5. STATUS2 is not cleared on read, by the driver's own account: the S2MPG14 regmap marks only INT1 to INT5 precious ("clear on read"), and STATUS2 is listed volatile ("RTC alarm flag") and not precious, so it is a level flag a read does not change, and regmap's debugfs refuses precious registers anyway. The plan says so.

The doubled "the shell's" I could not find after merging main; if it is still there in a line you see, point me at it and I'll fix it.

Ten 30-second s2idle cycles with idle clock gating off all woke with no UFS errors. The run with gating on was also ten of ten, so the hypothesis is neither confirmed nor ruled out yet.
@derekross

Copy link
Copy Markdown
Owner

Thank you, this is a thorough pass, and console_suspend=N is a real find. I'll fix the last bit at merge: the AGENTS sleep line still says "three" and "both direct freezes", from before the sixth-cycle hang. The doubled phrase was "The shell's" with a capital T.

@derekross derekross closed this in 17dc6b9 Oct 31, 2026
@derekross

Copy link
Copy Markdown
Owner

Landed on main authored by you (the PR shows as closed because the commit went in directly).

derekross added a commit that referenced this pull request Nov 1, 2026
…s on the 7 Pro (#254)

Kernel #153 (husky touch), #166 and #133 and omarchy-mobile #149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…oor and sleep tests stay attended (derekross#166)

S1-S3 of the Pixel 9a's sleep plan: the drain is the SoC floor, the sleeps that didn't wake and the UFS resume failure are recorded with what pstore held and how each cycle entered sleep, the CLKGATE test is a runbook step, and sleep tests stay attended. Maintainer edit: the AGENTS sleep line counts four no-wakes, adds the sixth-cycle systemctl suspend hang, and drops the doubled phrase.

Closes derekross#166

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…s on the 7 Pro (derekross#254)

Kernel derekross#153 (husky touch), derekross#166 and derekross#133 and omarchy-mobile derekross#149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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