Repository navigation
arm64: dts: exynos: google: gs201-panther: describe the GNSS receiver - #268
angelrenefm wants to merge 1 commit into
Conversation
|
Thank you, Ángel. I compared the new blocks with the Pixel 7 Pro's in One thing stops it from working as proposed. Could you pick one of these?
Either way, please mention in the comment above On order: this and #181 don't conflict with each other. #195 will need a rebase after whichever of them lands first. |
The Pixel 7's stock dtbo for board 0x30406 (the one ABL picks on this phone) describes the GNSS receiver exactly as the Pixel 7 Pro's (board 0x30306): the spi5 node with its bcm4775@0 child at 26 MHz in mode 3, host_req on gpa6-4, mcu_req on gpp4-3, mcu_resp on gph2-2 and nstandby on gph2-3, with the same pin settings; the two fragments compare equal. Google's source has one file for both, gs201-common-gps.dtsi in kernel/devices/google/gs201 (android-gs-pantah-6.1-android16). Its supplies are the S2MPG13's L9S_GNSS_CORE, L10S_GNSS_RF and L11S_GNSS_AUX, with the same ranges as cheetah's (0.725-1.3 V, 1.6-1.95 V, 1.6-1.95 V), from the shared gs201-pmic.dtsi. So add cheetah's gnss@0 node on USI5's SPI, its pin groups, and the three LDOs in the sub-PMIC node. The LDOs are disabled, as LDO15S is, because the fingerprint overlay enables the sub-PMIC on this phone; USI5 and its SPI stay disabled as in gs201.dtsi. A bring-up overlay (omarchy-mobile's device/panther/overlays/gnss.dtso) turns them on, together with gph2's pin controller (pinctrl_hsi2, disabled in gs201.dtsi), which mcu_resp and nstandby need. Assisted-by: LLM Signed-off-by: Ángel René <17342133+angelrenefm@users.noreply.github.com>
9e5ac89 to
cadbb95
Compare
|
Thank you, Derek, good catch: my phone's tree has #195, which turns Checked here: Not done yet: the boot you asked for (today's I used AI help (Claude) to work on this. |
|
The boot you asked for, on 2026-11-18: today's How: a kexec from the phone's usual kernel with that DTB ( After the boot, before anything else:
Not checked: the fingerprint sensor on this boot. Trusty doesn't come back after a kexec ( I used AI help (Claude) to work on this. |
The Pixel 7's GNSS receiver, described as the Pixel 7 Pro's. One commit, device tree only.
The stock panther dtbo (board 0x30406) has the same spi5 node,
bcm4775@0child and four GPS pin groups as cheetah's (0x30306); Google's source has one file for both,gs201-common-gps.dtsiinkernel/devices/google/gs201(android-gs-pantah-6.1-android16), and the rails come from the sharedgs201-pmic.dtsi. So this adds cheetah'sgnss@0on USI5's SPI, its pins, and LDO9S-LDO11S in panther's sub-PMIC node, next to the fingerprint's LDO15S. Everything stays disabled; the overlay that turns it on is omarchy-mobile#861.tools/kernel-pr-check --buildonto today'somamobile:Tested on a Pixel 7. Its kernel has run this node since 4 Nov (a local build). This branch's
gs201-panther.dtbagainst the phone's live tree:gnss@0, the four pin groups and the three LDOs have the same properties, apart from phandles andstatus.omamobile-gnss forcefor 20 s:bcm4775x-gnssbinds onspi0.0, the chip powers up, and/run/omamobile-gnss/nmea-ttygives 1089 sentences (GPS, GLONASS, Galileo, BeiDou and QZSS GSA), with no fix indoors.omamobile-gnss offpowered it down again.Not tested: this exact tree on the phone (the running kernel is a local build with the same node), and the overlay through
omamobile-boot-update.I used AI help (Claude) to work on this.