Repository navigation
Pixel 8a (akita): the first-light board file, with USB, SSH and the boot framebuffer - #192
Conversation
The Pixel 8a (akita) is a zuma (Tensor G3) board like the Pixel 8 Pro (husky). Add its compatible to the zuma board list. Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
Add a first-light board file for the Pixel 8a: husky's first-light file with akita's model, compatible and /soc_compatible children, and USB. zuma.dtsi already describes the first DRAM bank (ABL adds the others), the fixed reservations, the watchdogs, and the PMU with its reboot mode; this file switches on the DWC3 and its two PHYs and carries husky's bootargs. akita's ABL picks the base DTB by /soc_compatible, as husky's does, but a retail 8a has the IPOP package: its live tree's children are B0_IPOP and B1_IPOP (product id 0x9865, pkg_mode 1), the two that Google's zuma-b0-ipop.dts carries, where husky's are FOPLP. Every fixed DRAM reservation in the 8a's live tree lies inside one of zuma.dtsi's, at husky's addresses, except the four that ABL inserts itself (pkvm_guest_firmware, sec_dram, sec_pt and debug_kinfo_reserved). The DWC3, the USB DRD PHY, the UART, the PMU and the watchdogs are at zuma.dtsi's addresses. There is no framebuffer yet: the splash address is read from DPP0 on a running 8a before a carve-out goes in, as on husky. UFS, the buttons, the PMICs, touch and the MAX77759 follow, each once it has run on the phone. Tested on a Pixel 8a (bootloader akita-17.0-15681527): the bootloader boots this tree from slot B, all nine CPUs come up, the watchdog driver stops both cluster watchdogs, and the initramfs brings up the USB gadget and SSH 0.4 s into boot. The booted tree has the bootloader's DRAM banks and its four reservations added, and the kernel reports no reserved-memory overlap. Link: https://android.googlesource.com/kernel/devices/google/akita/+/refs/tags/android-16.0.0_r0.10/dts/zuma-akita-mp.dts Link: https://android.googlesource.com/kernel/devices/google/zuma/+/refs/tags/android-16.0.0_r0.10/dts/zuma-b0-ipop.dts Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
ABL hands over with its splash still scanned out: on a booted Pixel 8a, DPP0's RDMA_BASEADDR_P0 (0x19900040) reads 0xfac00000, as on the Pixel 8 Pro. Describe it as a simple-framebuffer at the panel's native 1080x2400 (a8r8g8b8), with a no-map carve-out so the kernel leaves it alone, as the Pixel 8 Pro's board file does and the 1080x2400 Pixel 7 and 7a ones do. The ak3b panel is in DSI command mode (no mode in Google's panel driver sets MIPI_DSI_MODE_VIDEO), and ABL leaves DECON0's hardware trigger masked (TRIG_CON 0x19470030 reads 0x3070, as on the Pixel 8 Pro), so frames reach the panel only once userspace unmasks it. Tested on a Pixel 8a: simpledrm binds to the framebuffer and fbcon runs at 67x75. With the trigger unmasked, the panel shows what is drawn there, in place and in the right colours, and keeps following later writes. Link: https://android.googlesource.com/kernel/devices/google/akita/+/refs/tags/android-16.0.0_r0.10/display/panel-google-ak3b.c Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
|
Thank you, @aninmucek. This is a tidy board file: husky's first-light file with only what the 8a changes, each value traced to the live tree, Google's GPL trees or a register read on the phone. The framebuffer is in its own commit, after the address was read, as husky's was. What I checked:
CI hasn't run yet because it's waiting for my approval; I'll approve it. The only other thing is the source check for the framebuffer commit that I asked for on omarchy-mobile#414, since that boot was |
From the review of derekross#414: - The status line names derekross/linux-omarchy-mobile#192 and its commits. M1.3's kernel commit, ce160abd9, is derekross#192's 1253914a9 with the same files. M1.4's -dirty run is derekross#192's 6a2999804: the kept DTS is blob 381ad1e0 and the flashed DTB has sha256 9a5d92a5, as derekross#192's. - Risks: every unmarked boot uses one of slot B's tries. If stock boots, decline any factory reset and take a fresh backup. - M1.2 lists the fastboot getvar values instead of a local helper, and the two rollbacks pin the serial. - NOTES.md: the COMPATIBLE and DTB rows point at derekross#192. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for checking it so closely, and for approving CI. The source check is in derekross/omarchy-mobile#414 now, and it matches. The DTS kept with the |
|
Thanks, @aninmucek. The source check matches. Your base has moved by one lynx commit since my last look, so I ran the gate again on today's |
Part of derekross/omarchy-mobile#1 (the zuma phones). This adds a board file for the Pixel 8a (akita), on
zuma.dtsi, in three commits:dt-bindings: arm: google: Add Pixel 8a (akita):
google,zuma-akitain the zuma enum.arm64: dts: exynos: google: Add Pixel 8a (akita) first-light board: husky's first-light file with:
/soc_compatiblechildren its bootloader matches,B0_IPOPandB1_IPOP(product id 0x9865,pkg_mode1; husky's are FOPLP);bootargs;Symbols are kept (
-@) for the bootloader's board overlay.arm64: dts: exynos: google: zuma-akita: Add the boot framebuffer:
simple-framebufferat 0xfac00000, 1080x2400a8r8g8b8, with ano-mapcarve-out, as husky's board file has.Where the values come from:
fastboot getvar all(a retail phone on stock CP3A.261005.005, bootloader akita-17.0-15681527);zuma-akita-mp.dts, zuma'szuma-b0-ipop.dts, and the ak3b panel driver, which setsMIPI_DSI_MODE_VIDEOin no mode, so the panel runs in command mode;RDMA_BASEADDR_P0= 0xfac00000;GLOBAL_CON= 0x133;TRIG_CON= 0x3070, the trigger masked.The full record is in omarchy-mobile's
device/akita/NOTES.mdand inBRINGUP-M1.md, which comes in derekross/omarchy-mobile#414.Tested on a Pixel 8a. The kernel was
7.3.0-rc6-omamobile-push1-gce160abd9ffc-dirty: these three commits' content on 4cf2c8b, with the framebuffer commit not yet committed. Since then the base has gained 8 commits, and none of them touch a zuma file. The three files here are byte-identical to what ran.*_bboot images were written, bybin/omamobile flash.kaslr-seedand the initrd range.reboot-to bootloaderreaches fastboot in 25 s, thanks toreboot=warm.SIMPLEFB_TRIG_CONunmasks DECON0's trigger, the panel shows Omarchy's splash in place and in the right colours, and then console text written over it.dtbs_check's two warnings) andexynos-clkout … -22.Not in this PR: UFS, the buttons, the PMICs, touch and the MAX77759, each of which follows once it has run on the phone. Whether this 8a's silicon is B0 or B1 is still open, since zuma has no chip-id driver here yet.
Checks:
tools/kernel-pr-check --build OUT --merge origin/omamobilepasses everything:checkpatch --strictwith no errors. Its two warnings are both on the first-light commit:MAINTAINERSalready coversarch/arm64/boot/dts/exynos/google/;bootargsline is 204 columns, the same line as in husky's board file;W=1anddtbs_check, with no new warnings. The 8a's two eUSB2-supply messages are the ones husky has at the base;dt_binding_checkongoogle.yaml.🤖 Generated with Claude Code