Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Peter Griffin" <peter.griffin@linaro.org>
Cc: linux-serial@vger.kernel.org, robh@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/4] arm64: dts: google: Add initial dts for frankel/blazer/mustang
Date: Fri, 18 Sep 2026 17:34:26 +0000	[thread overview]
Message-ID: <20260918173426.D6AEC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918-contrib-pg-pixel10-initial-dts-v3-3-c94e51140509@linaro.org>

> From: Douglas Anderson <dianders@chromium.org>
> 
> Add initial device trees for frankel (Pixel 10), blazer (Pixel 10
> Pro) and mustang (Pixel 10 Pro XL). These device trees are enough to
> boot to a serial prompt using an initramfs.
> 
> Currently only Laguna B0 silicon found in mass production phones is
> officially supported. Further revisions such as A0 silicon and EVT
> devices maybe added in the future if they are useful. As of today,
> these device trees boot fine on EVT devices with A0 silicon.
> 
> A few things can be noted about these device trees:
> 
> 1. They purposely choose to use the full 64-bit address and size cells
>    for the root node and the `soc@0` node. Although I haven't tested
> [ ... ]
>  - Add osc 38.4Mhz fixed-clock
> 
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Co-developed-by: Peter Griffin <peter.griffin@linaro.org>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-contrib-pg-pixel10-initial-dts-v3-0-c94e51140509@linaro.org?part=3


  reply	other threads:[~2026-09-18 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 17:26 [PATCH v3 0/4] Add Laguna/Tensor G5 SoC and Frankel, Blazer & Mustang boards Peter Griffin
2026-09-18 17:26 ` [PATCH v3 1/4] dt-bindings: arm: google: Add dt bindings for frankel/blazer/mustang Peter Griffin
2026-09-18 17:30   ` sashiko-bot
2026-09-18 17:26 ` [PATCH v3 2/4] arm64: dts: google: Add dts directory for Google-designed silicon Peter Griffin
2026-09-18 17:29   ` sashiko-bot
2026-09-18 17:26 ` [PATCH v3 3/4] arm64: dts: google: Add initial dts for frankel/blazer/mustang Peter Griffin
2026-09-18 17:34   ` sashiko-bot [this message]
2026-09-30 21:50   ` Linus Walleij
2026-09-18 17:26 ` [PATCH v3 4/4] arm64: defconfig: enable Tensor G5 SoC family Peter Griffin
2026-09-18 17:28   ` sashiko-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260918173426.D6AEC1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox