Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions device/husky/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,16 @@ Sources:
- `P/`: postmarketOS pmaports `device/testing` (2026-10-21).
- `G/`: Google's GPL kernel for this phone, `android-gs-shusky-6.1-android16` ([source.android.com: Build Pixel kernels](https://source.android.com/docs/setup/build/building-pixel-kernels)).

## 2026-11-13: display, GPU and CPU DVFS on merged `omamobile`

[Kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160) (merged 2026-11-10) and [#157](https://github.com/derekross/linux-omarchy-mobile/pull/157) with [#158](https://github.com/derekross/linux-omarchy-mobile/pull/158) (merged 2026-11-13) booted from `omamobile` itself, at `82f31d3a7` (#158's last commit), on Brett's phone (Samsung UFS 3.1): `7.3.0-rc6-omamobile-push1-g82f31d3a7a35`, the repository's husky config, the pinned clang (`clang-r596125`), `modules-push`, slot B flashed with `bin/omamobile flash`. The initramfs was the one from the 2026-11-01 test set, unchanged (husky packs no modules into it), and `omamobile-device-husky` was 0.1.8, so the kernel was the only change on this boot. Before the flash, slot B's retry count read 2 after one boot, and entering fastboot with `reboot-to bootloader` didn't change it [V].

- **CPU DVFS** [V]: cpufreq-dt with schedutil on three policies: CPUs 0-3 up to 1704 MHz, 4-7 up to 1945 MHz and 8 up to 2294 MHz, the battery current limiter's caps, with boost off (the turbo levels unused). The energy model has its three perf domains (`cpu0`, `cpu4`, `cpu8`) and logs no `EM: invalid perf. state`.
- **Thermal** [V]: big 49, mid 50, little 49 and gpu 50 °C at 52 s, idle.
- **GPU** [V]: panthor renders the session; its devfreq idles at 150 MHz.
- **Display** [V]: gs-decon with the HK3 on DSIM0, `card2-DSI-1` connected at 1344x2992. The HK3's one refused brightness write before `allow_tx` (`sending dcs data 51 02 bc failed: -1`) is still there, as on the test trees. 120 Hz was measured on the test tree with the same code (`husky-test-20261109-t1`, [kernel #160](https://github.com/derekross/linux-omarchy-mobile/pull/160#issuecomment-6748459836)), not again here.
- **The rest of the boot** [V]: the S2MPG14 RTC registers as `rtc0` ([kernel #243](https://github.com/derekross/linux-omarchy-mobile/pull/243)) and `/sys/power/mem_sleep` reads `[s2idle] deep` ([kernel #244](https://github.com/derekross/linux-omarchy-mobile/pull/244)). `tools/phone-smoke` passes every check: Wi-Fi joins (`wlp1s0`, brcmfmac), Bluetooth powers on, the battery charges. The test trees' `No PKTID available` and `exynos-clkout` probe lines are gone ([kernel #235](https://github.com/derekross/linux-omarchy-mobile/pull/235), [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209)). The new error-level lines it lists are the BCM4398's Bluetooth ID lines, brcmfmac's `TxCap blob found, loading` and the HK3 write above.

## 2026-11-09: NFC on the 8 Pro: the pad clock and the controller, two boots on the head of kernel #209

My phone (the Kioxia unit), slot B. Kernel PR [#209](https://github.com/derekross/linux-omarchy-mobile/pull/209) (the `exynos-clkout` match for zuma, plus the `nfc@8` node from #208) was tested at its head, `e9c3fa348` (a8087e225 plus the two optional edits Derek suggested, a DTS comment and a commit message line); the kernel is `7.3.0-rc6-omamobile-push1-ge9c3fa348c8a`, built with my test kernel's config. That head has no HK3 display driver and no PCIe PHY symbol, so these boots had a simple framebuffer, no Wi-Fi and no sound; the phone was driven over USB ssh. Each boot spent one slot B try; the count was refilled to 3 with `fastboot set_active b` before each flash.
Expand Down
Loading