Received: by 2002:a05:7412:419a:b0:f3:1519:9f41 with SMTP id i26csp4832784rdh; Wed, 29 Nov 2023 11:58:25 -0800 (PST) X-Google-Smtp-Source: AGHT+IH9meEOpL5fOeGNBfv6mOIKrKAXc92gXEMk333PQD0lud73qCtoErcKfFaqHS2YSmtJXboD X-Received: by 2002:a05:6a00:1a91:b0:6c4:9672:9a17 with SMTP id e17-20020a056a001a9100b006c496729a17mr23897579pfv.1.1701287904705; Wed, 29 Nov 2023 11:58:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701287904; cv=none; d=google.com; s=arc-20160816; b=duI7klsCz5QPevRhv/vt70ZW6I66KGazqAfP4L/An+t6LuLCr49QfQgs7inEQZXbSs 33u+OMxBXaicEicdpGi3HDPdGam22tQTw21RuV/9NXn5NRfv7NPACZF80Ux1Im8z8UI3 7BRmOwTJKm/Jxw/bTjVc3eQjcb7h+rbAQbX82N06OeXEMTR1QR/1lD3AS8wr0/UyQfRc DxpqZhbr69egepEmPUCOBvGEyZZ30IydYedMumynazaOk6rxRyMMORHGXDZXHrnyUd6Y +Z8uMEn3o8MCkcpMhW6E8NAsQQYBJ1z7Cu60Gc83CnPAb1yfIZP4ZMuo9CTdZM2yq0sx dndw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=O2gTASzFuTz2ty/6BtuAwIXGGrsfFdryZcP7tEqiEOg=; fh=58mvxDYp+91DFuCFSacis+b2Z1raZvSUVIFbm2i9FyM=; b=eJOHl/UpoXqcunQjqlw517SN06L0fXHk6CeJIeiIY1XXCbVX000AsPdSsXO7x+0MnG dy8elXEuSmCPvEsKwbmeRRDArZwzexJK3CEgYKeU/0ZbJKNYzIrKzcevXFPUaE1CqRmY X1YbS+kyMMzyp/EfETj8Q1K07w1Gy8FYRUXltKgYfcWUH/UwAJKTIZIjgO7fiCr5kjoq lK3HGW6S4ONgoPS12gtrUOo2ek9v2ziFr0x2Z7TbYIe9Fgf9WISac7jARrPWtE6AuSV7 mHMF7FyyOpiDhyQ2+uVdIrDdv1uhcMzvVZe15W6wPb1e5NT4sY5alHyBZAEnsjxY/7oB vVEQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from fry.vger.email (fry.vger.email. [2620:137:e000::3:8]) by mx.google.com with ESMTPS id p24-20020a634f58000000b005be37e27238si15121436pgl.893.2023.11.29.11.58.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Nov 2023 11:58:24 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id 2C4BE804B5C8; Wed, 29 Nov 2023 11:58:20 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230355AbjK2Tx7 (ORCPT + 99 others); Wed, 29 Nov 2023 14:53:59 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52026 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229741AbjK2Tx6 (ORCPT ); Wed, 29 Nov 2023 14:53:58 -0500 Received: from metis.whiteo.stw.pengutronix.de (metis.whiteo.stw.pengutronix.de [IPv6:2a0a:edc0:2:b01:1d::104]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8250B194 for ; Wed, 29 Nov 2023 11:54:04 -0800 (PST) Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[127.0.0.1]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1r8QdA-0000kK-Iq; Wed, 29 Nov 2023 20:53:56 +0100 Message-ID: <8fbc81b1-31ab-46b0-87f4-b8bd8e8e2b47@pengutronix.de> Date: Wed, 29 Nov 2023 20:53:52 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v7 2/2] arm64: boot: Support Flat Image Tree Content-Language: en-US To: Simon Glass Cc: linux-arm-kernel@lists.infradead.org, Masahiro Yamada , Tom Rini , lkml , U-Boot Mailing List , Catalin Marinas , Nathan Chancellor , Nick Terrell , Nicolas Schier , Will Deacon , linux-kbuild@vger.kernel.org, Pengutronix Kernel Team References: <20231129172200.430674-1-sjg@chromium.org> <20231129172200.430674-3-sjg@chromium.org> <30f32467-51ea-47de-a272-38e074f4060b@pengutronix.de> <875f0dbc-1d78-4901-91b2-6ad152bcea5a@pengutronix.de> <06281f7c-e0f2-405c-95a9-0f7e9e84a7f6@pengutronix.de> From: Ahmad Fatoum In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2a0a:edc0:0:900:1d::77 X-SA-Exim-Mail-From: a.fatoum@pengutronix.de X-SA-Exim-Scanned: No (on metis.whiteo.stw.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Wed, 29 Nov 2023 11:58:20 -0800 (PST) Hello Simon, On 29.11.23 20:44, Simon Glass wrote: > Hi Ahmad, > > On Wed, 29 Nov 2023 at 12:33, Ahmad Fatoum wrote: >> >> On 29.11.23 20:27, Simon Glass wrote: >>> On Wed, 29 Nov 2023 at 12:15, Ahmad Fatoum wrote: >>>> On 29.11.23 20:02, Simon Glass wrote: >>>>> On Wed, 29 Nov 2023 at 11:59, Ahmad Fatoum wrote: >>>>>> The specification says that this is the root U-Boot compatible, >>>>>> which I presume to mean the top-level compatible, which makes sense to me. >>>>>> >>>>>> The code here though adds all compatible strings from the device tree though, >>>>>> is this intended? >>>>> >>>>> Yes, since it saves needing to read in each DT just to get the >>>>> compatible stringlist. >>>> >>>> The spec reads as if only one string (root) is supposed to be in the list. >>>> The script adds all compatibles though. This is not really useful as a bootloader >>>> that's compatible with e.g. fsl,imx8mm would just take the first device tree >>>> with that SoC, which is most likely to be wrong. It would be better to just >>>> specify the top-level compatible, so the bootloader fails instead of taking >>>> the first DT it finds. >>> >>> We do need to have a list, since we have to support different board revs, etc. >> >> Can you give me an example? The way I see it, a bootloader with >> compatible "vendor,board" and a FIT with configuration with compatibles: >> >> "vendor,board-rev-a", "vendor,board" >> "vendor,board-rev-b", "vendor,board" >> >> would just result in the bootloader booting the first configuration, even if >> the device is actually rev-b. > > You need to find the best match, not just any match. This is > documented in the function comment for fit_conf_find_compat(). In my above example, both configuration are equally good. Can you give me an example where it makes sense to have multiple compatibles automatically extracted from the device tree compatible? The way I see it having more than one compatible here just has downsides. >> The configuration already has a compatible entry. What extra use is the compatible >> entry in the FDT node? > > It allows seeing the compatible stringlist without having to read the > FDT itself. I don't believe it is necessary though, so long as we are > scanning the configurations and not the FDT nodes. I think it's better to drop this if it has no use. Cheers, Ahmad > > Regards, > Simon > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |