mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Douglas Anderson <dianders@chromium.org>,
	Devicetree-compiler@vger.kernel.org,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
	"Brian Norris" <briannorris@chromium.org>,
	"Catalin Marinas" <catalin.marinas@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"Simon Glass" <sjg@chromium.org>,
	"Chen-Yu Tsai" <wenst@chromium.org>,
	linux-arm-msm@vger.kernel.org, "Nicolas Schier" <nsc@kernel.org>,
	"Peter Griffin" <peter.griffin@linaro.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	Devicetree@vger.kernel.org,
	"Julius Werner" <jwerner@chromium.org>,
	"Saravana Kannan" <saravanak@kernel.org>,
	"Will Deacon" <will@kernel.org>,
	"André Draszik" <andre.draszik@linaro.org>,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [RFC PATCH 6/7] arm64: dts: google: lga: Add lga.its FIT image script
Date: Wed, 21 Oct 2026 08:47:46 +0200	[thread overview]
Message-ID: <3142486c-9604-41bb-b7bd-d0708643d41f@amd.com> (raw)
In-Reply-To: <20261020083501.RFC.6.Idfb669fd6c518bc86e45d8555f159c0ec611a6f9@changeid>



On 10/20/26 17:35, Douglas Anderson wrote:
> Add an Image Tree Source (`lga.its`) describing the FIT image for Google
> Tensor G5 (LGA) Pixel 10 family boards (`lga-blazer.dtb`,
> `lga-frankel.dtb`, and `lga-mustang.dtb`) with board and SoC ID/revision
> metadata in the configuration descriptions, allowing the LGA FIT image
> to be built with:
> 
>    make \
>      FIT_ITS=google/lga.its \
>      FIT_FACTOR_DTBS=1 \
>      FDTFACTOR_ARGS="--strip-local-fixups --single-base-dtb" \
>      image.fit
> 
> NOTE: At the moment, Pixel 10 doesn't directly boot from a FIT
> image. However, packaging scripts will be able to take an image as
> built above and convert it into a format that the bootloader can
> handle.
> 
> It should also be noted that the "description" of the various
> configurations here is expected to be parsed to help figure out which
> configuration to use on which board. This idea came out of discussions
> at Linux Plumbers Conference 2026 and means we don't need "loader"
> info polluting device trees. Having a structured (and upstream) place
> to store this data is part of the motivation for landing this FIT
> image.
> 
> Side note: at the moment, the Pixel bootloader can't handle picking
> overlays based on the soc_id and soc_rev (it only uses those to pick
> base dtb files), so for now we won't be able to support boards that
> might have different SoCs. I've included the soc_id and soc_rev in
> this FIT image in the hopes that we can improve the bootloader in the
> future, though.
> 
> Assisted-by: Gemini:gemini-pro-prerelease
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> ---
> Note that building `image.fit` with `lga.its` requires the Pixel 10
> (`lga-blazer.dtb`, `lga-frankel.dtb`, and `lga-mustang.dtb`) device
> trees, which are currently in linux-next and not yet in mainline.
> 
>   arch/arm64/boot/dts/google/lga.its | 68 ++++++++++++++++++++++++++++++
>   1 file changed, 68 insertions(+)
>   create mode 100644 arch/arm64/boot/dts/google/lga.its
Looks good to me.

Acked-by: Michal Simek <michal.simek@amd.com>

Cheers,
Michal


  reply	other threads:[~2026-10-21  6:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 15:35 [RFC PATCH 0/7] arm64: Add fit images for sc7180-trogdor and google,lga Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 1/7] scripts/dtc: Add fdtget.c and fdtput.c to sync script Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 2/7] scripts/dtc: Update to upstream version v1.8.1-22-gf3451d12532b Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 3/7] scripts/dtc: Build fdtget and fdtput host tools Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 4/7] arm64: boot: Support building image.fit from a specified FIT_ITS script Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 5/7] kbuild: fit: Add opt-in FIT_FACTOR_DTBS support using fdtfactor Douglas Anderson
2026-10-20 15:35 ` [RFC PATCH 6/7] arm64: dts: google: lga: Add lga.its FIT image script Douglas Anderson
2026-10-21  6:47   ` Michal Simek [this message]
2026-10-20 15:35 ` [RFC PATCH 7/7] arm64: dts: qcom: sc7180: Add sc7180-trogdor.its " Douglas Anderson
2026-10-21  6:49   ` Michal Simek
2026-10-21  7:52   ` Konrad Dybcio

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=3142486c-9604-41bb-b7bd-d0708643d41f@amd.com \
    --to=michal.simek@amd.com \
    --cc=Devicetree-compiler@vger.kernel.org \
    --cc=Devicetree@vger.kernel.org \
    --cc=andre.draszik@linaro.org \
    --cc=briannorris@chromium.org \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=dianders@chromium.org \
    --cc=jwerner@chromium.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=saravanak@kernel.org \
    --cc=sjg@chromium.org \
    --cc=tudor.ambarus@linaro.org \
    --cc=wenst@chromium.org \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®