On Wed, Oct 21, 2026 at 05:11:51PM +0800, Kuan-Wei Chiu wrote: > 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 <[email protected]> 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?
You can wait to post v2 until we can get the dts patches via devicetree-rebasingi and a v7.x-dts tag, or you can cherry-pick them and include that in the series, once they exist in some -rc https://docs.u-boot-project.org/en/latest/develop/devicetree/control.html#resyncing-with-devicetree-rebasing I expect Simon missed the cover letter where you explained your expectations. -- Tom
signature.asc
Description: PGP signature
