Skip to content

arm64: dts: exynos: google: Add Pixel 6a (bluejay) first-light board - #179

Merged
derekross merged 2 commits into
derekross:omamobilefrom
PeterXMR:omamobile-gs101-bluejay-dts
Nov 2, 2026
Merged

derekross merged 2 commits into
derekross:omamobilefrom
PeterXMR:omamobile-gs101-bluejay-dts

Conversation

@PeterXMR

@PeterXMR PeterXMR commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

Add a first-light board file for the Pixel 6a: oriole's board file with
bluejay's model and compatible, without oriole's two board-specific
LDOs. Everything it enables, it enables as oriole's does, through
gs101-pixel-common.dtsi: the console UART, USB, both cluster
watchdogs, UFS and its PHY, the S2MPG10/11 regulators, the MAX77759
Type-C controller, fuel gauge and PMIC, and the battery EEPROM. The GPU
stays disabled, and there is no panel or touch node. The first commit
adds the compatible to the gs101 board binding.

bluejay boots the same two gs101 base device trees as oriole and raven:
Google's bluejay tree builds every bluejay board overlay on
gs101/gs101-a0.dtb and gs101/gs101-b0.dtb, whose soc_id is 0x09845000
and 0x09845001. So this DTB carries the B0 value as oriole's does, and
the image tooling writes the A0 copy from it.

The panel is a 1080x2400 S6E3FC3 variant (samsung,s6e3fc3_6a in
Google's gs101-bluejay-display.dtsi), oriole's size, so the splash
carve-out and the simple-framebuffer keep oriole's values. The retail
board overlay is MP 1.0, board_id 0x20506 and board_rev 0x10000; the
board dtbo for ABL and the image packing live in the omarchy-mobile
repository (device/bluejay).

Oriole's ldo14m (avdd18_tcxo) and ldo31m (nfc) are left out. Upstream
marks both as board specific, and Google's bluejay tree takes both from
the shared gs101-pmic.dtsi, regulator-always-on there: L14M_AVDD_TCXO,
and L31M, which gs101-whitefin2-pmic.dtsi (included by bluejay and by
oriole) renames to L31M_DISP_VDDI. Left undescribed, they stay as the
bootloader leaves them, as on raven.

Not booted yet: no Pixel 6a has run this tree. Every value comes
from Google's GPL bluejay and gs101 device trees (android-16.0.0_r0.9)
or is oriole's; the commit message links each source. Apart from the
model, the compatible, the LDO block and its regulator include, and
oriole's comments, the file matches oriole's, and it keeps oriole's two
copyright lines. The only other differences between the two boards in
postmarketOS's gs101-bluejay.dts are ST FTS touch values, for a driver
this tree does not have. The precedent for merging before a boot is
oriole's soc_id commit (#14), on the same kind of evidence.

Checks, host (dtc 1.8.1, dtschema 2026.9): gs101-bluejay.dtb builds
with -@ from the preprocessed DTS; dt-validate against the tree's
processed schema reports 0 messages, the same as gs101-oriole.dtb;
dt-doc-validate and dt-mk-schema accept google.yaml; checkpatch
--strict: 0 errors, 0 checks, one FILE_PATH_CHANGES warning for the new
file (MAINTAINERS already lists arch/arm64/boot/dts/exynos/google/, as
for the lynx and panther first-light commits); tools/pr-check: no
identifiers, no blobs; the branch is a fast-forward of omamobile. A
pre-submission review against docs/review/LESSONS.md (L-6, L-27, L-29,
L-93, L-100, L-120, L-149, L-187, L-240, L-336) read every Link: at its
tag and found each claim in the message there.

tools/kernel-pr-check --build --merge, in the build container:

ok - merges cleanly onto fa5553177 (test merge eb429b76e)
ok - 2 commits signed off by their authors, none by an AI
ok - subjects have subsystem prefixes
ok - checkpatch --strict: no errors (1 warnings and checks to read)
#   e85110d61 arm64: dts: exynos: google: Add Pixel 6a (bluejay) first-light board
#     WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
ok - policy (tools/pr-check): identifiers, blobs
ok - C builds: no C files touched # SKIP
ok - 9 device trees build with W=1 and dtbs_check, no new warnings
ok - dt_binding_check on 1 bindings

The descriptor pull request (device/bluejay: device.conf, notes, the
board overlay, the DEVICES.md row) is derekross/omarchy-mobile#265 and
names this branch; DEVICE=bluejay bin/omamobile images needs this DTB
in a kernel build, so this PR merges first.

The Pixel 6a (bluejay) is a gs101 (Tensor) board like the Pixel 6 and
Pixel 6 Pro, and the binding's description already names it. Add its
compatible to the gs101 board list.

Assisted-by: Claude Fable 5.1
Signed-off-by: PeterXMR <xmrpeter@proton.me>
@derekross

Copy link
Copy Markdown
Owner

Thank you, @PeterXMR, and welcome. This is a careful first-light board: the file is oriole's with bluejay's model and compatible, and every value I checked is in the Google sources you link. board_id and board_rev are in gs101-bluejay-mp1_0.dts. The A0/B0 base trees and their soc_id are in the bluejay Makefile and gs101-b0.dts. The S6E3FC3 panel at 1080x2400 is in gs101-bluejay-display.dtsi. Bluejay also includes the same raviole battery file, so the MAX77759 gauge's 5 mΩ sense resistor still holds. Leaving oriole's two board-specific LDOs out, so they stay as the bootloader left them, is the safe choice.

On my side: our gate passes on today's omamobile (clean merge, sign-offs, checkpatch with only the new-file warning, all 9 device trees with no new warnings), gs101-bluejay.dtb validates with no messages, the same as oriole and raven, and no other board's DTB changes. CI is waiting for my approval because this is your first PR here, and I'll start it.

The one open question is the first boot. Our contributing guide asks for a tools/phone-smoke report from the phone a kernel change affects. You don't need this merged to get it: you can build the kernel from your branch (KERNEL_DIR=<your tree> KERNEL_OUT=<a scratch dir> bin/omamobile kernel) together with the descriptor from omarchy-mobile#265 and boot slot B. Once it has booted, please add uname -r and the smoke report here, and I'll merge it.

Two optional things:

  • Oriole's comments on soc_id and on the bootargs (ABL appends console=null, so panic=10 reboots rather than hanging silently) would be worth keeping in bluejay's file too.
  • Like oriole, the bootargs don't set mem_sleep_default=s2idle, so bluejay's device package will need the s2idle drop-in that the other gs101 packages carry. I'll raise that on the descriptor side.

Thanks again for the thorough sourcing.

(Maintainer: if you'd rather merge it now on the #14 precedent, replace the "first boot" paragraph with "I'm merging this now, as we did for oriole's soc_id; please post the first boot's report on #265".)

Add a first-light board file for the Pixel 6a: oriole's board file with
bluejay's model and compatible, without oriole's two board-specific
LDOs. Everything it enables, it enables as oriole's does, through
gs101-pixel-common.dtsi: the console UART, USB, both cluster watchdogs,
UFS and its PHY, the S2MPG10/11 regulators, the MAX77759 Type-C
controller, fuel gauge and PMIC, and the battery EEPROM. The GPU stays
disabled, and there is no panel or touch node.

bluejay boots the same two gs101 base device trees as oriole and raven:
Google's bluejay tree builds every bluejay board overlay on
gs101/gs101-a0.dtb and gs101/gs101-b0.dtb, whose soc_id is 0x09845000
and 0x09845001. So this DTB carries the B0 value as oriole's does, and
the image tooling writes the A0 copy from it.

The panel is a 1080x2400 S6E3FC3 variant (samsung,s6e3fc3_6a in
Google's gs101-bluejay-display.dtsi), oriole's size, so the splash
carve-out and the simple-framebuffer keep oriole's values. The retail
board overlay is MP 1.0, board_id 0x20506 and board_rev 0x10000; the
board dtbo for ABL and the image packing live in the omarchy-mobile
repository (device/bluejay).

Oriole's ldo14m (avdd18_tcxo) and ldo31m (nfc) are left out. Upstream
marks both as board specific, and Google's bluejay tree takes both from
the shared gs101-pmic.dtsi, regulator-always-on there: L14M_AVDD_TCXO,
and L31M, which gs101-whitefin2-pmic.dtsi (included by bluejay and by
oriole) renames to L31M_DISP_VDDI. Left undescribed, they stay as the
bootloader leaves them, as on raven.

Not booted yet: no Pixel 6a has run this tree. Apart from the model,
the compatible, the LDO block and its regulator include, the file
matches oriole's, its comments on soc_id and the bootargs included; the
splash and framebuffer blocks are oriole's text, so its copyright lines
stay. The only other
differences between the two boards in postmarketOS's gs101-bluejay.dts
are ST FTS touch values, for a driver this tree does not have.

Link: https://android.googlesource.com/kernel/devices/google/bluejay/+/refs/tags/android-16.0.0_r0.9/dts/gs101-bluejay-mp1_0.dts
Link: https://android.googlesource.com/kernel/devices/google/bluejay/+/refs/tags/android-16.0.0_r0.9/dts/gs101-bluejay-display.dtsi
Link: https://android.googlesource.com/kernel/devices/google/bluejay/+/refs/tags/android-16.0.0_r0.9/dts/Makefile
Link: https://android.googlesource.com/kernel/devices/google/gs101/+/refs/tags/android-16.0.0_r0.9/dts/gs101-b0.dts
Link: https://android.googlesource.com/kernel/devices/google/gs101/+/refs/tags/android-16.0.0_r0.9/dts/gs101-pmic.dtsi
Link: https://gitlab.postmarketos.org/soc/tensor-exynos/linux/-/blob/e8f42849a581/arch/arm64/boot/dts/exynos/google/gs101-bluejay.dts
Assisted-by: Claude Fable 5.1
Signed-off-by: PeterXMR <xmrpeter@proton.me>
@PeterXMR
PeterXMR force-pushed the omamobile-gs101-bluejay-dts branch from e85110d to 93a6438 Compare November 1, 2026 23:04
@PeterXMR

PeterXMR commented Nov 1, 2026

Copy link
Copy Markdown
Contributor Author

Thank you for the review @derekross .

I've added oriole's soc_id and bootargs comments to gs101-bluejay.dts as suggested; the DTB is byte-identical before and after, and checkpatch reports nothing on the change.
tools/kernel-pr-check with --build --merge against today's omamobile passes all checks (clean merge, sign-offs, checkpatch with only the new-file warning, 9 device trees with W=1 and dtbs_check with no new
warnings, dt_binding_check).

On the first boot: I have a Pixel 6a, but I can't run the boot test myself.
If merging now on the #14 precedent works for you, I'd take it, and I'll ask on
omarchy-mobile issue #2 whether someone with a spare 6a can boot slot B from this DTS and post uname -r and the phone-smoke report there.

The s2idle drop-in is noted for the bluejay device package.

@derekross

Copy link
Copy Markdown
Owner

Thank you, @PeterXMR. The new head adds oriole's two comments word for word, and nothing else changes in the file, so the DTB is the same as before, as you say. Our gate on today's omamobile passes again: a clean merge, both commits signed off, checkpatch with only the new-file warning, and all 9 device trees with no new warnings. CI is waiting for my approval again after the push, and I'll start it.

On the first boot: thanks for saying so plainly. I'm merging this once CI is green, as we did for oriole's soc_id. It's a new board file, and it doesn't change any other board's DTB. Asking on omarchy-mobile#2 for someone with a spare 6a is a good idea. Whoever boots it, please post uname -r and the tools/phone-smoke report there, and add a dated entry to device/bluejay/NOTES.md. Until that boot, bluejay's row in DEVICES.md stays at "no phone yet". If it's useful to say on #2 why you can't run it yourself (bootloader locked, or the phone in daily use), that tells people what kind of help you need.

@derekross
derekross merged commit cc144e3 into derekross:omamobile Nov 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants