diff --git a/device/panther/DISPLAY-PLAN.md b/device/panther/DISPLAY-PLAN.md new file mode 100644 index 000000000..0ad6792ca --- /dev/null +++ b/device/panther/DISPLAY-PLAN.md @@ -0,0 +1,200 @@ + +# Pixel 7 (panther) display: DCS brightness, then flip-only KMS + +Status (2026-11-01): G1, D1 and D2 passed (kernel: [linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177), in review): the panel driver takes the panel over, and brightness and display off/on work over DCS, including from the shell's slider. device-panther 0.1.4 ships `allow_tx=1` (installed; its first boot is still to come). Next: D3 (flip-only KMS). + +Today the Pixel 7 shows the bootloader's framebuffer through simplefb and +simpledrm: no brightness control, no screen off, no vsync. The Pixel 7 Pro +solved the same with three drivers on top of the pipeline ABL leaves +running (device/cheetah/DISPLAY-PLAN.md): + +- **`gs-dsim-cmd`**: a MIPI DSI host on DSIM0 that sends DCS packets through + the DSIM FIFOs, interleaved with frames. It sends only with `allow_tx=1`. +- **A panel driver** that takes the running panel over and sends nothing + until the brightness or the power state changes. +- **`gs-decon`**: flip-only KMS that keeps ABL's DECON, DSIM and DSC + configuration, flips DPP0 between buffers, reports frame starts as + vblanks, and replaces simpledrm. + +This plan brings them to panther, one change per boot. The display path +and DSIM are the same as the Pixel 7 Pro's. The panel is different, and +so is the size. + +[V] is verified on this phone or in the source; [I] is inferred. + +Every gate keeps the last good image set and its modules for its Rollback: +the previous kernel's images are kept beside the new build, and its +modules stay on the phone until `linux-modules-cleanup` moves them. + +## What is known + +| Fact | Evidence | +| --- | --- | +| ABL leaves DECON0 → DSIM0 → panel running in command mode, with DPP0 scanning 0xfac00000 | BRINGUP-M1.md, first light [V] | +| The panel is the Samsung S6E3FC3 "P10": compatible `samsung,s6e3fc3-p10` under DSIM0's `panel@0`, and stock's command line names `sdc-s6e3fc3-p10` | stock live DT and `/proc/cmdline` [V] | +| Reset on gpa7-1, as on the Pixel 7 Pro; supplies vci (S2MPG12 LDO27M) and vddi (S2MPG13 BUCKA), as in Google's `gs201-panther-display.dtsi`; TE on DSIM0's `te-gpio` | stock live DT [V] | +| 1080x2400, 66x146 mm, 60 and 90 Hz (plus a 30 Hz AOD mode); DSC with two 540x48 slices, 8 bpc, 8 bpp; four lanes, non-continuous clock | Google's GPL `panel-samsung-s6e3fc3-p10.c` (`kernel/google-modules/display/samsung`, branch `android-gs-pantah-6.1-android16`) [V] | +| Brightness is DCS 0x51 with an 11-bit value MSB first: 4-2047 normal, 2048-4095 HBM, default 1023 | the same driver and its common `exynos_panel_set_brightness()` [V] | +| Cold init: sleep out (120 ms), TE on, column and page address, then level-2 registers (TE width, FQ CON, V-total, source, LTPS, EM off), 60 Hz (0x60 0x00), TE2, DSC on with the vendor PPS, MIC off (0xc2 0x14), DSC decoder on (0x9d 0x01), WRCTRLD 0x20, display on | `s6e3fc3_p10_enable()` and `s6e3fc3_p10_init_cmds` [V] | +| `gs-dsim-cmd` works with any panel; it switches the refresh rate only on a link it has timers for, so on panther it stays at 60 Hz | `drivers/gpu/drm/google/gs-dsim-cmd.c` (`gs_dsim_rates[]`) [V] | +| `gs-decon` on gs201 offers only the Pixel 7 Pro's 1440x3120 modes, and refuses to run when ABL's size differs | `gs-decon.c` (`gs201_decon_data`, the size check at probe) [V] | +| The DSI command path, the panel driver and `gs-decon` are modules autoloaded from the DT; `allow_tx` and `screen_off` are set by the Pixel 7 Pro's device package | `kernel/configs/omamobile.config`, `omamobile-device-cheetah` `modprobe.d/omamobile-display.conf` [V] | + +## The changes ([linux-omarchy-mobile#177](https://github.com/derekross/linux-omarchy-mobile/pull/177)) + +1. `dt-bindings: display: panel: add Samsung S6E3FC3 P10`. +2. `drm/panel: add Samsung S6E3FC3 command-mode panel`. It follows the + Pixel 7 Pro's S6E3HC4 driver: + - **Takeover.** At probe, if reset reads released, the driver holds the + supplies and leaves the line alone. + - **Brightness.** A backlight device over DCS 0x51, 4-2047. + - **Blanking.** It turns the display off with the panel out of sleep. + - **Cold path for KMS.** Prepare runs the reset and Google's init at + 60 Hz, enable sends display on, disable display off, and unprepare + sleep in and reset. + - **Left out:** local HBM (it needs panel reads), AOD and the panel + revision reads. Only EVT1 and later panels are covered. +3. `arm64: dts: ... gs201-panther: add the DSI command path to the panel`. + It enables `cmu_disp`, `cmu_dpu` and `dsi0` with the panel node. DECON0 + stays disabled. + +`CONFIG_DRM_PANEL_SAMSUNG_S6E3FC3=m` goes into `kernel/configs/omamobile.config`. + +Later, for D3: `gs-decon` picks its mode table by the size ABL left (adding +the S6E3FC3's 1080x2400 timings), panther's DT gets DECON0 with a +`display_pool`, and device-panther gets the `modprobe.d` options. + +## Gates + +### G1. The new `omamobile` base alone (low risk) + +`omamobile` moved from b0d62d9e7 to caf5f8a2b. It brought #166 and #167, +which are already in kernel F, and also gs201's ACPM TMU, thermal zones, +CPU DVFS and cooling. Kernel G1 is the same feature set as F on that base: +#133, #171 and #170 merged. It changes nothing in the display path. Flash +it through fastboot (slot B is at 1 retry). + +**Pass:** +- Touch, GPU, haptics, battery and the USB rescue are as on F. +- The thermal zones read sensible temperatures. +- cpufreq lists its policies, with no ACPM errors. + +**Stop if:** the phone resets, ACPM errors, or thermal throttling at idle. +**Rollback:** fastboot (Power + Volume Down), then flash kernel F's image +set, whose modules are still on the phone. + +### D1. DSI command path, read-only (low risk) + +Kernel G2 = G1 + the display branch. Modules first, then a push. + +**Pass:** +- `gs_dsim_cmd` and `panel_samsung_s6e3fc3` bind, and the panel logs + "taken over from the bootloader". +- `/sys/class/backlight/*` exists. +- **The screen keeps showing the desktop**: nothing is sent, because + `allow_tx` is 0. +- simplefb and simpledrm stay in charge. +- No DSIM errors in `dmesg`, and everything else is as on G1. + +**Stop if:** the screen blanks or freezes. **Rollback:** fastboot, then +flash G1's image set (its modules stay on the phone); USB and SSH don't +depend on the screen. + +### D2. DCS brightness (low-medium risk; the screen changes) + +On the running G2: `echo 1 > /sys/module/gs_dsim_cmd/parameters/allow_tx`. +Then: +1. Write the brightness at 1023 (the default), then 400, 2047 and 4. +2. Blank the backlight (`bl_power` 4), then unblank it (0). + +Announce each step before running it. + +**Pass:** the screen dims and brightens at each step, turns off when +blanked and comes back when unblanked, with the picture intact, and there +are no DSIM timeouts. + +**Stop if:** the picture breaks or stays dark after unblank. **Rollback:** +`allow_tx=0` stops further packets; a reboot restores ABL's state. + +On a pass, device-panther ships `options gs_dsim_cmd allow_tx=1`, and the +shell's brightness slider drives the backlight. + +### D3. Flip-only KMS (medium-high risk; staged) + +`gs-decon` with the S6E3FC3 modes at 60 Hz, in three stages: +- **Stage 0:** log DECON and DPP0, read-only. +- **Stage 1:** count frame starts. The measured rate should be about 60 Hz. +- **Stage 2:** take the screen over from simpledrm, then test DPMS off/on + and the panel sleep (`screen_off=2`). + +Each stage is its own boot or module reload. The plan gets its own +runbook before D3 starts, with a Rollback for each stage: D2's image set +by fastboot, and `gs_decon` blacklisted so that simpledrm keeps the +screen. + +### D4. 90 Hz (medium risk) + +DSIM timers for panther's link in `gs_dsim_rates[]`, and the panel's +0x60 0x08. Written after D3. + +## Results + +### 2026-11-01: G1 + +Kernel `7.3.0-rc6-omamobile-push1-g53710bb094e3` (`omamobile` caf5f8a2b with +#133, #171 and #170), flashed after its modules: + +- **Thermal:** `gs101-acpm-tmu` registered 6 thermal zones (big, mid, + little, GPU, ISP, TPU). They read 44-52 °C just after boot and 49-50 °C + 20 s later. Every cooling device was at state 0. +- **cpufreq:** three policies (0, 4, 6) on `schedutil`, at 300-1803, + 400-1999 and 500-2252 MHz. +- **Unchanged from F:** ACPM 14 of 15 channels, touch, GPU, haptics, the + battery and the USB rescue. +- **New warning:** `cpu cpuN: EM: invalid perf. state: -22` on the three + clusters, from the new CPU DVFS. It is still there on D1. +- **The gauge reloaded its model** at this boot (`battery model loaded`), + so it had been in POR: this was the first boot after a stop in fastboot, + and pushed reboots haven't done that. + +The phone was then put in fastboot before D1's modules were on it, so G1 +was flashed again and booted the same way. + +### 2026-11-01: D1 + +Kernel `7.3.0-rc6-omamobile-push1-g54fb87ae5295` (G1 plus the display +branch), pushed after its modules: + +- `gs_dsim_cmd` and `panel_samsung_s6e3fc3` bound. The panel logged + "taken over from the bootloader", attached with 4 lanes and mode flags + 0x400 (non-continuous clock), and its supplies are dummies. +- `/sys/class/backlight/1c2c0000.dsi.0`: 1023 of 2047, `bl_power` 0, + `allow_tx` N. simpledrm kept the screen (`card0`), and **the screen looked + the same**. +- **ABL's DSIM:** VERSION 0x02060000, DPHY_STATUS 0x10f, CLK_CTRL + 0x06131f04, CONFIG 0x04887cff, CMD_TE_CTRL1 0x2a82306d, UNDERRUN_CTRL + 0x1cf8. The underrun isn't in `gs_dsim_rates[]`, so the driver logs "no + rate switching" and stays at 60 Hz. +- No DSIM errors. Everything from G1 still works. + +### 2026-11-01: D2 + +On the running D1 kernel, with `allow_tx` set to 1: + +| Step | Seen on the phone | +| --- | --- | +| brightness 1023 | a little brighter than ABL left it | +| 400 | darker | +| 2047 | clearly brighter | +| 4 | very dark, still visible | +| `bl_power` 4 | display off | +| brightness 1023, then `bl_power` 0 | back on, picture intact, touch working | + +Each write returned 0, and `actual_brightness` followed. There were no DSIM +timeouts or errors in `dmesg`. **The shell's brightness slider then +drove the panel** through the backlight device. + +device-panther 0.1.4 was then installed on the running D1 kernel (no +reboot): `modprobe -c` lists `options gs_dsim_cmd allow_tx=1` from +`/usr/lib/modprobe.d/omamobile-display.conf`. Whether `allow_tx` reads Y +by itself is checked at the next boot. diff --git a/docs/DEVICES.md b/docs/DEVICES.md index 1f729c793..c1fafe565 100644 --- a/docs/DEVICES.md +++ b/docs/DEVICES.md @@ -27,7 +27,7 @@ The status of each device, as verified on real hardware. Rows in the matrix have | Pixel 4 XL ([notes](../device/coral/NOTES.md)) | coral | SM8150 (Snapdragon 855) | WIP (direct ABL v2 boot on the test handset's slot A; slot-B install and §3.1 entry pending; [notes](../device/coral/BRINGUP-M1.md)) | testing (read-only `blockdev` guard + RAM `overlayfs`) | testing (1440x3040@60Hz S6E3HC2 DSC 1.1 KMS, DPMS, brightness) | testing (Adreno 640 / FD640 Mesa Freedreno, Hyprland) | testing (FTS SPI multitouch + read-only flash guard) | testing (power via `qcom-pon` + volume via `gpio-keys`) | testing (CDC ECM + ACM + SSH; stays up with host USB switched off) | testing (`WCN3990` `ath10k_snoc` + `rmtfs -r`, WPA2/DHCP/HTTPS; radio sessions ran before the modem baseline) | WIP (`WCN3990` `hci_qca` `hci0` up + BLE scan; audio/pairing open) | WIP (PM8150B ADC `VBAT_SNS` voltage + FG temp; aftermarket pack on test unit: no reply from `1-0036`) | testing (PM8150B SMB5 charger with `4.20 V` / `500 mA` kernel clamp) | testing (`CS40L25A` I2C click waveform) | testing (PM8150L flash LEDs + quick-settings tile) | no | - | testing (QDSP6 + dual `CS35L36` amps capped at `-26 dB` + `IA8508` SPI mic DSP) | testing (`SLPI` + `fastrpc` + RAM-backed `hexagonrpcd` + QMI SSC: 7 sensors + Soli radar) | WIP (`MPSS` boots with `rmtfs -r` + patched `tqftpserv`, SIM detected; no IPA/voice yet; radio sessions ran before the modem baseline) | no | testing (`CAMSS` + `IMX363`, `IMX481`, `IMX520`, dual `OV7251` NIR; `libcamera` softISP) | no | - | | Pixel 9a ([notes](../device/tegu/NOTES.md)) | tegu | zumapro (Tensor G4) | works ([#28](https://github.com/derekross/omarchy-mobile/issues/28): native boot from slot B, the Arch root on `userdata`, `omamobile-device-tegu`; slot B was marked successful by hand on 2026-10-28 with the `devinfo` write approved on 2026-10-22, now on hold ([#125](https://github.com/derekross/omarchy-mobile/pull/125)), and the package does not mark it; unpublished kernel: the SoC and board device tree is [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (UFS behind the read-only guard; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (120 Hz through gs-decon; the panel driver [kernel #89](https://github.com/derekross/linux-omarchy-mobile/pull/89), 120 Hz [kernel #88](https://github.com/derekross/linux-omarchy-mobile/pull/88), merged, the display DT [kernel #90](https://github.com/derekross/linux-omarchy-mobile/pull/90) in review; brightness and the panel's sleep are not claimed until they have a dated record; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Panthor, the desktop renders, runtime suspend when idle; this boot runs at a fixed 160 MHz, so frequency scaling and the GPU thermal zone count as in review, [kernel #85](https://github.com/derekross/linux-omarchy-mobile/pull/85) in review, [kernel #87](https://github.com/derekross/linux-omarchy-mobile/pull/87) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (Synaptics S3908 over SPI, [kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81), merged; survives sleep, [kernel #82](https://github.com/derekross/linux-omarchy-mobile/pull/82), merged; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (gpio-keys: power and volume; the power key wakes from sleep; unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CDC NCM and SSH; reconnects after a replug, `omamobile-tegu-usb-rescue` ([the replug record](../device/tegu/NOTES.md#2026-10-28-what-the-device-tables-claims-rest-on)); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (BCM4383 on PCIe through brcmfmac, WPA2 with iwd, kept loaded across sleep by the package's sleep hook; started by hand, not by the package; [kernel #56](https://github.com/derekross/linux-omarchy-mobile/pull/56) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (hci_uart on the bootloader's address, BlueZ, A2DP; [kernel #94](https://github.com/derekross/linux-omarchy-mobile/pull/94); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (MAX77779 gauge with temperature, current and time estimates through UPower; [kernel #66](https://github.com/derekross/linux-omarchy-mobile/pull/66); unpublished kernel; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (the chip charges on its own; the charger driver with its charge limit and inhibit is loaded by hand, [kernel #92](https://github.com/derekross/linux-omarchy-mobile/pull/92); [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (CS40L26A through feedbackd, with brownout prevention, [kernel #95](https://github.com/derekross/linux-omarchy-mobile/pull/95); its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | works (LM3644, 25 steps to 75 mA, quick-settings tile; its DT [kernel #96](https://github.com/derekross/linux-omarchy-mobile/pull/96) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (a position fix on 2026-10-30 and Omarchy's Location switch serving it on 2026-10-31, started by hand: 46 of 52 GGA sentences fixed, 9-13 satellites, first fix about 80 s after a client connects; needs [kernel #150](https://github.com/derekross/linux-omarchy-mobile/pull/150) and [#114](https://github.com/derekross/omarchy-mobile/pull/114), and a session lasts as long as the modem's PCIe link, one to five minutes, which is the open item; [plan](../device/tegu/MODEM-PLAN.md), record with [#202](https://github.com/derekross/omarchy-mobile/pull/202)) | testing (audio and sensor DSP through the GSA and Trusty, 93 services; the package ships its start disabled until a kernel enables the nodes, so it is started by hand; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (speakers at a -10 dB ceiling, microphone, through the AoC card and PipeWire; by hand, as the AoC; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (accelerometer, light, proximity through the AoC; by hand, as the AoC; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (ONLINE with IPC on an unpublished kernel, no SIM yet; [plan](../device/tegu/MODEM-PLAN.md)) | testing (NXP ST54L through nxp-nci: polls and read a payment card on 2026-10-29 with [kernel #131](https://github.com/derekross/linux-omarchy-mobile/pull/131), merged ([kernel #100](https://github.com/derekross/linux-omarchy-mobile/pull/100) closed into it), [kernel #104](https://github.com/derekross/linux-omarchy-mobile/pull/104) in review; started by hand; polling stops before sleep; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (three cameras stream through libcamera; by hand; [kernel #63](https://github.com/derekross/linux-omarchy-mobile/pull/63) in review, [kernel #103](https://github.com/derekross/linux-omarchy-mobile/pull/103) in review; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | WIP (s2idle when asked for, or through the shell's auto-sleep with the `omamobile-sleep` toggle on, which ships off; the power key or the RTC wakes it, but three test sleeps have not woken, so sleep tests stay attended ([plan](../device/tegu/SLEEP-PLAN.md) S1); the drain is about 300 mA asleep, the same as awake with the screen off, because nothing below the CPUs sleeps yet; [record](../device/tegu/NOTES.md#2026-10-29-the-device-package-boot-and-what-this-row-rests-on)) | testing (enrolls, matches, refuses other fingers and unlocks the lock screen through Trusty and `omamobile-fingerprint`, 2026-10-29; the service ships disabled; [kernel #126](https://github.com/derekross/linux-omarchy-mobile/pull/126), merged; [plan](../device/tegu/FINGERPRINT-PLAN.md)) | | Pixel 8 Pro ([notes](../device/husky/NOTES.md)) | husky | zuma (Tensor G3) | WIP ([#1](https://github.com/derekross/omarchy-mobile/issues/1): slot B, not marked successful; Omarchy's image from the signed repository boots to the lock screen; the zuma device tree is merged ([kernel #13](https://github.com/derekross/linux-omarchy-mobile/pull/13), [#53](https://github.com/derekross/linux-omarchy-mobile/pull/53))) | testing (UFS at HS-G4 behind the read-only guard; Arch on `userdata`; [UFS-PLAN](../device/husky/UFS-PLAN.md)) | WIP (simple-framebuffer: console and Omarchy's lock screen) | no | testing (ST FTM5 over SPI, merged, [kernel #153](https://github.com/derekross/linux-omarchy-mobile/pull/153); [NOTES](../device/husky/NOTES.md)) | testing (power and volume through `gpio-keys`, merged, [kernel #148](https://github.com/derekross/linux-omarchy-mobile/pull/148); [NOTES](../device/husky/NOTES.md)) | testing (USB and SSH) | testing (BCM4398 on a test kernel, [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156); firmware from the owner's image, [#214](https://github.com/derekross/omarchy-mobile/pull/214); [NOTES](../device/husky/NOTES.md)) | no | testing (gauge with Google's ATL model through a bring-up overlay, temperature, MFD, on a test kernel, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163); [notes](../device/husky/BATTERY-NOTES.md)) | testing (the charger driver by hand under a dead-man tool, slow on plain 5 V, on a test kernel, [kernel #163](https://github.com/derekross/linux-omarchy-mobile/pull/163); [notes](../device/husky/BATTERY-NOTES.md)) | no | no | no | no | no | no | no | no | no | no | no | -| Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland lock screen) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | no | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; in review, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | no | no | no | no | no | no | no | no | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | no | +| Pixel 7 ([notes](../device/panther/NOTES.md)) | panther | gs201 (Tensor G2) | WIP (slot B, not marked successful; Arch and Hyprland boot; [BRINGUP-M1](../device/panther/BRINGUP-M1.md); board file merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (UFS behind the read-only guard; Arch on `userdata`; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | WIP (simple-framebuffer: console and the Hyprland desktop; brightness and display off/on over DCS through the S6E3FC3 panel driver and device-panther 0.1.4, in review, [kernel #177](https://github.com/derekross/linux-omarchy-mobile/pull/177); [DISPLAY-PLAN](../device/panther/DISPLAY-PLAN.md)) | testing (Panthor on the Mali-G710; Hyprland renders on it; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the always-on rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | WIP (FocalTech FT3658: touches drive Hyprland and unlock the PIN screen on a test kernel; the driver, [kernel #109](https://github.com/derekross/linux-omarchy-mobile/pull/109), and the touch node, [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), are merged; stock's interrupt pull-up and CS delay, [kernel #166](https://github.com/derekross/linux-omarchy-mobile/pull/166), the driver's review fixes, [kernel #133](https://github.com/derekross/linux-omarchy-mobile/pull/133), and the kernel option with the touch notes, [#149](https://github.com/derekross/omarchy-mobile/pull/149), are merged) | testing (gpio-keys: power, volume; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108)) | testing (USB and SSH; merged, [kernel #108](https://github.com/derekross/linux-omarchy-mobile/pull/108); a replug comes back through `omamobile-usb-rescue` in device-panther 0.1.3, on the MAX77759's I2C bus, merged, [kernel #167](https://github.com/derekross/linux-omarchy-mobile/pull/167); [notes](../device/panther/NOTES.md#2026-10-29-usb-comes-back-after-a-replug-u1)) | no | no | WIP (MAX77759 fuel gauge with stock's battery model on a test kernel: percentage, capacity and temperature in upower and the bar; in review, [kernel #171](https://github.com/derekross/linux-omarchy-mobile/pull/171) and the driver fix [#170](https://github.com/derekross/linux-omarchy-mobile/pull/170); [BATTERY-PLAN](../device/panther/BATTERY-PLAN.md)) | no | testing (CS40L26 with the phone's own firmware, `tools/extract-vendor-firmware -d panther`; merged through [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134), with the feedbackd rule in device-panther 0.1.1, [#145](https://github.com/derekross/omarchy-mobile/pull/145); [notes](../device/panther/NOTES.md#2026-10-28-the-gpu-and-the-haptics-power-off-and-usb-after-a-replug)) | no | no | no | no | no | no | no | no | no (s2idle by default since [kernel #134](https://github.com/derekross/linux-omarchy-mobile/pull/134) and device-panther 0.1.1; not run yet) | no | | OnePlus 13 ([notes](../device/dodge/NOTES.md)) | dodge | sm8750 (Snapdragon 8 Elite) | testing (kernel in the contributor's fork, [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [BRINGUP](../device/dodge/BRINGUP-M1.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (msm/dpu; warm-boot drop fixed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (Adreno 830 / gpu2; Vulkan untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing ([notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (CDC NCM + SSH; gadget stuck after replug until reboot; kernel in the contributor's fork, [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (WCN7860 / ath12k; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (pairing; A2DP untested; kernel in the contributor's fork, [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (gauge; charging path not claimed; kernel in the contributor's fork, [kernel #115](https://github.com/derekross/linux-omarchy-mobile/pull/115) closed; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | no | no | - | testing (speakers, earpiece, mics; headset plug untested; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (accel, prox, compass; autorotate; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | testing (LTE data; calls/SMS untested; opt-in flag; [modem](../device/dodge/modem/README.md), [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | no | WIP (s2idle not default; [notes](../device/dodge/NOTES.md#2026-10-28-matrix-evidence)) | no | | *Template* | *codename* | *SoC* | | | | | | | | | | | | | | | | | | | | | | | diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 4bf051aef..241e98f11 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -157,6 +157,10 @@ CONFIG_SND_SOC_TAS2781_I2C=m # (modprobe.d/omamobile-display.conf) since gate D2 passed. CONFIG_DRM_GS_DSIM_CMD=m CONFIG_DRM_PANEL_SAMSUNG_S6E3HC4=m +# The Pixel 7's panel (S6E3FC3 P10), for brightness and display on/off +# (device/panther/DISPLAY-PLAN.md). A module, autoloaded from the DT; it +# binds only to its compatible. +CONFIG_DRM_PANEL_SAMSUNG_S6E3FC3=m # Flip-only KMS on the bootloader's DECON0, 60 and 120 Hz (DISPLAY-PLAN.md, # D5d/D6). Autoloaded from the DT (decon0 enabled); it replaces simpledrm once # gs-dsim-cmd, the panel and clk_acpm have probed. diff --git a/packages/omamobile-device-panther/PKGBUILD b/packages/omamobile-device-panther/PKGBUILD index fee65edf4..ed30bf0c6 100644 --- a/packages/omamobile-device-panther/PKGBUILD +++ b/packages/omamobile-device-panther/PKGBUILD @@ -3,7 +3,7 @@ pkgname=omamobile-device-panther pkgver=$(cat "${startdir:-.}/version") pkgrel=1 -pkgdesc="Omarchy Mobile support for the Google Pixel 7 (panther): storage guard, USB networking, GPU, haptics, suspend-to-idle and USB after a replug" +pkgdesc="Omarchy Mobile support for the Google Pixel 7 (panther): storage guard, USB networking, GPU, haptics, suspend-to-idle, USB after a replug and display brightness" arch=(aarch64) url="https://github.com/derekross/omarchy-mobile" license=(MIT) diff --git a/packages/omamobile-device-panther/README.md b/packages/omamobile-device-panther/README.md index 197fb6135..e375aeaa0 100644 --- a/packages/omamobile-device-panther/README.md +++ b/packages/omamobile-device-panther/README.md @@ -10,6 +10,7 @@ Omarchy Mobile's first userspace package for the Google Pixel 7 (codename panthe | `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover | | `bin/omamobile-usb-rescue`, `vendor/systemd/system/omamobile-usb-rescue.service` | `/usr/bin`, `/usr/lib/systemd/system` (enabled for `multi-user.target`) | Brings USB back after a replug: the MAX77759 opens its USB2 data switch on unplug, and with no Type-C driver nothing closes it. While VBUS is valid, puts the switch back to 0x09 on the chip's I2C bus (USI13, which the board file enables). Reads two registers and writes that one; stands aside once a Type-C driver owns the chip. Same script and unit as the Pixel 7 Pro; needs `i2c-tools` | | `vendor/systemd/logind.conf.d/10-omamobile-power-key.conf` | `/usr/lib/systemd/logind.conf.d` | A short power press does not power the phone off. Same drop-in as the Pixel 7 Pro. The long press stays the PMIC reset | +| `vendor/modprobe.d/omamobile-display.conf` | `/usr/lib/modprobe.d` | Lets `gs_dsim_cmd` send DCS packets to the panel (`allow_tx=1`), so the panel driver can set the brightness and turn the display off and on. The driver ships with sending off; brightness passed DISPLAY-PLAN gate D2 on the Pixel 7 | | `vendor/systemd/sleep.conf.d/10-omamobile.conf` | `/usr/lib/systemd/sleep.conf.d` | Suspend means suspend-to-idle: the kernel offers `deep`, but Linux has no gs201 sleep sequence, and the phone doesn't wake from it. No hibernation. Same drop-in as the Pixel 7 Pro | | `vendor/NetworkManager/conf.d/10-omamobile-usb.conf` | `/usr/lib/NetworkManager/conf.d` | Keeps NetworkManager off that link | | `etc/omamobile-mirrorlist` | `/etc/pacman.d/omamobile-mirrorlist` | Where pacman finds the `[omamobile]` repository. Same file as the Pixel 7 Pro package | diff --git a/packages/omamobile-device-panther/install b/packages/omamobile-device-panther/install index 20b76a6e5..e8b009dc2 100755 --- a/packages/omamobile-device-panther/install +++ b/packages/omamobile-device-panther/install @@ -26,6 +26,8 @@ install -Dm644 vendor/systemd/logind.conf.d/10-omamobile-power-key.conf \ "$destination/usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf" install -Dm644 vendor/systemd/sleep.conf.d/10-omamobile.conf \ "$destination/usr/lib/systemd/sleep.conf.d/10-omamobile.conf" +install -Dm644 vendor/modprobe.d/omamobile-display.conf \ + "$destination/usr/lib/modprobe.d/omamobile-display.conf" install -Dm644 vendor/NetworkManager/conf.d/10-omamobile-usb.conf \ "$destination/usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf" install -Dm644 device.conf \ diff --git a/packages/omamobile-device-panther/test/all b/packages/omamobile-device-panther/test/all index 184403aa7..1fa49ecbc 100755 --- a/packages/omamobile-device-panther/test/all +++ b/packages/omamobile-device-panther/test/all @@ -76,6 +76,7 @@ for f in usr/bin/reboot-to \ usr/lib/systemd/network/20-usb-gadget.network \ usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf \ usr/lib/systemd/sleep.conf.d/10-omamobile.conf \ + usr/lib/modprobe.d/omamobile-display.conf \ usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf \ usr/share/omamobile/device.conf \ usr/share/omamobile/device-panther/version \ @@ -105,6 +106,8 @@ grep -q '^HandlePowerKeyLongPress=ignore$' "$power" \ || fail "the long press stays the PMIC reset" grep -q '^MemorySleepMode=s2idle$' "$tmp/root/usr/lib/systemd/sleep.conf.d/10-omamobile.conf" \ || fail "suspend must be s2idle: gs201 never wakes from deep" +grep -qx 'options gs_dsim_cmd allow_tx=1' "$tmp/root/usr/lib/modprobe.d/omamobile-display.conf" \ + || fail "the DSI command host may send to the panel (brightness)" [[ -x $tmp/root/usr/bin/omamobile-usb-rescue ]] || fail "omamobile-usb-rescue is executable" [[ $(readlink "$tmp/root/usr/lib/systemd/system/multi-user.target.wants/omamobile-usb-rescue.service") == ../omamobile-usb-rescue.service ]] \ || fail "omamobile-usb-rescue starts at boot" diff --git a/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf new file mode 100644 index 000000000..0fbfc998d --- /dev/null +++ b/packages/omamobile-device-panther/vendor/modprobe.d/omamobile-display.conf @@ -0,0 +1,5 @@ +# SPDX-License-Identifier: MIT +# The DSI command host may send to the panel: brightness over DCS 0x51 and +# display off/on. Off by default in the driver; proven on the Pixel 7 in +# device/panther/DISPLAY-PLAN.md gate D2. +options gs_dsim_cmd allow_tx=1 diff --git a/packages/omamobile-device-panther/version b/packages/omamobile-device-panther/version index b1e80bb24..845639eef 100644 --- a/packages/omamobile-device-panther/version +++ b/packages/omamobile-device-panther/version @@ -1 +1 @@ -0.1.3 +0.1.4