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>
Describe the CS40L26A haptics driver at 0x43 on USI8 I2C, as on the Pixel 7 Pro: the same bus (gpp16-0/1 at 400 kHz), interrupt (gpa8-1) and reset (gpp24-3) as the Pixel 7 Pro, and the same stock boost and actuator values (peak current 2.5 A, boost 11 V, f0 145 Hz, ReDC 13 ohm), all read from the Pixel 7's live device tree. Enable the PERIC0 pin controller, USI8 and its I2C bus with it. The driver loads its RAM firmware (cs40l26.wmfw) and, if present, the wavetable (cs40l26.bin), from the phone's own vendor files; without the firmware it does not probe. Tested on a Pixel 7 from slot B (7.3.0-rc6), with the GPU enabled as well: cs40l26-vibra probes the CS40L26 (ID 0x40a260, revision A1), loads cs40l26.wmfw (v7.2.91) and cs40l26.bin, and registers cs40l26_vibra; FF_RUMBLE effects of 100-500 ms at 25-80 % play through tools/ff-rumble and are felt, with no errors from the driver. Assisted-by: Claude Opus 5.5 Signed-off-by: Alejandro Garcia <skipper.pelygro@gmail.com>
|
Thank you, @nesmeck. The haptics node is the Pixel 7 Pro's, line for line, and the values also match Google's shared Since the node is already proven on the Pixel 7 Pro and passed on your Pixel 7, adding it enabled in one commit fits the exception in CONTRIBUTING. Without the phone's own Nothing blocks. As with #129, I plan to land this through #134 (rebase merge, so your commits keep their messages), after derekross/omarchy-mobile#145 with the firmware mapping and the feedbackd rule. |
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.
Describes the CS40L26A haptics driver on the Pixel 7 (panther). This PR builds on #129 (the GPU): it carries that commit too, because both edit the board file's header comment. Please merge #129 first; this one then adds a single commit.
The node is the Pixel 7 Pro's, and so are the values, all read from the Pixel 7's live device tree:
hsi2c_8, gpp16-0/1, 400 kHz);It enables the PERIC0 pin controller, USI8 and its I2C bus. The driver needs the phone's own RAM firmware (
cs40l26.wmfw) and loads the wavetable (cs40l26.bin) if present. Both come from the user's factory image through omarchy-mobile'stools/extract-vendor-firmware -d pantherand are never redistributed. That omarchy-mobile PR (with the feedbackd rule) follows.Tested on a Pixel 7 (slot B, 7.3.0-rc6):
omamobileplus the touch test commit, #129's commit and this one, with the firmware in/usr/lib/firmware/updates:cs40l26-vibrafinds the CS40L26 (ID 0x40a260, revision 0xa1), loadscs40l26.wmfw(firmware 0x1800d4, v7.2.91, 13 algorithms) andcs40l26.bin, and registerscs40l26_vibra;tools/ff-rumbleeffects of 100-500 ms at 25-80 % play and are felt, and the driver logs no errors;vdd-a/vdd-pfall back to dummy regulators, as on cheetah, since the bootloader leaves the rails on.Checks:
tools/kernel-pr-check --build OUT --merge origin/omamobilepasses everything for both commits: 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