From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3DA51C982D8 for ; Fri, 18 Sep 2026 16:21:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Cc:List-Subscribe: List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:To:Subject :MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=xO+FV1aU8AaGxr7r3J/tyF8U+kF2bzLErzHLhc+geyQ=; b=EMib2zcIfiB89x Jsn6RdOYU5InZb/GOrO3w7rIWhJhepkAK4sP1sbIQsLyCAOfnHuOmwoeEeUhsQP7/bsSzgGdOWsWM 9mGd3+0UjpFACUrevLxZzXwNQQ6bxDv4Oei/EvYHLRP3zVQ0Qx2fP3Gk7P5H5aHVhx8wr8xt7nieb CiyA2KkMGM5egHMEsb/y2ceDE5hLLWp3LA39hnBuf1UoSL74QNzLsMCr/WrQRmQ0Vdqz5iaEuqk34 V7nFnMjO+o4cxwciV0N5O1SMphFywsYzk4RJ/8QHVpc8sciZSABh1tnl/1SXrnBYPlAYjEE0ZaXE3 yurI4HqPXjdbkMYblAeQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x7bLM-0000000F0yU-3BkC; Fri, 18 Sep 2026 16:21:44 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x7bLJ-0000000F0y9-34hn for linux-arm-kernel@lists.infradead.org; Fri, 18 Sep 2026 16:21:43 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8B4C3168F; Fri, 18 Sep 2026 09:21:35 -0700 (PDT) Received: from [100.72.146.165] (usa-sjc-mx-foss1.foss.arm.com [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 128D83F86C; Fri, 18 Sep 2026 09:21:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1789748499; bh=/OybNd89mEkvshGFEDppqY+8tuTPGqXqbXHfup9KH90=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=fJwZQlJsnMiSfZIlOizxrilzkBZz7exxuPyeBUE+ppFFDfzYKFNi6vcVdg+lyNtDa KmdZYJm5DOOZgCpSlpQZrgeFfKD+1C4gfdJFiZiSRhVNwLNf0ci9EguPOdEhr3PaSb nbk7+IZRhRJYbwXBiBuQS9kJ/054i+iRniIaE4AE= Message-ID: Date: Fri, 18 Sep 2026 18:21:34 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v3 2/8] firmware: smccc: Add support for Live Firmware Activation (LFA) To: Mark Rutland References: <20260706134455.132091-1-andre.przywara@arm.com> <20260706134455.132091-3-andre.przywara@arm.com> <20260717-bipedal-courageous-alpaca-4fb54d@sudeepholla> <84f0862c-5333-4d53-b882-79b8e4c362ed@arm.com> Content-Language: en-GB From: Andre Przywara In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260918_092142_149379_FCC53DF6 X-CRM114-Status: GOOD ( 23.21 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Conor Dooley , Trilok Soni , Salman Nabi , Rob Herring , Lorenzo Pieralisi , linux-kernel@vger.kernel.org, Varun Wadekar , Sudeep Holla , devicetree@vger.kernel.org, vsethi@nvidia.com, Nirmoy Das , Krzysztof Kozlowski , linux-arm-kernel@lists.infradead.org Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Mark, On 9/18/26 16:28, Mark Rutland wrote: > On Fri, Sep 18, 2026 at 11:13:19AM +0200, Andre Przywara wrote: >> On 7/17/26 11:03, Sudeep Holla wrote: >>> On Mon, Jul 06, 2026 at 03:44:42PM +0200, Andre Przywara wrote: > >>>> +/* A list of known GUIDs, to be shown in the "name" sysfs file. */ >>>> +static const struct fw_image_uuid { >>>> + const char *name; >>>> + const char *uuid; >>>> +} fw_images_uuids[] = { >>>> + { >>>> + .name = "TF-A BL31 runtime", >>> >>> This doesn't make any sense to me. Why do you want kernel to assign >>> some random name base on UUID. Userspace is well place to deal with >>> UUID and give it any fancy name it wants. >> >> Well, the whole interface is quite usable without any accompanying user >> space tools, so just from the shell, but then identifying firmware >> components by their GUID becomes a major pain and leaves users completely >> clueless. >> And while we indeed will never be able to fully catch up with all the >> firmwares out there, especially not with vendor specific ones, there are >> some standard firmware components that I think warrant some name. >> TF-A BL31 above (and TF-RMM) are good examples: these GUID is already in the >> mainline repository, and since BL31 is also an LFA agent, it's quite likely >> we encounter this component. Even when vendors typically use downstream TF-A >> ports, those GUIDs would stay the same. >> So yes, it's more opportunistic than complete, but I think it would help to >> identify at least those well-known firmwares. Anything not named then would >> use the GUID, and can indeed be resolved by (a yet-to-be-written) userspace >> component. > > Sudeep is right; this is not a good idea. > > Remove the table and just expose the UUID of the image. Users can map > that to a string in userspace if they need/want, and that'll work > regardless of the vintage of kernel they're using. > > I appreciate it might seem helpful to expose a name where we know it, > but overall it creates more problems, including (but not limited to) > compatibility issues, needless busywork to add entries (and arguments > about what is approriate to add), political issues when some project > naming changes, etc. Fair enough, and honestly I was expecting something like this. I just wanted to offer some compensation for the spec forcing me to put GUIDs on you. By now I can remember that the TF-RMM GUID starts with "6c", I guess that needs to suffice now ;-) Cheers, Andre > I am not going to Ack this with the name present, and I suspect neither > will Sudeep. > > Mark.