From d97bc39190cd1d26a8a4d97ae538434eaffe360b Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 12:39:05 -0647 Subject: [PATCH 1/5] kernel config: build in the Pixel 9a's USB PHY and the PMIC path it is powered through A kernel built from omamobile.config booted the 9a without USB: the eUSB2 PHY was a module, and the PHY's rails come from the S2MPG14 PMIC through ACPM and the APM mailbox, also modules. The initramfs loads no modules, so USB never came up. With the four built in, a build of linux-omarchy-mobile#96 boots with USB networking and SSH. --- kernel/configs/omamobile.config | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 5bb1b64c3..90b7dbee4 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -37,6 +37,14 @@ CONFIG_IKCONFIG_PROC=y CONFIG_ARCH_EXYNOS=y CONFIG_EXYNOS_PMU=y CONFIG_PHY_EXYNOS5_USBDRD=y +# The Pixel 9a's (zumapro) USB 2.0 runs through a Synopsys eUSB2 PHY; as a +# module (defconfig) the initramfs has no USB and its safety net reboots +CONFIG_PHY_SNPS_EUSB2=y +# Its USB PHY's rails come from the S2MPG14 PMIC, reached only through ACPM +# over the APM mailbox: built in too, or the PHY waits for its supplies +CONFIG_EXYNOS_MBOX=y +CONFIG_EXYNOS_ACPM_PROTOCOL=y +CONFIG_MFD_SEC_ACPM=y CONFIG_USB_LIBCOMPOSITE=y CONFIG_FRAMEBUFFER_CONSOLE=y From 1c5d69c90a09e9db224db1993ebef5e0ae94e969 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 13:23:55 -0647 Subject: [PATCH 2/5] kernel config: the Pixel 9a's MAX77779 fuel gauge and charger Both drivers are merged in the kernel but were off in the fragment, so a kernel built from it had no battery or charger on the 9a. With them as modules, a boot of the charger device tree shows both supplies, and charge inhibit works. --- kernel/configs/omamobile.config | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 90b7dbee4..6bfdb47e7 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -137,6 +137,9 @@ CONFIG_BT_HCIUART_BCM=y CONFIG_MFD_MAX77759=m CONFIG_CHARGER_MAX77759=m CONFIG_BATTERY_MAX17042=m +# The Pixel 9a's MAX77779 fuel gauge and charger (both drivers merged) +CONFIG_BATTERY_MAX77779=m +CONFIG_CHARGER_MAX77779=m # Display bring-up (device/cheetah/DISPLAY-PLAN.md): a DSI command path on # the bootloader's DSIM0 and the S6E3HC4 panel, for brightness and display From d977421fd7ba2610dd4db0b3aff6816a0be6f8d7 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 16:47:35 -0647 Subject: [PATCH 3/5] kernel config: the Pixel 9a's RT6160 camera regulator The main camera's supply chain includes an RT6160, whose driver was off in the fragment. With it, linux-omarchy-mobile#164's cameras power up and all three stream. --- kernel/configs/omamobile.config | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 6bfdb47e7..6725a1500 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -140,6 +140,8 @@ CONFIG_BATTERY_MAX17042=m # The Pixel 9a's MAX77779 fuel gauge and charger (both drivers merged) CONFIG_BATTERY_MAX77779=m CONFIG_CHARGER_MAX77779=m +# The Pixel 9a's camera power: the RT6160 buck-boost behind the main camera +CONFIG_REGULATOR_RT6160=m # Display bring-up (device/cheetah/DISPLAY-PLAN.md): a DSI command path on # the bootloader's DSIM0 and the S6E3HC4 panel, for brightness and display From e061496c0de592cac3a222a38d2c6a3862ddf70b Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 17:12:16 -0647 Subject: [PATCH 4/5] kernel config: the Pixel 9a's PCIe channel-1 host for Wi-Fi linux-omarchy-mobile#168's pcie_zumapro, as a module: the device package's hang-safe start loads it, and built in it would probe at boot without the marker. --- kernel/configs/omamobile.config | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 6725a1500..173f86a1e 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -142,6 +142,9 @@ CONFIG_BATTERY_MAX77779=m CONFIG_CHARGER_MAX77779=m # The Pixel 9a's camera power: the RT6160 buck-boost behind the main camera CONFIG_REGULATOR_RT6160=m +# The Pixel 9a's PCIe channel-1 host for Wi-Fi: a module, loaded by the +# device package's hang-safe start, never built in (it would probe at boot) +CONFIG_PCIE_ZUMAPRO=m # Display bring-up (device/cheetah/DISPLAY-PLAN.md): a DSI command path on # the bootloader's DSIM0 and the S6E3HC4 panel, for brightness and display From c62a709bd569136f48a7002c6dbeaf423ec5b32f Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Sat, 31 Oct 2026 17:12:35 -0647 Subject: [PATCH 5/5] kernel config: the Pixel 9a's TAS2572 speaker amplifiers The tas2781 I2C driver drives the 9a's two TAS2572s; the device package's AoC start loads it once the AoC is online (linux-omarchy-mobile#162). --- kernel/configs/omamobile.config | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kernel/configs/omamobile.config b/kernel/configs/omamobile.config index 173f86a1e..b292415ce 100644 --- a/kernel/configs/omamobile.config +++ b/kernel/configs/omamobile.config @@ -145,6 +145,9 @@ CONFIG_REGULATOR_RT6160=m # The Pixel 9a's PCIe channel-1 host for Wi-Fi: a module, loaded by the # device package's hang-safe start, never built in (it would probe at boot) CONFIG_PCIE_ZUMAPRO=m +# The Pixel 9a's TAS2572 speaker amplifiers (tas2781 driver), loaded by the +# AoC start once the AoC is online +CONFIG_SND_SOC_TAS2781_I2C=m # Display bring-up (device/cheetah/DISPLAY-PLAN.md): a DSI command path on # the bootloader's DSIM0 and the S6E3HC4 panel, for brightness and display