From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=74.125.82.48 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794604167; b=bkQ35089nWWCEQhx0CftYU8P8rYdeLrGx2rQdGjVJkMBM0D6R24XldZ1rQHX2S3gH1FV kkZjSns129uLxUMtHFpbwFibhU+NEwPcWTRNdUBbu1V39PfjtJjYfP5pC9Spr8h8sCaBX WrhLUw07OImmLyGiMe5zg9iFXZ4dlyqjF3Vjih5/Z35CQYs+eeujdq0cJYEiV4Edu8Q7q 4oS5y8ibs1tD3BFv8EsSUsnHnwGVMT6LjF033MkBFTEKLSRdePIUwM3rbfJQSecZb/ZcH F1ZlxdvaD0XCkPPpC2JVySuPYSuXuG77PHcakDGivxpMS9BDh1hNrEpgUUcWt1Pc1Kw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794604167; h=DMARC-Filter:Received:DKIM-Signature:X-Google-DKIM-Signature: X-Forwarded-Encrypted:X-Gm-Message-State:X-Gm-Gg:X-Received:Received: From:To:Cc:Subject:Date:Message-ID:X-Mailer:MIME-Version:Content-Type: Content-Transfer-Encoding; bh=/XWpc39jBynwI4nBXv0NNeAvE7u5mNOBsmUvCwWc94s=; b=JIb/Gn+KcV7Qg8mwpaDiimmZM0AE0RJ4RTXgVRMeg+vVbVdtsFHN0482pTZ1nnlqXG7m C3266v/NBsD6I5Nd8pmr4FeOFPi/hPw5SHKUI0gz4G/b8A/lg6I/AWU+10GbiSqoCQHGv 4Vuwgmuqc0OnOvnYPHMWa7HXft5TCBSLaUX7bDN4qyCuxtIIZqPKTaQ8qZPoIZeRDZQRQ MW4wsQ3zh98gFUjmS/TTktuY0o/tIF1gRaD0L/097aVbThRdibj8v6OOiux3azmpeViPM Q+B3+UzW2CqxgUj8yAkyfBj+qkd2eBLQlFltyweLKvtpA0NEXcC6EDd7oKZjyYH+RwQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=chromium.org; spf=pass smtp.mailfrom=chromium.org; dkim=pass header.d=chromium.org header.i=@chromium.org header.a=rsa-sha256 header.s=google header.b=aLz0Y4MS; arc=none smtp.remote-ip=74.125.82.48 Received: from mail-dl1-f48.google.com (mail-dl1-f48.google.com [74.125.82.48]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DDD2D606A882 for ; Fri, 13 Nov 2026 21:09:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org DDD2D606A882 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=chromium.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=chromium.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=chromium.org header.i=@chromium.org header.a=rsa-sha256 header.s=google header.b=aLz0Y4MS Received: by mail-dl1-f48.google.com with SMTP id a92af1059eb24-15dd124bbe7so503309c88.1 for ; Fri, 13 Nov 2026 13:09:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; t=1794604166; x=1795208966; darn=vger.kernel.org; h=content-transfer-encoding:content-type:mime-version:message-id:date :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to :content-type; bh=/XWpc39jBynwI4nBXv0NNeAvE7u5mNOBsmUvCwWc94s=; b=aLz0Y4MS5HVFlOxmPqqFMPg0eifh1MyYKl/shV1TSg6AxCreEouIS+gfPiKcMe7L9e OJULCa6qggA7ACGjZYTTTAD8i4wnoNX4gtt2F8uaWmZybukSpX1dnjUmD89JcyNbtIoz 4T+1uksvKL1Z2sg/crUlpSJThsjBU/GFWUcGI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1794604166; x=1795208966; h=content-transfer-encoding:content-type:mime-version:message-id:date :subject:cc:to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to:content-type; bh=/XWpc39jBynwI4nBXv0NNeAvE7u5mNOBsmUvCwWc94s=; b=PwveKWcppUF1IaerHcFZxUrzdCkVbkH4HYhr8N8x0AQsZB9k4jSCN/ilt5HBX+kOs9 s1FwKWFUuVpPL+JG64t1/AacDYasqUJhomxsaTGt7Vh6wSCAAgPYAkj6HT1uwnLmkxAn KIjduEH57uusRMO8mw0EI6SJb/AtEcN+JTqNMvBJm2ixoxJtsp9YtHgjpS33CPsfnYtw 0lXDXYlqqZSfKCxGaLoPAjJHheaI6Ur0iwvfpTAQI5WDabZkCMJtE8OmQRUOoHJFM6mX 2TvFTNHh3j8twwZb1J6Wx/gtjf5mgoLjM/MEUzZ9s0JR5Lv4M6YIC4jlw08li8UUNnkE 8UIA== X-Forwarded-Encrypted: i=1; AL+hErFaqVAIzJI3imvDti19iMk9cCir7zv2XQmUycYz/AIt8cnVNyVGhy01SJ3r4Ffc0oMi0daTzl4pcMU=@vger.kernel.org X-Gm-Message-State: APuU4Z+XU2dQUhfq3+/EG1AJsPbOJar1rm7qylETCerw6NzHDpPcLQSA dNs2qnrtjf9TCaoQRgCTJUgWQkNgJe6UoxHL0LDxo6GxWVk8dLCMfKcN/JwIrWb9sQ== X-Gm-Gg: AYBFou0xQLncrDDXXxHgMheZeB4fNQlLgE4xTCUP7e8hvhOb941rKRqdFSWk/p2tq/n hotiBxpeuUslLnDqTKvWIFUWe+6O96ZQ5HQ+g5MzpP1TlHE/G0L3RfYNhuFldJR56Rs97W2P9J+ 2u1KXKUgIEcbXtwsmPJ3lHOqr9s8uc49dAfVGE34oJ3ORg1eD4FRpdT98xgOcdU67QIz+w9Pyvm euVTdXxVuv7U3sLsZ7OJhfPeMkow2hqmNA3g1sVZXOSRExa1dpmPAMKJ7nChggzkTd/17QceK7L xscfDceRrG8knzopgc4OM2kI8LoNSRfEZWA6z1YVh2pDmLrc3irkb0C3n66syhuy+2vUYWEITml 1j8dLVp6X5FJE3L3o31JD9uA8JrAde/5NmWpZVzaYuU9sbP8V9MC1kr8W4HLbWNyPH5Nhw1SFQj cCwc7Cyn7dhB5Ae+whilqFMCMkiXURof0me8ywbkQknCJnRJ+AdKvMP4PADMpJMAhEoxOlslW9+ HB/UMIBKdk2AhRWXQvHOJdKFyEeq2QTR2BfSBf8qkhI7c2mTEsMqJo+Db1gYo53qTkIqz76ck3p e98/+Fywsqxs9H6dG4RlNXraBxbQox9DCa6LiQYv0Wxpg63lO9hgWU+MktbotA5/MYpwsSDTWMx Km9QCy81XBUSI+Q== X-Received: by 2002:a05:701b:4182:10b0:1b2:5128:df1b with SMTP id a92af1059eb24-1b5031b7dd3mr3390648c88.45.1794604165722; Fri, 13 Nov 2026 13:09:25 -0800 (PST) Received: from dianders.sjc.corp.google.com ([2a00:79e0:2e7c:8:38c:b779:3be9:e682]) by smtp.gmail.com with ESMTPSA id a92af1059eb24-1b50300e5dcsm8463040c88.0.2026.11.13.13.09.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Nov 2026 13:09:23 -0800 (PST) From: Douglas Anderson To: Devicetree-compiler@vger.kernel.org, Rob Herring , Krzysztof Kozlowski , Conor Dooley , Konrad Dybcio Cc: linux-arm-msm@vger.kernel.org, Julius Werner , Michal Simek , =?UTF-8?q?Andr=C3=A9=20Draszik?= , linux-arm-kernel@lists.infradead.org, Simon Glass , Peter Griffin , linux-kbuild@vger.kernel.org, Tudor Ambarus , Chen-Yu Tsai , Will Deacon , Nathan Chancellor , Devicetree@vger.kernel.org, Catalin Marinas , Nicolas Schier , linux-kernel@vger.kernel.org, Saravana Kannan , Brian Norris , Douglas Anderson , Abel Vesa , Alice Ryhl , Bjorn Andersson , David Sterba , Jonathan Corbet , Josh Poimboeuf , "Lorenzo Stoakes (ARM)" , Manuel Ebner , Marco Elver , Mark Rutland , Mauro Carvalho Chehab , Nick Terrell , "Peter Zijlstra (Intel)" , Randy Dunlap , Rong Xu , Shuah Khan , cros-qcom-dts-watchers@chromium.org, devicetree@vger.kernel.org, linux-doc@vger.kernel.org, linux-samsung-soc@vger.kernel.org, workflows@vger.kernel.org Subject: [RFC PATCH v2 0/5] arm64: Add FIT configurations for sc7180-trogdor and google,lga Date: Fri, 13 Nov 2026 13:09:09 -0800 Message-ID: <20261113210918.356261-1-dianders@chromium.org> X-Mailer: git-send-email 2.56.0.611.g1030f0b940-goog X-Mailing-List: workflows@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The end goal of this series is to move forward on producing a "universal" Pixel 10 boot image that can boot on a variety of Pixel 10 devices (frankel, blazer, and mustang and eventually multiple revisions of each). At the moment, this is impossible since the Pixel 10 bootloader: * Picks the base devicetree based on SoC ID information. * Picks an overlay devicetree based on Board ID information. * Needs metadata associated with each overlay to match it up. Since we don't have per-board overlays and don't have per-board metadata, that means that today you need to pick exactly one revision of one board and build a boot image just for that. How does this series help us? 1. It uses a checked-in `.fitconfig` configuration file alongside the `.dts` files to select which DTBs belong in the FIT image and to associate metadata with each board's configuration in `scripts/make_fit.py` [1]. Other tools can parse this metadata in order to craft a package that the Pixel bootloader can understand. 2. It integrates a call to the new `fdtfactor` tool [2], which results in a "base dtb + board dtbo" that looks like what the bootloader needs, at least as long as all the boards have the same SoC. What happens if everyone hates this series and it gets dropped on the floor? Honestly, everything here could just go out of tree and it would be "fine". IMO it's nice to have the Board ID / SoC ID information for each devicetree stored in the same repository as the devicetrees themselves are, but if this has to live somewhere else then so be it. NOTE: from reading the above, you might wonder why the sc7180-trogdor `.fitconfig` configuration file is part of this series. The answer: it's a board I was previously deeply involved in and it is a convenient way for me to prove out that the Chromebook use case works well. I did hack up some changes to the ChromeOS build system to use the provided FIT image and it worked great, but since I'm not on the ChromeOS team these days it's not something I personally plan to follow-up with. It sounds plausible that Chen-Yu may follow-up with it or post a similar change for some Mediatek Chromebooks. [1] https://github.com/open-source-firmware/flat-image-tree/pull/66 [2] https://lore.kernel.org/r/20261101220224.1436242-1-dianders@chromium.org v1: https://lore.kernel.org/r/20261020153652.2907186-1-dianders@chromium.org Changes in v2: - New preparatory patch documenting preexisting FIT_COMPRESSION and FIT_DECOMPOSE_DTBS variables (Simon Glass) - Replace FIT_ITS + mkimage + fdtget/fdtput approach with FIT_CONFIG .fitconfig sidecar files handled directly by scripts/make_fit.py (Simon Glass) - Support subnode properties (e.g. match-1/...) and u32 integer values for the proposed FIT configuration match subnode spec (Simon Glass) - Document FIT_CONFIG in Documentation/kbuild/kbuild.rst and under image.fit in arm64 'make help' (Simon Glass) - Update fdtfactor invocation for v2+ flags (-v -> -s, -f -> -F) - Expand commit message and notes to explain why FIT_FACTOR_DTBS is needed, that fdtfactor is an external host dependency, and that compressed DTBs in the FIT are supported (Simon Glass) - Document the optional fdtfactor dependency and FIT_FACTOR_DTBS / FDTFACTOR / FDTFACTOR_ARGS in Documentation/process/changes.rst, Documentation/kbuild/kbuild.rst, and arm64 'make help' (Simon Glass) - Drop fdtget/fdtput sync and hostprog patches (patches 1-3 in v1) now that scripts/make_fit.py handles FIT configuration files directly (Simon Glass) - Replace checked-in lga.its with a compact lga.fitconfig sidecar file consumed by scripts/make_fit.py (Simon Glass) - Move board/SoC matching metadata from the configuration description string to a typed match-1 subnode per the proposed FIT spec extension (Simon Glass) - Replace 728-line sc7180-trogdor.its with a 49-line sc7180-trogdor.fitconfig sidecar file consumed by scripts/make_fit.py (Simon Glass) - Move motivation for sc7180-trogdor from commit notes into the commit message body (Simon Glass) Douglas Anderson (5): kbuild: fit: Document FIT_COMPRESSION and FIT_DECOMPOSE_DTBS kbuild: fit: Support selecting DTBs and config properties from a file kbuild: fit: Add opt-in FIT_FACTOR_DTBS support using fdtfactor arm64: dts: google: lga: Add lga.fitconfig FIT configuration file arm64: dts: qcom: sc7180: Add sc7180-trogdor.fitconfig FIT config file Documentation/kbuild/kbuild.rst | 33 +++++ Documentation/process/changes.rst | 10 ++ arch/arm64/Makefile | 2 + arch/arm64/boot/dts/google/lga.fitconfig | 22 ++++ .../boot/dts/qcom/sc7180-trogdor.fitconfig | 49 ++++++++ scripts/Makefile.dtbs | 17 +++ scripts/Makefile.lib | 32 ++++- scripts/make_fit.py | 117 +++++++++++++++--- 8 files changed, 267 insertions(+), 15 deletions(-) create mode 100644 arch/arm64/boot/dts/google/lga.fitconfig create mode 100644 arch/arm64/boot/dts/qcom/sc7180-trogdor.fitconfig -- 2.56.0.611.g1030f0b940-goog