Repository navigation
Pixel 8a (akita): enable UFS, as on the Pixel 8 Pro - #206
Conversation
The Pixel 8a's UFS is wired as the Pixel 8 Pro's. Its live device tree has the host at 0x13200000 (SPI 466) with the same six register regions, the reset and reference-clock pins on gph5-1 and gph5-0 (function 2), the UFS sysreg at 0x13020000 (IOCC 0x710), the PMU isolation at 0x3ec0, and VCC on a fixed regulator switched by gpp0-1, active high, as Google's zuma-ufs.dtsi describes it for every zuma board. ABL hands the device over with VCC off, so the driver has to turn it on. zuma.dtsi already describes the host, its PHY, the pins and the clock stand-ins. Add the VCC regulator and enable the host and its PHY, the same nodes zuma-husky.dts has. Tested on a Pixel 8a, with the initramfs's storage guard: the link comes up at HS-G4 on two lanes, rate series B, as on stock. The four LUNs and all 62 partitions appear with stock's names on stock's device nodes, a 64 MiB direct read runs at 1.5 GB/s, and the log has no UFS error, reset or I/O error. Link: https://android.googlesource.com/kernel/devices/google/zuma/+/refs/tags/android-16.0.0_r0.10/dts/zuma-ufs.dtsi Assisted-by: Claude Opus 5.5 Signed-off-by: DarekM <149845949+aninmucek@users.noreply.github.com>
|
Thank you, @aninmucek. This one is easy to check: the three nodes are the Pixel 8 Pro's, your One small thing, if you're willing: the comment above I'll merge this first, then #456. |
|
Thanks for merging! The comment fix is up as #214, with the wording you suggested. It is comment-only: on today's |
Part of derekross/omarchy-mobile#1. One commit, on today's
omamobile(29a7a93):gpp0-1, active high;vcc-supplyandstatus = "okay"onufs_0;ufs_0_physwitched on.Why husky's nodes fit. akita's live device tree has every UFS value where husky's does:
brd-for-cal1;gph5-1andgph5-0(function 2);gpp0-1, which Google's GPLzuma-ufs.dtsidescribes for every zuma board.The nodes are enabled in one commit under CONTRIBUTING §6.2's exception for a node proven on a same-SoC phone, now that it has passed on this one.
Tested on a Pixel 8a. The kernel was
7.3.0-rc6-omamobile-push1-g29a7a9326bf0-dirty: this commit's DTS on 29a7a93 before it was committed, byte-identical (blobbfa8b6f54e0e). It booted from slot B into the initramfs, withomamobile.ufs-probe omamobile.initramfsfrom a bring-up overlay, so nothing ran onuserdata.Power mode changed to : FAST series_B G_4 L_20.24 s into boot, as on stock. The device isKLUDG4UHGC-B0E1, rev 3203.userdatawritable.sdb-sddare read-only, and/dev/sdais removed.boot_bran at 1.5 GB/s. About 2 GB of read-only backup reads followed (tools/nv-backupand a full partition set) with no UFS error, reset or I/O error.ufshcd_populate_vregassumesvdd-hba,vccqandvccq2are on, as on the Pixel 8 Pro.The runbook and its results are in derekross/omarchy-mobile#456 (
device/akita/BRINGUP-M2.md, M2.1-M2.4).Checks:
tools/kernel-pr-check --build OUT --merge origin/omamobilepasses everything:checkpatch --strictwith no errors and no warnings;W=1anddtbs_check, with no new warnings.🤖 Generated with Claude Code