Skip to content

Pixel 8 Pro display: gs-decon, DSIM0 and the HK3 panel at 120 Hz - #160

Merged
derekross merged 10 commits into
derekross:omamobilefrom
greenbrettmichael:omamobile-zuma-husky-display
Nov 10, 2026
Merged

derekross merged 10 commits into
derekross:omamobilefrom
greenbrettmichael:omamobile-zuma-husky-display

Conversation

@greenbrettmichael

@greenbrettmichael greenbrettmichael commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

10 commits on omamobile, rebased after #153 landed. It doesn't depend on #157 or #158.

This gives the Pixel 8 Pro a real display path. gs-decon, the flip-only KMS driver, takes over from simple-framebuffer, and gs-dsim-cmd with a new HK3 panel driver adds 120 Hz, brightness and sleep. It mirrors the Pixel 9a's display work (#88, #89, #90): zuma's DECON and DSIM are the Tensor G4's.

Why zumapro's support carries over: Google's display driver builds zuma with cal_9865 (its Kbuild has CONFIG_SOC_ZUMA → cal_9865), the CAL gs-decon's zumapro data follows. husky's stock DECON0 node has zumapro's main registers (0x19470000), DPP0 read DMA (0x19900000), interrupts (SPI 243, 242, 241) and 14 windows. cal_9865/regs-dsim.h has cal_9845's offsets for every register gs-dsim-cmd uses. DSIM0 is at 0x19440000 on SPI 252.

The commits:

  1. dt-bindings: display: google,gs201-decon: Add the Tensor G3
  2. drm: google: gs-decon: Add the Tensor G3: zumapro's register layout, padded pitch and hardware trigger, with the HK3 panel's modes from Google's panel-gs-hk3.c: 1344x2992 at 60 and 120 Hz, porches 80/24/42 and 12/4/22, 70 x 155 mm.
  3. arm64: dts: exynos: google: zuma: add DECON0 (disabled)
  4. arm64: dts: exynos: google: zuma-husky: enable DECON0: a 64 MiB reusable scanout pool below 4 GiB, in RAM stock leaves free, and the splash as the boot framebuffer.
  5. dt-bindings: display: samsung: google,gs201-dsim: Add the Tensor G3: google,zuma-dsim with the gs201 fallback, as arm64: dts: exynos: google: zumapro-tegu: Enable the display #90 does for zumapro.
  6. arm64: dts: exynos: google: zuma: add DSIM0 (disabled)
  7. drm: google: gs-dsim-cmd: Add the Pixel 8 Pro's link timers
  8. dt-bindings: display: panel: Add Google HK3
  9. drm/panel: Add Google HK3 panel driver
  10. arm64: dts: exynos: google: zuma-husky: put the HK3 on DSIM0

The 120 Hz link timers (7):

  • The 60 Hz pair is the bootloader's: UNDERRUN_CTRL 0x2235, CMD_TE_CTRL1 0x34c53c1e.
  • Google's dsim_calc_underrun() reproduces 0x2235 exactly for 4 lanes at 1368 Mbit/s (word clock 85.5 MHz), DSC 3:1, 1344x2992, 24 bpp and HK3's TE idle of 350 us with a 1 % variance.
  • So the 120 Hz underrun is the same formula's, 0x06a7. The TE protect and timeout fields are halved, as for the other two links, giving 0x1a621e0f.
  • The way the table's other 120 Hz values were derived, the 60 Hz value less the frame time saved at the word clock, agrees: 8757 - 7054.5 = 1702.5, so within one unit.

The HK3 driver (9): command sequences from Google's MIT-licensed panel-gs-hk3.c. Like the TG4C driver, it takes the panel over as the bootloader left it and never resets it or touches its supplies.

  • Sleep and wake: sleep in/out, with Google's display on and off sequences (the AMP type and Vreg changes, using the Vreg of panels from DVT1 on, the retail ones).
  • 60/120 Hz in HS manual mode: the whole of Google's panel feature update for that mode each time. That's fixed TE and early exit at 120 Hz, changeable TE and no early exit at 60 Hz, then the manual frequency, all applied by the frame update command (F7 0F). HBM and IRC stay as the bootloader left them.
  • Brightness: a backlight over Google's normal range, DBV 196-3307 (2-1000 nits), with pixel off at 0 as Google does. A level set while the panel is asleep, or before gs-dsim-cmd allows commands (-EPERM), is kept and sent with the next write. That way systemd-backlight's boot-time restore succeeds, and its unit stays active to save the level at shutdown.

Tested on husky (tags husky-test-20261031-d1, the first 4 commits, and -d2, all 10, each merged with #156 and #158, built and installed with modules-push):

  • gs-decon on its own (d1):
    • stage 0 reads GLOBAL_CON 0x113 (command mode, running), BLD_BG_SIZE/RDMA_IMG_SIZE 0x0bb00540 (1344x2992) and RDMA_BASEADDR 0xfac00000;
    • stage 1 counts frame start and frame done at 60.03 Hz, one for one;
    • stage 2 takes over from simpledrm. On a normal boot it does so at 3.7 s, before SDDM at 4.5 s, and Hyprland starts on gs-decon, rendering with panthor through aquamarine's render-node fallback.
  • The DSIM and the panel (d2):
    • with allow_tx off, gs-dsim-cmd dumps DSIM0 and recognises the timers ("link timers for 60 Hz"), and the HK3 driver binds with its backlight. A brightness write from userspace is refused;
    • with allow_tx on, brightness writes reach the panel: 1600 and then 600 dimmed the screen, and Omarchy's own brightness control works;
    • gs-decon then offers "up to 120 Hz", and Hyprland picks 1344x2992@120 as the preferred mode;
    • DECON0 counts 601 frame starts in 5 s (120 Hz, paced by the panel's TE), with DSIM0 holding 0x6a7/0x1a621e0f;
    • flips are 5.2 ms on average, 10.5 ms worst, with no timeouts, none late, and no DSI or underrun errors;
    • by eye: swipes are smoother, with no glitches, flicker or tint.
  • Reboots, with the omarchy-mobile display start (omamobile-device-husky 0.1.3: the display at 120 Hz, with brightness omarchy-mobile#228, which sets gs_dsim_cmd.allow_tx before gs_decon as the 9a's graphics start does; tag -d3, its files installed under /etc and /usr/local):
    • the start allows DSI commands for google-hk3.20800a before gs_decon loads;
    • the session comes up on gs-decon and switches to 120 Hz;
    • a brightness of 700 set before the reboot comes back.
  • Sleep and wake (tag husky-test-20261101-e1, with gs_decon screen_off=2, which wifi: brcmfmac: confine the Bluejay BCM4389 bring-up #228 now sets): four DPMS off/on cycles with DSI commands allowed. Each time DECON stopped and the panel went to sleep, and DPMS on woke it at 120 Hz. Over the cycles: no flip timeouts, none late, the worst flip at 10.4 ms, and no DSI or panel errors.

tools/kernel-pr-check --build --merge passes: it merges cleanly onto 51fb40d, W=1 builds of the 7 touched C files pass, 8 device trees have no new dtbs_check warnings, and dt_binding_check passes on 10 bindings. checkpatch --strict has one note: the HK3 binding's MAINTAINERS entry arrives with its driver in the next commit.

Not here yet:

  • The copy: aquamarine allocates its swapchain as dumb buffers on gs-decon (DRM Dumb: created a dumb allocator, 3 x XR24), so frames rendered on panthor are copied into them rather than scanned out directly. The DPU's SysMMU would remove that copy.
  • The panel's DT description: its reset line and supplies, once the main PMIC's regulators are described.

🤖 Generated with Claude Code

@derekross

Copy link
Copy Markdown
Owner

Thanks Brett, this is a very complete port, and the 120 Hz numbers hold up: I ran Google's dsim_calc_underrun() with HK3's parameters and get 0x2235 at 60 Hz and 0x6a7 at 120 Hz, as you say. The modes, size and brightness range match Google's HK3 driver too. On the Pixel 7 Pro side, gs-decon compiles to the same instructions, and in gs-dsim-cmd only the probe's table lookup grows; the 7 Pro's timers still match only its own row. What I need before merging:

  1. A rebase onto omamobile: Pixel 8 Pro touchscreen: zuma's clocks, ACPM and HSI0's SPI (stacked on #148) #153 landed under new ids, so GitHub shows a conflict and CI hasn't run. Your commits pick cleanly.
  2. The d1, d2 and d3 tags on your fork, plus uname -r and a tools/phone-smoke report from the d2 or d3 boot.
  3. Have you put the screen to sleep and woken it on this build? The display-off sequence (AMP type change, Vreg 4.5 V, sleep in) isn't in the test list. One off/on cycle with DSI commands allowed, then flip times and any DSI errors, would cover it.

Also, #90 changes the same DSIM compatible to a oneOf for the 9a; whichever lands second should list google,zuma-dsim and google,zumapro-dsim in one enum before the gs201 fallback. Small things: the header's citation path should be kernel/devices/google/shusky/display/panel-gs-hk3.c, and Google's default brightness is 1353 rather than 1600. derekross/omarchy-mobile#228 will merge after this one.

@greenbrettmichael

Copy link
Copy Markdown
Contributor Author

Thanks Derek, and thanks for re-running dsim_calc_underrun().

  1. Rebased onto omamobile and force-pushed. The commits picked cleanly. tools/kernel-pr-check --build --merge passes: 3 C files at W=1, 8 trees with no new dtbs_check warnings, dt_binding_check on 3 bindings. The one note left is the binding's MAINTAINERS entry, which arrives with the driver one commit later.

  2. The tags husky-test-20261031-d1, -d2 and -d3 are on my fork now, plus today's husky-test-20261101-e1: this branch as pushed, merged with Pixel 8 Pro CPU DVFS: zuma's CPU levels from the ECT and CPU thermal zones (stacked on #157) #158 (which carries Pixel 8 Pro GPU: zuma's CMU_G3D, ACPM GPU clock, panthor and a GPU thermal zone #157) and Pixel 8 Pro Wi-Fi: zuma's PCIe and the BCM4398 (stacked on #153, #143, #56) #156. The smoke report from e1 is below.

  3. Sleep and wake: thanks for asking, because it turned up a gap.

    • With gs-decon's default screen_off=0, DPMS off only parks DECON on black frames at 60 Hz. The HK3 stays awake, so the display-off sequence never ran.
    • With screen_off=2, as cheetah and tegu ship it, I ran four off/on cycles on e1 with DSI commands allowed, through Hyprland's DPMS:
      • each time, DECON stopped (frame_start unchanged over 2 s) and panel_asleep went to 1;
      • DPMS on woke the panel back to 120 Hz, at 241-242 frames in 2 s;
      • over the cycles: 374 flips, 0 timeouts, 0 late, latency 4.5 ms on average and 10.4 ms at worst, which is the same worst case as before the cycles;
      • no DSI, panel or underrun errors in the kernel log, only gs-decon's rate lines.

    omamobile-device-husky 0.1.3: the display at 120 Hz, with brightness omarchy-mobile#228 now sets screen_off=2.

  4. Small things: the header cites kernel/devices/google/shusky/display/panel-gs-hk3.c, and the default brightness is 1353, Google's 140 nits.

On #90: agreed. Whichever lands second lists google,zuma-dsim and google,zumapro-dsim in one enum before the gs201 fallback.

tools/phone-smoke on husky-test-20261101-e1

uname -r: 7.3.0-rc6-omamobile-husky-wifi (the test kernels pin the release name; this is build #11 of tag husky-test-20261101-e1).

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-husky-wifi, slot b, up 289s
storage guard (required) ok 62 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 0 error lines in dmesg
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1344x2992
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok SALIXP Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth skip no controller
battery skip no battery power supply
sound cards skip none
sensors skip no sensor proxy
cameras skip no libcamera tools
thermal ok hottest zone 50 °C

The "0 error lines" is only because I cleared the ring buffer with dmesg -C during the screen-off test on this boot. From journalctl -k -b -p err, the boot's error lines, leaving out brcmfmac's, are:

  • panthor: _opp_set_regulators: no regulator (mali) found, expected: ACPM sets the rail;
  • the HK3's one refused brightness write before allow_tx (sending dcs data 51 02 bc failed: -1), whose level is kept and sent again;
  • exynos-clkout: cannot match parent device, from the zuma PMU already on omamobile, and on the d3 boot too;
  • systemd's gpt-auto generator, and "unable to open an initial console".

@greenbrettmichael greenbrettmichael changed the title Pixel 8 Pro display: gs-decon, DSIM0 and the HK3 panel at 120 Hz (stacked on #153) Pixel 8 Pro display: gs-decon, DSIM0 and the HK3 panel at 120 Hz Nov 1, 2026
@derekross

Copy link
Copy Markdown
Owner

Thanks Brett, all four points are in, and the screen-off test is exactly what I was after:

  1. The rebase: clean, CI is green (dtbs_check and dt_binding_check included), and my own gate run agrees. The one checkpatch note is the MAINTAINERS line arriving with the driver one commit later, which is fine.
  2. The tags: fetched. husky-test-20261101-e1 contains this head, and its only change to these files is Pixel 8 Pro Wi-Fi: zuma's PCIe and the BCM4398 (stacked on #153, #143, #56) #156's wider bus ranges, so the e1 smoke report covers this PR.
  3. Sleep and wake: thanks for finding the screen_off=0 gap. Four cycles with the panel really asleep, no DSI errors and the same worst-case flip time is good evidence. It also makes omarchy-mobile#228's screen_off=2 part of the deal, and that PR merges after this one.
  4. The small things: the citation now points at kernel/devices/google/shusky/display/panel-gs-hk3.c, and 1353 is Google's default_brightness (140 nits) in that file.

On the Pixel 7 Pro side, gs-decon.c and gs-dsim-cmd.c are byte-for-byte the files I compared last round, and the base hasn't touched them since, so that comparison still holds.

The merge order: Lef's #163 goes first. This PR merges cleanly on top of it and of #175, so it comes next, without another rebase. #158 then rebases once over both. If #90 lands before this one, the DSIM binding needs the one-enum form we agreed on.

@derekross

Copy link
Copy Markdown
Owner

A correction to the order above: #96 merged first, and it carries the Pixel 9a's DSIM binding (#90's patch), so this now conflicts in google,gs201-dsim.yaml. Please rebase onto omamobile and fold the zuma compatible into that binding's single enum, the form we agreed on. Everything else stands, and I'll merge it as soon as CI is green on the rebase.

@derekross

Copy link
Copy Markdown
Owner

Brett, since my last comment the Pixel 9a's DSIM binding landed, so #160 now conflicts in google,gs201-dsim.yaml. Both compatibles go in one enum under the items: (zuma and zumapro, then google,gs201-dsim), and the merged description wants rewrapping. After that the plan is unchanged: #160, then #158 rebased over it.

The Tensor G3 (zuma) DECON0 is the Tensor G4's: Google's display driver
builds zuma with the same CAL (cal_9865), and the Pixel 8 Pro's stock
DECON0 node has zumapro's main registers (0x19470000), DPP0 read DMA
(0x19900000), interrupts (SPI 243, 242, 241) and fourteen windows. Add
its compatible.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
The Tensor G3 (zuma) DECON0 and DPP0 are the Tensor G4's: Google's
display driver builds zuma with cal_9865, the CAL the zumapro support
follows, and the Pixel 8 Pro's stock DECON0 sits at the same addresses
with the same interrupts and fourteen windows. Match google,zuma-decon
with zumapro's register layout, padded pitch and hardware trigger, and
the Pixel 8 Pro's HK3 panel modes: 1344x2992 at 60 and 120 Hz, with the
porches of Google's panel-gs-hk3.c and its 70 x 155 mm size.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Describe zuma's DECON0 with its DPP0 read DMA window and its frame start,
frame done and extra interrupts, from the Pixel 8 Pro's stock node, as
zumapro.dtsi does. It is disabled: a board enables it with its scanout
pool and boot framebuffer.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Turn on DECON0 on the Pixel 8 Pro with a 64 MiB reusable scanout pool
below 4 GiB, for DPP0's 32-bit DMA, in RAM that stock leaves free, and
the bootloader's splash as its boot framebuffer. DPP0 already scans the
splash out by its physical address (RDMA_BASEADDR_P0 reads 0xfac00000).
There is no DSIM on its output port yet, so gs-decon stays at the
bootloader's 60 Hz.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
The Tensor G3 (zuma) DSIM0 has gs201's register layout for the command
path: Google's cal_9865/regs-dsim.h, which its display driver builds for
zuma, has cal_9845's offsets for every register gs-dsim-cmd uses, and on
the Pixel 8 Pro they hold the bootloader's command-mode setup (version
0x02090100). Add google,zuma-dsim next to google,zumapro-dsim, with
google,gs201-dsim as the fallback of both.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Describe zuma's DSIM0 with its link and D-PHY windows and its interrupt
(SPI 252), from the Pixel 8 Pro's stock node, as Google's zuma tree has
them. It is disabled: a board enables it with its panel.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Add the command-mode timers for the Pixel 8 Pro's HK3 link, so gs-decon
can switch it between 60 and 120 Hz. The 60 Hz pair is the bootloader's
(UNDERRUN_CTRL 0x2235, CMD_TE_CTRL1 0x34c53c1e). At 120 Hz the TE
protect and timeout fields are halved, as for the other two links, and
the underrun is Google's dsim_calc_underrun() for 4 lanes at 1368
Mbit/s, DSC 3:1, 1344x2992 and HK3's TE idle of 350 us with a 1 %
variance: the same formula gives the bootloader's 60 Hz value exactly.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
The HK3 is the Google Pixel 8 Pro's 1344x2992 command-mode AMOLED panel:
DSC 1.2 with two 672x187 slices at 8 bits per pixel over four DSI lanes,
a TE line, and 60 or 120 Hz, as in Google's panel-gs-hk3.c. Its supplies
and reset line are described as on the TG4C, though the driver takes the
panel over as the bootloader left it.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Add a driver for the Google Pixel 8 Pro's HK3 command-mode AMOLED panel,
with command sequences from Google's MIT-licensed panel-gs-hk3.c.

Like the TG4C driver, it takes the panel over as the bootloader left it:
out of sleep, with the display on, at 60 Hz. It never resets the panel
or touches its supplies. It:

- puts the panel to sleep and wakes it, with Google's display on and
  off sequences around display on/off (the AMP type and Vreg changes,
  with the Vreg of panels from DVT1 on, the retail ones);
- switches it between 60 and 120 Hz in high-speed (HS) manual mode,
  sending the whole of Google's panel feature update for that mode
  each time: fixed TE and early exit at 120 Hz, changeable TE and no
  early exit at 60 Hz, then the manual frequency, applied together by
  the frame update command. The HBM and IRC settings stay as the
  bootloader left them;
- exposes its brightness as a backlight over Google's normal range,
  DBV 196-3307 (2-1000 nits), using pixel off at 0 as Google does. A
  level set while the panel is asleep, or before gs-dsim-cmd allows
  commands (allow_tx), is kept and sent with the next write, so a
  boot-time restore of the saved level does not fail.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
Enable DSIM0 with the Pixel 8 Pro's HK3 panel and connect it to DECON0's
output port, so gs-decon switches the link and the panel between 60 and
120 Hz and the panel driver handles brightness and sleep. The panel is
described without its reset line and supplies: the driver takes it over
as the bootloader left it, and the main PMIC's regulators are not
described yet.

Assisted-by: LLM
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
@greenbrettmichael
greenbrettmichael force-pushed the omamobile-zuma-husky-display branch from 9e2071b to d5c35c5 Compare November 9, 2026 18:13
@greenbrettmichael

Copy link
Copy Markdown
Contributor Author

Thanks Derek, and sorry for the wait. Rebased onto today's omamobile (1a882ca) and force-pushed (d5c35c5fa).

The other eight commits picked up unchanged (git range-diff shows them as identical).

tools/kernel-pr-check --build --merge passes: it merges cleanly onto 1a882ca, checkpatch --strict has no errors (the one warning is still the HK3 binding's MAINTAINERS line, which arrives with the driver one commit later), W=1 builds of the 3 touched C files pass, 10 device trees build and pass dtbs_check with no new warnings, and dt_binding_check passes on 3 bindings.

I haven't booted this exact head. Apart from the binding, the only change is the merge with the Wi-Fi nodes, and e1 already ran that combination.

For the order: #158 (rebased today as well) conflicts with this one only in zuma.dtsi, where both add nodes at the same place: DSIM0 and DECON0 here, CMU_G3D and the GPU there. Kept in address order, it's a two-sided keep. I'll rebase #158 once this lands.

@greenbrettmichael

Copy link
Copy Markdown
Contributor Author

A boot of the exact heads now, as promised: omamobile (1a882ca) with #160 (d5c35c5fa) and then #158 (e00ab31e1) merged. The one zuma.dtsi conflict between them is resolved by keeping both sides in address order. Test tag: husky-test-20261109-t1.

  • Build: the pinned clang 22.0.2 (clang-r596125, tools/fetch-toolchain), main's tooling, the modules installed with modules-push, and slot B flashed with omamobile flash. The initramfs is the e1 one, unchanged (husky packs no modules into it), so the kernel was the only change on this boot.
  • Device package: omamobile-device-husky 0.1.8 from main. I installed it on e1 first and booted it once there (clean: the rescue stood aside with no hsi2c_11). The point was that its MAX77759 blocklist is in place before this kernel turns the bus on.
  • uname -r: 7.3.0-rc6-omamobile-push1-g54e10dcccd6b

What the two PRs do on this boot:

tools/phone-smoke on husky-test-20261109-t1
Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g54e10dcccd6b, slot b, up 57s
storage guard (required) ok 62 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 97G free
kernel health (required) ok no oops or BUG; 0 WARN, 46 error lines in dmesg (34 known, 12 new)
new dmesg errors not ok N N: brcmf_msgbuf_rxbuf_data_post: No PKTID available !! x2; Bluetooth: N: BCM: '…' x2; exynos-clkout exynos-clkout: probe with driver exynos-clkout failed with error N x1
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card2-DSI-1 connected, 1344x2992
GPU ok render node on panthor
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked true)
touch ok SALIXP Touchscreen
buttons ok gpio-keys
Wi-Fi ok wlp1s0 on brcmfmac, link up
Bluetooth ok hci0, powered true
battery ok 20% Charging, 22 °C
sound cards skip none
sensors skip no sensor proxy
cameras skip no libcamera tools
thermal ok hottest zone 49 °C

The "new" dmesg lines, none from these PRs:

@derekross

Copy link
Copy Markdown
Owner

Thank you, Brett, and welcome back. Everything from my 11-01 comments is in: the DSIM binding has
the single enum with google,gs201-dsim as the fallback, and the rest of the series is
unchanged apart from the Wi-Fi context in zuma-husky.dts. I fetched husky-test-20261109-t1:
it's exactly this head merged with #158, with the zuma.dtsi conflict kept in address order, so
your boot covers what will land. The DPMS cycle with the panel really asleep is the result I was
after.

I checked the Pixel 7 Pro side again on today's base: its device tree is byte-identical, gs-decon
compiles to the same instructions, and in gs-dsim-cmd only the probe's rate lookup grows, with
none of the 8 Pro's values matching the 7 Pro's. The merge also passes my gate, and the device
trees validate with no new messages.

The one hiccup isn't yours: GitHub's run for your 18:13Z push failed before it started any job
("workflow file issue"), the same for #158, while #157's identical commits ran fine. I'll re-run
it and merge this as soon as it's green. Then #158 needs its one rebase over this; keeping both
sides in zuma.dtsi as in t1 is right (the rebased tree should come out as t1's,
a0d5f81ee17d). Thanks for the patient work on this one.

@derekross
derekross merged commit 3b13c2d into derekross:omamobile Nov 10, 2026
1 check passed
@derekross

Copy link
Copy Markdown
Owner

Merged, thank you, Brett. CI's second run passed on this head (the first one never started a job, which was GitHub's side). For #158: please rebase it over this, and take the Pixel 8a point from my comment there in the same push.

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