Skip to content

device/tegu MODEM-PLAN: where stock's values for the GNSS handshake pins come from - #679

Merged
derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-gnss-pins-source
Nov 12, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
W4HO-ham:tegu-gnss-pins-source

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The small thing left from #590's review: the two stock values the pin readings are compared with now name their source. gpa5-4 is gnss_spi_irq under &pinctrl_2 (an interrupt, pull-down, drive 0, kept as it was in power-down), gpp2-3 is gnss_spi_int under &pinctrl_11 (an output, no pull, drive 0), both in Google's zuma-cp-s5400-phone-gnss.dtsi, where gnssif's pinctrl-0 names them. The plan links the file at the commit it was read at, the same one FAR-ALIVE-PLAN cites.

One sentence in section P of tegu's MODEM-PLAN; nothing else changes. tools/pr-check origin/main passes.

…ins come from

The readings of the two pins were compared with "stock's" pull and function without saying which file has them. They are the groups gnss_spi_irq (gpa5-4) and gnss_spi_int (gpp2-3) in Google's zuma-cp-s5400-phone-gnss.dtsi, named by gnssif's pinctrl-0; the plan now says so and links the file at the commit it was read at.
@derekross

Copy link
Copy Markdown
Owner

Thank you, this is exactly the small thing I asked for on #590. I fetched Google's zuma-cp-s5400-phone-gnss.dtsi at the commit you link and every value is there as you give it: gnss_spi_irq under &pinctrl_2 on gpa5-4 as an interrupt with the pull-down at drive 0 and the pin kept as it was in power-down, gnss_spi_int under &pinctrl_11 on gpp2-3 as an output with no pull at drive 0, and gnssif's pinctrl-0 naming both. I also looked at Google's tegu board files for an override of either group and found none (the only GNSS file there sets gnss-type), so the values hold for the 9a. Using the same commit FAR-ALIVE-PLAN cites is a nice touch. Merging.

@derekross
derekross merged commit 68e1929 into derekross:main Nov 12, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ins come from (derekross#679)

The two stock values the 2026-11-10 pin readings are compared with now name their source: `gnss_spi_irq` (gpa5-4) and `gnss_spi_int` (gpp2-3) in Google's `zuma-cp-s5400-phone-gnss.dtsi`, linked at the commit FAR-ALIVE-PLAN cites. This was the one point left open when derekross#590 merged. Checked against the file at that commit, and against Google's tegu board files for an override (none).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants