Skip to content

omamobile-device-cheetah 0.1.47: load nvmem_max77759 for the reboot reason - #534

Merged
derekross merged 1 commit into
mainfrom
device-cheetah-reboot-reason
Nov 9, 2026
Merged

derekross merged 1 commit into
mainfrom
device-cheetah-reboot-reason

Conversation

@derekross

Copy link
Copy Markdown
Owner

The package half of linux-omarchy-mobile#176 (merged today): stop blacklisting nvmem_max77759, the provider of the MAX77759's reboot-reason cell, so nvmem-reboot-mode can bind and reboot-to bootloader reaches fastboot without the buttons. Tested on the 7 Pro on 2026-11-08 with the module loaded by hand (details in the commit and on #176). tcpci_maxim and gpio_max77759 stay blacklisted. Package test: 9 ok.

Merge after the desktop's cheetah boot files are restaged (L-427): device-cheetah changes are skipped by the nightly until then, same as #371. Version 0.1.47 sits above #371's planned 0.1.46 and the four open 0.1.45 claims.

🤖 Generated with Claude Code

…eason

linux-omarchy-mobile#176 describes the MAX77759's reboot-reason cell and
an nvmem-reboot-mode node on it, so `reboot-to bootloader` writes
0x800000fc (RSBM valid, bootloader) where Google's driver does and ABL
stops in fastboot. The cell's provider is nvmem_max77759, which this
package has blacklisted since the MAX77759 bring-up, so the reboot-mode
driver waited for its supplier and the reason was never written.

Tested on the maintainer's Pixel 7 Pro on 2026-11-08, on #176's kernel
(7.3.0-rc6-omamobile-push1-g8de6aedc7373) with nvmem_max77759 loaded by
hand: reboot-mode bound, the cell read 00 00 00 80, `reboot-to
bootloader` reached fastboot about 4 s later with no buttons (the same
command without the module did not that morning), `fastboot reboot`
returned to slot B with the cell back at 00 00 00 80, and a plain
`systemctl reboot` booted normally. The module autoloads by its
platform:max77759-nvmem alias once the blacklist is gone. On a kernel
without #176's cells it provides nothing anyone uses.

tcpci_maxim and gpio_max77759 stay blacklisted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross
derekross merged commit 38e3bb0 into main Nov 9, 2026
2 checks passed
@derekross
derekross deleted the device-cheetah-reboot-reason branch November 9, 2026 00:28
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…eason (derekross#534)

linux-omarchy-mobile#176 describes the MAX77759's reboot-reason cell and
an nvmem-reboot-mode node on it, so `reboot-to bootloader` writes
0x800000fc (RSBM valid, bootloader) where Google's driver does and ABL
stops in fastboot. The cell's provider is nvmem_max77759, which this
package has blacklisted since the MAX77759 bring-up, so the reboot-mode
driver waited for its supplier and the reason was never written.

Tested on the maintainer's Pixel 7 Pro on 2026-11-08, on derekross#176's kernel
(7.3.0-rc6-omamobile-push1-g8de6aedc7373) with nvmem_max77759 loaded by
hand: reboot-mode bound, the cell read 00 00 00 80, `reboot-to
bootloader` reached fastboot about 4 s later with no buttons (the same
command without the module did not that morning), `fastboot reboot`
returned to slot B with the cell back at 00 00 00 80, and a plain
`systemctl reboot` booted normally. The module autoloads by its
platform:max77759-nvmem alias once the blacklist is gone. On a kernel
without derekross#176's cells it provides nothing anyone uses.

tcpci_maxim and gpio_max77759 stay blacklisted.

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.

1 participant