Repository navigation
Conversation
Enable the Mali-G710 that gs201.dtsi describes, as the Pixel 7 Pro does.
Its clock is the ACPM GPU clock, which this board already gets through
acpm_ipc, and as on the Pixel 7 Pro there is no mali-supply: the G3D rails
follow the PMU power domain and ACPM, and the bootloader leaves the GPU
powered.
Tested on a Pixel 7 from slot B (7.3.0-rc6), with the device package's
rule that keeps the GPU powered: panthor probes the Mali-G710 (id 0xa862,
shader_present 0x1110055), boots the CSF firmware (interface v1.5.0) and
registers renderD128, and Hyprland renders on it through Mesa's panfrost
("Mali-G710 MC7 (Panfrost)") with no MMU faults or GPU resets. As on the
Pixel 7 Pro, probe prints "no regulator (mali)" from the OPP core.
Assisted-by: Claude Opus 5.5
Signed-off-by: Alejandro Garcia <skipper.pelygro@gmail.com>
|
Thank you, @nesmeck. This is the cleanest kind of GPU enable: one Here's what I checked:
One ordering point, no change needed from you: the Pixel 7 Pro keeps the GPU powered through the always-on udev rule, because powering G3D back up needs a secure call our kernel doesn't make yet. You tested with the same rule installed, and it ships in derekross/omarchy-mobile#145. So I'll merge that first (or at the same time), so no panther build ever has the GPU without the rule. Since #130 and #134 carry this commit, I plan to land all three through #134 with "Rebase and merge", which keeps each commit as you wrote it, and then close this one as merged through #134. If you'd rather I merge them one by one, say so; the PRs above it would then need a rebase after each merge. |
The Pixel 7 gets three files from the Pixel 7 Pro's package, byte-identical and compared by the package test when cheetah's package is beside it: - sleep.conf.d/10-omamobile.conf: Suspend means s2idle. The phone offers "deep" (mem_sleep reads "s2idle [deep]"), and gs201 never wakes from it. - 20-omamobile-gpu-always-on.rules, for Panthor on the Mali-G710 (derekross/linux-omarchy-mobile#129). - 72-omamobile-feedbackd.rules, for the CS40L26 haptics (derekross/linux-omarchy-mobile#130). The udev rules match nothing until a kernel has those nodes. A lone copy of the package (phone-install-package, build-packages --container-check) checks the rules' content instead of comparing them. tools/extract-vendor-firmware -d panther extracts the same gs201 files as cheetah under panther's board name, with the same format checks; cheetah's map is unchanged. device/panther/NOTES.md records the GPU (G1) and haptics (H1) boots with their kernel releases, power off restarting the phone (PSCI SYSTEM_OFF), and USB not coming back after a replug. DEVICES.md and BRINGUP-M1 follow. Tested on the Pixel 7 with 0.1.1 installed through phone-install-package: tools/phone-smoke all ok on 7.3.0-rc6-omamobile-push1-g9ec3a2e38705.
…ross#145) The Pixel 7 gets three files from the Pixel 7 Pro's package, byte-identical and compared by the package test when cheetah's package is beside it: - sleep.conf.d/10-omamobile.conf: Suspend means s2idle. The phone offers "deep" (mem_sleep reads "s2idle [deep]"), and gs201 never wakes from it. - 20-omamobile-gpu-always-on.rules, for Panthor on the Mali-G710 (derekross/linux-omarchy-mobile#129). - 72-omamobile-feedbackd.rules, for the CS40L26 haptics (derekross/linux-omarchy-mobile#130). The udev rules match nothing until a kernel has those nodes. A lone copy of the package (phone-install-package, build-packages --container-check) checks the rules' content instead of comparing them. tools/extract-vendor-firmware -d panther extracts the same gs201 files as cheetah under panther's board name, with the same format checks; cheetah's map is unchanged. device/panther/NOTES.md records the GPU (G1) and haptics (H1) boots with their kernel releases, power off restarting the phone (PSCI SYSTEM_OFF), and USB not coming back after a replug. DEVICES.md and BRINGUP-M1 follow. Tested on the Pixel 7 with 0.1.1 installed through phone-install-package: tools/phone-smoke all ok on 7.3.0-rc6-omamobile-push1-g9ec3a2e38705.
Enables the Mali-G710 on the Pixel 7 (panther), as the Pixel 7 Pro does: one
&gpu { status = "okay"; }ings201-panther.dts. The clock is the ACPM GPU clock the board already gets from gs201.dtsi, and there is nomali-supply, since the G3D rails follow the PMU power domain and ACPM (as on cheetah). The haptics PR builds on this one, because both edit the board file's header comment.The device side is the Pixel 7 Pro's always-on udev rule (powering the GPU domain back up needs a secure call this kernel doesn't make yet), in
omamobile-device-panther0.1.1; that omarchy-mobile PR follows.Tested on a Pixel 7 (slot B, 7.3.0-rc6):
omamobileplus the touch test commit and this one, with the rule installed before the boot:id 0xa862,shader_present=0x1110055), boots the CSF firmware (interface v1.5.0,arm/mali/arch10.8/mali_csffw.bin) and registersrenderD128;Renderer: Mali-G710 MC7 (Panfrost), smooth by eye, with no MMU faults, timeouts or GPU resets indmesg;on/active; probe prints_opp_set_regulators: no regulator (mali), as cheetah does (cheetah's GPU-PLAN calls it harmless).Checks:
tools/kernel-pr-check --build OUT --merge origin/omamobilepasses everything: a clean merge onto 2a318a9, sign-offs, checkpatch --strict with no warnings, and the seven device trees with W=1 and dtbs_check, with no new warnings.🤖 Generated with Claude Code