Repository navigation
arm64: dts: exynos: google: zumapro-tegu: Add the touchscreen - #81
Conversation
e281f81 to
9c410c4
Compare
|
Thanks! I checked the node against Google's One optional point: stock's This merges after #80. A smoke report from the #80 boot that lists touch would cover it. |
4eec839 to
9386dfa
Compare
|
Thanks. I've left |
9386dfa to
8c0c38e
Compare
8c0c38e to
832c8cc
Compare
|
Thanks. I compared the new head with the one I last checked: your touchscreen commit is the same patch, and the tree at this commit is identical ( This branch needs the Makefile rebase I described on #80, like the rest of the stack: today's Nothing else is needed on this PR. Touch will be covered by the boot of #96's head that I asked for on #80, where the smoke report's touch row should read "ok". This lands with #96, and I'll close it then. |
… 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>
The Pixel 9a's touchscreen is a Synaptics S3908 on SPI20 (HSI0's USI2, dedicated pads, native chip select), with its attention line on the custom-alive bank gpn0, which raises its own interrupt, and its reset on gpp1-1. The S2MPG14 supplies it from LDO25M (VDD) and LDO4M (AVDD). The USI's default pin state holds the controller in reset while the USI probe switches to SPI; the touch driver then releases it. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
832c8cc to
4d0a85f
Compare
|
Merged, thank you, @W4HO-ham. All five commits ran on the 9a in exactly this form (the board in the 10-28 boot, touch "ok" in the 10-29 boot of |
Stacked on #80 (the Tensor G4 SoC and the first-light Pixel 9a board). Only the last commit is new.
This adds the Pixel 9a's touchscreen to
zumapro-tegu.dts:The USI's default pin state holds the controller in reset while the USI probe switches to SPI, and the driver releases it.
Against the palmtop: these nodes match the running DTB property for property (the same node-by-node comparison as #80: phandles resolved to paths, clocks to names). It's the touchscreen in daily use on the 9a, with the S3908 supply sequencing from #26.
CHECK_DTBS=y W=1forzumapro-tegu.dtbis clean, and checkpatch --strict is clean.