U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: Simon Glass <sjg@chromium.org>
Cc: trini@konsulko.com, ilias.apalodimas@linaro.org,
	marscheng@google.com, eleanor15x@gmail.com,
	jserv@ccns.ncku.edu.tw, u-boot@lists.u-boot-project.org
Subject: Re: [PATCH 0/4] arm: google: Add initial support for Google Tensor G5
Date: Wed, 21 Oct 2026 17:11:51 +0800	[thread overview]
Message-ID: <atiB14EfQYSo2g5o@google.com> (raw)
In-Reply-To: <CAFLszTgb+w2mbsw-h0fHmqoVztS5ZNx2ZCM+R-V3gaJONBAOKQ@mail.gmail.com>

Hi Simon,

On Mon, Oct 19, 2026 at 06:27:31AM -0700, Simon Glass wrote:
> Hi Kuan-Wei,
> 
> On 2026-10-16T04:02:12, Kuan-Wei Chiu <visitorckw@gmail.com> wrote:
> 
> > This series adds initial architecture and board support for the Google
> > Tensor G5 SoC, referred to in code as LGA, and the Pixel 10 series
> > boards based on it.
> 
> Thanks for sending this.
> 
> Please can you add a doc/board/google/lga.rst (linked from
> doc/board/google/index.rst) covering how to build this, the BL33 load
> address, the DT prerequisite below, and what currently works.

Ah, I always forget to add doc in my first version.
I'll add the doc in v2.

> 
> > The device trees for LGA are queued in the Samsung and Google SoC tree
> > for Linux v7.4 [1] and have not yet been synced into dts/upstream, so
> > cherry-picking those commits locally is required to build this series
> > until the next dts/upstream subtree update.
> 
> One thing I'd like to check before this series goes in.. as it stands
> google_lga_defconfig cannot be built from a clean tree, which breaks
> bisection and CI. It would be worth holding the defconfig patch (and
> perhaps the -u-boot.dtsi) until the dts/upstream subtree has picked up
> lga, so the series lands atomically. What do you think?
> 
I'm not sure what the usual process is in U-Boot for this situation. I
originally expected the maintainers to wait until the device tree is
synced into dts/upstream before applying the series. Do you mean that
in v2 I should only send the first two patches, and resend the last two
patches after the device tree sync?

Regards,
Kuan-Wei

  reply	other threads:[~2026-10-21  9:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  4:02 [PATCH 0/4] arm: google: Add initial support for Google Tensor G5 Kuan-Wei Chiu
2026-10-16  4:02 ` [PATCH 1/4] arm: Add Google Tensor SoC architecture support Kuan-Wei Chiu
2026-10-19 13:27   ` Simon Glass
2026-10-21  9:15     ` Kuan-Wei Chiu
2026-10-21 14:43       ` Tom Rini
2026-10-16  4:02 ` [PATCH 2/4] board: google: Add Google Tensor G5 board support Kuan-Wei Chiu
2026-10-16 19:21   ` Tom Rini
2026-10-17  6:56     ` Kuan-Wei Chiu
2026-10-19 13:27   ` Simon Glass
2026-10-16  4:02 ` [PATCH 3/4] arm: dts: lga: Enable console UART in U-Boot Kuan-Wei Chiu
2026-10-19 13:27   ` Simon Glass
2026-10-16  4:02 ` [PATCH 4/4] configs: google: Add lga default configuration Kuan-Wei Chiu
2026-10-19 13:27   ` Simon Glass
2026-10-19 13:27 ` [PATCH 0/4] arm: google: Add initial support for Google Tensor G5 Simon Glass
2026-10-21  9:11   ` Kuan-Wei Chiu [this message]
2026-10-21 14:39     ` Tom Rini

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=atiB14EfQYSo2g5o@google.com \
    --to=visitorckw@gmail.com \
    --cc=eleanor15x@gmail.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=marscheng@google.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    /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