Repository navigation
Conversation
|
Thank you, the display nodes are compact and they check out against Google's tree. What I checked:
The clock series under this branch has landed on One question before it merges. Google's tegu device tree lists three panels under the connector (TG4A, TG4B and TG4C), and as on the Pixel 7 Pro I'd expect the bootloader to name the fitted one on the kernel command line (
Two smaller notes: gs201 keeps the DECON0 to DSIM0 ports in the SoC dtsi, and zumapro could do the same (optional); and the "created CMA memory pool" line from your 9a's dmesg would be nice to have in the PR. For the omarchy-mobile side, tegu's kernel config will need |
fa04098 to
39d8bb3
Compare
|
Thanks for checking it against Google's tree. The bootloader on my 9a reports I agree on the guard. The tegu device package isn't published yet; when it is, it will set The pool from the 9a's boot log: I'll take the binding wording and moving the DECON0 to DSIM0 ports into the SoC dtsi at the rebase after #80, #81, #85 and #87. |
|
Thank you for the answers and the pool lines.
Your three commits are unchanged from last time. I built every Google board's device tree with this branch: the six existing ones are byte-identical and validate exactly as before. With #89 and #88 merged in as well, the 9a's tree validates with no messages, so CI's one remaining failure ( So the plan stays the same. #89 can merge now, then the board PRs under this one. After that, rebase this branch onto |
39d8bb3 to
de5d1aa
Compare
de5d1aa to
5529571
Compare
|
Thanks for rebasing. With #89 merged, CI passes here and the 9a's device tree validates with no messages. Your three commits are unchanged, so the binding wording ("compatible with the gs201 DSIM for the registers its driver uses") and moving the DECON0-to-DSIM0 ports into the SoC dtsi aren't in yet. Both are optional. You'll be pushing the stack once more anyway for the "Tested on" line (see #80), so that push would be the easiest time to add them. If you'd rather leave them for later, that's fine too. The stack will land through #96, its top, and I'll close this PR as landed there. |
5529571 to
2c8422b
Compare
|
Thanks. All three of your commits are unchanged since my last look (the tree at this commit is the same, With the rebase resolved, the display commits build at each step without warnings, One thing outside this PR. On 10-27 you said the tegu device package would set The display will be covered by the boot of #96's head (the smoke report's display row, 1080x2424 on DSI-1). This lands with #96. |
2c8422b to
c608f4e
Compare
Turn on CMU_G3D and the Mali-G715 for the Pixel 9a, with its core clock on ACPM's paired "gpu" clock (index 17), which sets the shader (G3D) and L2 (G3DL2) domains together, and coregroup and stacks on CMU_G3D's gates. The operating points are the shader rates of the 9a's GPU DVFS table up to 649 MHz. The levels above it, to 940 MHz, wait for a GPU thermal zone, since nothing throttles the GPU yet. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Give the three CPU clusters their ACPM DVFS clocks (cpucl0-2, by the zumapro ACPM clock ids) and operating points for cpufreq-dt, with capacities and power coefficients for the energy model from Google's zumapro-cpu.dtsi, and add the ACPM TMU sensor and the big, mid, little and GPU thermal zones. The CPU levels are the APM firmware's own (its DVFS table, read on the Pixel 9a), up to the 9a's thermal headroom: 1950 MHz little (Google's max-freq for that cluster), 2367 MHz mid and 2687 MHz big. The little cluster's 324 and 610 MHz lie below stock's 820 MHz floor. Each CPU zone throttles its cluster from 80 C, forces the cluster's lowest levels from 95 C and shuts down at 105 C, all below stock's 112 C (CPU) and 115 C (GPU) hot trips. gpu-thermal throttles panthor's devfreq from 85 C. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
… MHz With gpu-thermal throttling the GPU, add the 9a's GPU levels above 649 MHz: 723, 807, 850 and 890 MHz. The table's top, 940 MHz, stays out until it has run on the 9a. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
The Tensor G4 (zumapro) display pipeline has the gs201 DSIM, at the same register layout and with the same three register windows. Add google,zumapro-dsim with google,gs201-dsim as its fallback. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Add DSIM0, the DSI master between DECON0 and the panel: its link and D-PHY register windows and its interrupt (GIC SPI 252), as in Google's GPL zumapro device tree, disabled until a board names its panel. Link: https://android.googlesource.com/kernel/devices/google/zumapro/+/8831630eee2ad095b85ed452944e6353940966a5/dts/zumapro.dtsi Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Turn on the Pixel 9a's display pipeline: DECON0 with a 64 MiB reusable scanout pool below 4 GiB and the bootloader's splash as its boot framebuffer, scanning out to DSIM0, and the TG4C panel on DSIM0's virtual channel 0. With DECON's output on DSIM0, gs-decon switches the link and the panel between 60 and 120 Hz. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
c608f4e to
33c1855
Compare
|
Rebased onto today's omamobile. The Tensor G4 SoC, the Pixel 9a board and its touchscreen are in omamobile now, so those commits dropped out; six remain (GPU, CPU DVFS and thermal zones, the GPU's levels, the DSIM binding, DSIM0, the display). zumapro-tegu.dts compiles with dtc; checkpatch --strict clean on each commit. |
|
Thanks for the rebase. Same patches and trees as before, and the gate passes on today's |
|
Its patches landed unchanged through #96, so I'm closing this one. Thanks! |
Stacked on #87, #85, #81 and #80. It uses #89's
google,tg4cbinding, and at run time #88 and #89. Only the last three commits are new.google,gs201-dsim: addgoogle,zumapro-dsim, withgoogle,gs201-dsimas the fallback. The Tensor G4 has the same DSIM and register layout, and the 9a has run gs-dsim-cmd on the gs201 compatible all along.zumapro.dtsi: DSIM0, with its link and D-PHY windows and GIC SPI 252 as in Google's zumapro tree. It's disabled.zumapro-tegu.dts:With DECON's output on DSIM0, gs-decon switches between 60 and 120 Hz.
Against the palmtop: the DSIM0, panel, DECON port and pool nodes match the DTB it boots now (round pn1, the panel as
google,tg4cdriven by #89's driver), apart from DSIM0's new compatible. That boot runs the desktop at 120 Hz with DPMS sleep and wake.CHECK_DTBS=y W=1forzumapro-tegu.dtbis clean,dt_binding_checkpasses for the DSIM schema, and checkpatch --strict is clean on all three commits.