Repository navigation
Conversation
8392ff2 to
5926c67
Compare
|
Thank you for this. A first SoC and board file for the Tensor G4 is a big step, and it's careful work: everything disabled in the dtsi, the
Two things before I merge:
Smaller things, none blocking:
Thanks again. This is the base everything else for the 9a builds on, and it reads very cleanly. |
fd1ee01 to
87e87a9
Compare
|
Thanks for checking it so thoroughly. Pushed, rebased onto today's
On the smaller points:
|
|
Thanks. Thanks for the other answers too:
What's left is the boot of this tree, as you said: On my side the stack checks out on today's |
87e87a9 to
ebd7e5e
Compare
|
The reserved-memory note is in omarchy-mobile #100 ( |
|
Thanks for the reserved-memory note in omarchy-mobile #100. It says exactly what I asked, including that the two gaps come from the early bring-up map rather than a public source. Last night's push reached every branch this time. The stack is now one line on today's
So the only thing left is the boot. Since the whole stack can now land at once, please boot its top (#96's head) rather than this PR alone, so the test covers exactly what lands. I'd like to see After that I'll rebase-merge #96 on its own, which lands all twelve commits, and close #80, #81, #85, #87 and #90 as landed there. |
|
Booted this head on the palmtop this morning:
Every required check passes: boot, storage guard, root, kernel health (no oops or BUG), USB gadget. The "not ok" rows are what this PR doesn't describe yet: display (#90), GPU (#85), touch (#81) and cameras. So this PR's tree on its own gives a headless system that gets past the watchdogs, with storage and USB. Next I'll add the "Tested on" line to the board commit, then rebase the stack onto |
ebd7e5e to
f2827cb
Compare
|
Thank you for the boot report and the "Tested on" paragraph. The tree you booted ( Two things before the stack can land:
One heads-up for the order: kernel #55 (S2MPG14 interrupt and RTC) makes After that, I'll rebase-merge #96, which lands all twelve commits, and close #80, #81, #85, #87 and #90 as landed there. |
… PERIC1 Add the Tensor G4 (zumapro) system-register blocks the SoC's USIs select their mode through: APM (one UART), HSI0 (two SPI buses and an I2C bus) and PERIC1 (one I2C bus). Each block's interface clock is a gate the Tensor G4 clock driver exports, so they list clocks, as PERIC0 and UFS do. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
The Tensor G4 (zumapro) UART behind the APM's USI1 works as gs101's, with a 256-byte FIFO, so add it with google,gs101-uart as the fallback, as gs201 does. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Add zumapro.dtsi, the Tensor G4 SoC as far as Linux drives it today: the CPUs, PSCI, the timer and GIC, every CMU with a driver (TOP, MISC, APM, HSI0, HSI1, HSI2, PERIC0, PERIC1, G3D), the eight pin controllers and their banks, the system registers the USIs and UFS use, the PMU with its reboot mode, both cluster watchdogs, the APM mailbox and SRAM for ACPM, UFS and its PHY, the USB 2.0 path (dwc3, the USB 3.2 DRD PHY wrapper and the eUSB2 PHY), the USIs behind the cameras', battery's, haptics', NFC's, touchscreen's and GNSS's buses, the Bluetooth UART, DECON and the Mali GPU. Everything a board doesn't need is left disabled; zumapro-tegu.dts turns on what the Pixel 9a uses. zumapro-reserved-memory.dtsi carries the fixed firmware regions from Google's GPL zumapro tree, the xhci pools of zuma-usb.dtsi (which zumapro-usb.dtsi includes), and two small gaps next to them that the earlier bring-up kept reserved; they stay reserved until shown unused. Addresses, interrupts and bank layouts come from Google's GPL zumapro device tree; clock ids and parents from the Tensor G4 clock driver. Link: https://android.googlesource.com/kernel/devices/google/zumapro/+/8831630eee2ad095b85ed452944e6353940966a5/dts/zumapro.dtsi Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Add a first-light board file for the Pixel 9a (tegu): ABL's selector nodes for its A0 and A1 IPOP parts, the clocks, pins, system registers and PMU, both watchdogs, ACPM with the S2MPG14's two eUSB2 supplies, UFS behind its GPIO-switched VCC, USB 2.0 peripheral and the three keys. That is enough to boot the root file system from UFS and reach it over USB networking. Display, touch, battery, sound and the radios follow in their own changes. The bootargs pick suspend to idle: the firmware advertises PSCI SYSTEM_SUSPEND, but Linux has no Tensor SoC sleep sequence for "deep". The USB core also holds CMU_HSI0's sub-control clock: it clocks the link's registers, the PHY turns it off in suspend, and dwc3 touches those registers before it initialises the PHY again on resume. Tested on the Pixel 9a: a kernel built from this tree with its zumapro-tegu.dtb boots to the root file system on UFS, reachable over USB networking, and stays up past the bootloader watchdogs (85 s at the check). tools/phone-smoke passes boot, the storage guard, root, kernel health and USB gadget. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
f2827cb to
94e632c
Compare
|
Closing as landed: these commits went in with #81, thank you. |
Rebased onto
omamobilenow that the clock series (#73-#79) is merged. Only these four commits remain.This adds the Tensor G4 SoC device tree and a first-light Pixel 9a board, in the same spirit as
zuma-husky.dts:dt-bindings: soc: samsung: exynos-sysreg: the APM, HSI0 and PERIC1 system registers, the blocks the USIs select their mode through. Each lists its clock, as PERIC0 and UFS do.dt-bindings: serial: samsung:google,zumapro-uart, withgoogle,gs101-uartas the fallback, as gs201 does.zumapro.dtsiandzumapro-reserved-memory.dtsi: CPUs, PSCI, timer, GIC, every CMU with a driver, the eight pin controllers, the system registers, the PMU with reboot mode, both watchdogs, the APM mailbox and SRAM for ACPM, UFS and its PHY, USB 2.0 (dwc3, DRD PHY, eUSB2 PHY), the USIs and their I2C/SPI/UART children, DECON and the GPU. All are disabled unless a board turns them on. Thesocchildren are sorted by address. Theect,dpmanddpm-stubsnodes are ABL's overlay targets, as on zuma.zumapro-tegu.dts: ABL's selector nodes for the A0/A1 IPOP parts, the clocks, pins, sysregs and PMU, both watchdogs, ACPM with the S2MPG14's eUSB2 supplies, UFS with its GPIO-switched VCC, USB 2.0 peripheral, and the three keys. Display, touch, battery, sound and the radios come in later changes, one each.Checks:
CHECK_DTBS=y W=1forzumapro-tegu.dtbis clean, with no dtc warnings and no schema errors.dt_binding_checkpasses for both schemas. checkpatch --strict on the series shows only the MAINTAINERS question for the new files.Against the palmtop: I compared this DTB node by node with the one the Pixel 9a boots now (the integration kernel,
7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty), using a script that resolves phandles to paths and clock specifiers to their names in each tree's header. Every node and property here exists there with the same value. The only differences are the intended ones:chosen/bootargsis shorter;google,zumapro-ufs-sysreg(from dt-bindings: Pixel 9a (tegu) board and zumapro UFS sysreg #60);I haven't booted this tree's own kernel on the palmtop yet. That's next, and I'll post the result here.