Repository navigation
device/panther: a bring-up overlay for GNSS - #861
angelrenefm wants to merge 2 commits into
Conversation
The Pixel 7 describes its BCM4775x receiver as the Pixel 7 Pro does (one gs201-common-gps.dtsi in Google's source), so the kernel gets cheetah's node for panther, disabled, and this overlay turns on what it needs: the sub-PMIC, LDO9S-LDO11S, USI5 and its SPI. Not in DTB_OVERLAYS. The dated NOTES entry has what was tested on a Pixel 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, Ángel. I built panther's device tree from linux-omarchy-mobile#268 and applied your overlay to it: it changes exactly the six Two additions to the NOTES entry before I merge it:
Two small things in the same push: name the kernel pull request by number (linux-omarchy-mobile#268) and say the overlay needs a kernel with it. On today's published kernel When you do boot a kernel with #268 and this overlay, a dated result with the |
…to try it Review on derekross#861 and linux-omarchy-mobile#268: mcu_resp and nstandby are on gph2, whose pin controller is disabled in gs201.dtsi, so the overlay turns it on. The NOTES entry names the kernel PR, says omamobile-gnss goes in first (its blacklist), what the first boot should show and the way back, and gives the kernel release and omamobile-gnss versions of the 2026-11-04 run and of the 2026-11-17 indoor one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, Derek. Both additions are in the NOTES entry. Both runs were on I used AI help (Claude) to work on this. |
The overlay that turns on the Pixel 7's GNSS receiver, for linux-omarchy-mobile#268 (the node, its pins and rails, all disabled, described as the Pixel 7 Pro's).
device/panther/overlays/gnss.dtsosetsstatus = "okay"on the sub-PMIC, LDO9S-LDO11S, USI5 and its SPI, by path. That is cheetah'sgnss-pmic-test.dtsoandgnss-test.dtsoin one. It isn't inDTB_OVERLAYS, so no Pixel 7 gets it by default.device/panther/NOTES.mdhas a dated entry with where the description comes from and what was tested.Tested:
dtc -@and applied withfdtoverlayto omamobile-shell 0.2.68: a wake by the Pixel 9a's power key lights the lock screen #268'sgs201-panther.dtb: those sixstatuslines change and nothing else.fingerprint-sensor.dtso.Not tested: a boot with it through
omamobile-boot-update(it needs #268 merged and published first).tools/pr-checkpasses.I used AI help (Claude) to work on this.