Skip to content

arm64: dts: exynos: google: zumapro-tegu: Add the Kepler GNSS link - #237

Merged
derekross merged 1 commit into
derekross:omamobilefrom
W4HO-ham:tegu-dt-gnss
Nov 10, 2026
Merged

derekross merged 1 commit into
derekross:omamobilefrom
W4HO-ham:tegu-dt-gnss

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

The Pixel 9a's GNSS receiver is the Kepler core in its S5300 modem; its data go over spi21 (USI3 of HSI0) in 64-byte blocks, paced by two handshake lines. gnssif_spi (#185) drives both, but the board's device tree had neither node, so the driver could only be tried from a bring-up overlay. This adds the SPI device, the handshake node, and enables the USI.

The bus keeps zumapro's SPI port configuration. My first version gave the bus gs101's compatible alone, for the controller's automatic chip select, as stock has it for this device. On the palmtop that worked, but spi-s3c64xx then cut each 64-byte block into 60 and 4 bytes (poll_full_fifo is zumapro's), and 12 of those reads timed out in 13 minutes over two GNSS sessions (gnss_spi spi1.0: I/O Error: rx-1 tx-0 rx-f tx-p len-4 ... res-(-110), then len-60). With zumapro's compatible kept (a block in one piece, polled; chip select held per message) two more sessions and 10 minutes of link cycling logged none. The feedback delay is stock's 0 in both. The bus has no pin group: it runs on the bootloader's pin state, as #151's closing found sufficient.

Tested on the palmtop (2026-11-09, 7.3.0-rc6-omamobile-push1-g773b4102f5ec: omamobile at abcd6aac51cf plus #224, #236 and this change's first version, then this version's DTB on the same Image; defconfig, the shared config, omarchy-mobile#274's PCIe PHY and CONFIG_EXYNOS_GNSS_IF_SPI=m; the modem from the in-tree CPIF with omarchy-mobile#594's overlay):

  • with this DTB: two 150 s sessions through the Location switch's socket, 105 of 107 and 142 of 144 GGA sentences fixed, up to 21 satellites, no SPI error line, no UFS error-handler pass; a third boot the same way, and an incoming call on it;
  • with the first version: 108 of 113 and 142 of 143 fixed, and the 12 timeouts above;
  • without the modem (the modules blacklisted by the device package, omarchy-mobile#594): nothing probes, and a Power-key wake from s2idle on that boot was clean.

CHECK_DTBS=y for zumapro-tegu.dtb is quiet, checkpatch is quiet. Nothing changes for other boards: the nodes are in zumapro-tegu.dts only.

The Pixel 9a's GNSS receiver is the Kepler core in its S5300 modem. Its
data go over an SPI bus of the application processor, USI3 of HSI0
(spi21), in 64-byte blocks paced by two handshake lines; gnssif_spi
drives both. Add the SPI device and the handshake node, and enable the
USI.

The bus keeps zumapro's port configuration, with which spi-s3c64xx
moves a 64-byte block in one piece. With gs101's compatible alone
(the controller's automatic chip select, as stock uses for this
device) the driver cut each block into 60 and 4 bytes, and in two
sessions on the phone 12 of those reads timed out (-110) in 13
minutes; with zumapro's, two more sessions had none. The feedback
delay is stock's 0. The bus has no pin group: it runs on the
bootloader's pin state, which the data were clean with.

Nothing probes until the modules load, and the core answers only while
the modem is up and the GNSS daemon has loaded its firmware.

Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, @W4HO-ham. It's good to see GNSS move from the bring-up overlay into the board file, and I appreciate that you tested both bus configurations and wrote down why the one you kept is the right one.

I checked the wiring against the file tegu's stock DT actually includes, zuma-cp-s5400-phone-gnss.dtsi: gpa5-4 and gpp2-3, spi_21 with gnss@0, 3.125 MHz and feedback delay 0 all match (the generic zumapro GNSS files name other pins, so that was worth a look). The polarity follows our binding, spi21 is USI3 of HSI0 in our dtsi as in stock's alias table, and only the 9a includes these files. Our gate passes on today's omamobile, CI's dtbs_check is green, and it merges cleanly with #236. I'll merge it right after that one.

Three things for afterwards, none of which hold this:

  • Sleep. This turns on an SPI controller in HSI0 on every boot, and the record on this DTB is one Power-key wake. Now that arm64: dts: exynos: google: zumapro-tegu: the main PMIC's interrupt, so the RTC alarm wakes the Pixel 9a #236 gives you the alarm, could a short RTC-woken series on a build with this DTB go into SLEEP-PLAN?
  • The handshake pins. Stock gives the node pin groups (gpa5-4 as an interrupt with a pull-down, gpp2-3 as an output with no pull, drive 0), and here they run on the bootloader's state. The pull-down the bootloader leaves on GPA5 matches stock; for gpp2-3 I couldn't find a reading. Could you add the two pins' CON/PUD/DRV from the pinctrl debugfs file to the plan (one controller per read)? If you later want the groups in the board file, that's its own change and its own boot.
  • A wording nit: "Nothing probes until the modules load" isn't quite it, since the USI and the SPI controller are built in and do probe; it's the two GNSS drivers that wait.

On my side: the drivers aren't built by the shared config yet, so this is inert until omarchy-mobile#594. When that goes in I'll make sure device-tegu with the blacklist is published no later than the first kernel with the option, so nobody's 9a autoloads the GNSS modules without the modem.

@derekross
derekross merged commit 253208c into derekross:omamobile Nov 10, 2026
1 check passed
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Thank you for checking the wiring against the file tegu really includes.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The two handshake pins, read on 2026-11-10 on a build of the published tree (plus #224) with the modem-cpif overlay applied and the modem unit masked, so before any GNSS driver had requested them; one controller per read:

154e0000.pinctrl: pin 4 (gpa5-4) 4:gpa5  CON(0x0) DAT(0x0) PUD(0x1) DRV(0x0)
10840000.pinctrl: pin 12 (gpp2-3) 3:gpp2  CON(0x0) DAT(0x0) PUD(0x1) DRV(0x0) CON_PDN(0x2) PUD_PDN(0x1)

gpa5-4 is an input with the pull-down, as stock has it. gpp2-3 is an input with a pull-down too, where stock's group has an output with no pull: the driver makes it an output when it loads, and nothing in the tree sets its pull, so the GNSS sessions most likely ran with that pull-down under a driven line. I haven't read the pins with the drivers loaded. The readings are in tegu's MODEM-PLAN, section P, with omarchy-mobile#590 (commit 05943847).

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