This series adds barebones device trees for Pixel 10 (frankel), Pixel
10 Pro (blazer), and Pixel 10 Pro XL (mustang). With a yet-unreleased
bootloader these can boot to a UART command prompt from an initramfs.

The end result of the device trees introduced in this series is really
pretty simple, so it's expected that most of the discussion in the
series will be about compatible strings, file organization, dts/dtso
organization, etc.


Douglas Anderson (4):
  dt-bindings: arm: google: Add bindings for frankel/blazer/mustang
  dt-bindings: serial: snps-dw-apb-uart: Add "google,lga-uart"
  arm64: dts: google: Add dts directory for Google-designed silicon
  arm64: dts: google: Add initial dts for frankel, blazer, and mustang

 .../devicetree/bindings/arm/google.yaml       |  87 +++-
 .../bindings/serial/snps-dw-apb-uart.yaml     |   1 +
 MAINTAINERS                                   |   1 +
 arch/arm64/Kconfig.platforms                  |   6 +
 arch/arm64/boot/dts/Makefile                  |   1 +
 arch/arm64/boot/dts/google/Makefile           |  10 +
 arch/arm64/boot/dts/google/lga-b0.dts         | 391 ++++++++++++++++++
 .../arm64/boot/dts/google/lga-blazer-mp1.dtso |  22 +
 .../boot/dts/google/lga-frankel-mp1.dtso      |  22 +
 .../boot/dts/google/lga-mustang-mp1.dtso      |  22 +
 .../boot/dts/google/lga-muzel-common.dtsi     |  17 +
 11 files changed, 561 insertions(+), 19 deletions(-)
 create mode 100644 arch/arm64/boot/dts/google/Makefile
 create mode 100644 arch/arm64/boot/dts/google/lga-b0.dts
 create mode 100644 arch/arm64/boot/dts/google/lga-blazer-mp1.dtso
 create mode 100644 arch/arm64/boot/dts/google/lga-frankel-mp1.dtso
 create mode 100644 arch/arm64/boot/dts/google/lga-mustang-mp1.dtso
 create mode 100644 arch/arm64/boot/dts/google/lga-muzel-common.dtsi

-- 
2.51.2.1041.gc1ab5b90ca-goog

Hi!

> This series adds barebones device trees for Pixel 10 (frankel), Pixel
> 10 Pro (blazer), and Pixel 10 Pro XL (mustang). With a yet-unreleased
> bootloader these can boot to a UART command prompt from an initramfs.

Well, booting to full system with working cameras would be nicer, but
this is good start. Do you plan / do you have resources for full
support in some reasonable timeframe? 

Please cc phone-devel@vger with phone related patches.

And... thanks! :-).

Best regards,
								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!

Hi,

On Sun, Nov 23, 2025 at 2:27 PM Pavel Machek <pavel@ucw.cz> wrote:
>
> Hi!
>
> > This series adds barebones device trees for Pixel 10 (frankel), Pixel
> > 10 Pro (blazer), and Pixel 10 Pro XL (mustang). With a yet-unreleased
> > bootloader these can boot to a UART command prompt from an initramfs.
>
> Well, booting to full system with working cameras would be nicer,

For sure!


> but
> this is good start. Do you plan / do you have resources for full
> support in some reasonable timeframe?

As you can probably guess, I can't really make any promises. :-) Of
course, "full support" of Pixel 10 by an upstream kernel in a
"reasonable" timeframe could arguably be impossible no matter how many
resources were thrown at it. There are just some drivers / subsystems
where getting upstream working as well as downstream is working
doesn't feel likely as a short term goal.

That all being said, interest / support from the community helps.
Knowing that people are interested in this work helps motivate folks
at Google and (hopefully) upstream maintainers.


> Please cc phone-devel@vger with phone related patches.

I will try to remember.


> And... thanks! :-).

Of course! Hopefully many people find the work interesting / helpful.

-Doug

Hi!

> > > This series adds barebones device trees for Pixel 10 (frankel), Pixel
> > > 10 Pro (blazer), and Pixel 10 Pro XL (mustang). With a yet-unreleased
> > > bootloader these can boot to a UART command prompt from an initramfs.
> >
> > Well, booting to full system with working cameras would be nicer,
> 
> For sure!
> 
> 
> > but
> > this is good start. Do you plan / do you have resources for full
> > support in some reasonable timeframe?
> 
> As you can probably guess, I can't really make any promises. :-) Of
> course, "full support" of Pixel 10 by an upstream kernel in a
> "reasonable" timeframe could arguably be impossible no matter how many
> resources were thrown at it. There are just some drivers / subsystems
> where getting upstream working as well as downstream is working
> doesn't feel likely as a short term goal.
> 
> That all being said, interest / support from the community helps.
> Knowing that people are interested in this work helps motivate folks
> at Google and (hopefully) upstream maintainers.

Motivation is certainly there, and race for usable, supported phone is
still continuing. Check https://wiki.postmarketos.org/wiki/Devices for
small glimpse into "mainline on phones" effort.

Best regards,

								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!