From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx0a-0031df01.pphosted.com (mx0a-0031df01.pphosted.com [205.220.168.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BFAFE30BF62 for ; Fri, 6 Feb 2026 06:37:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=205.220.168.131 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770359850; cv=none; b=G9+APpY7UGYoyg0tah+bAEVXawbQb9Po6qKZWd2IR3T7UN455eYmag+++yoQtZ/27E+YnkPXE8qbe0lIFCnUS6xqVMlmE5TfNpwmhHW4AzS0phnM4mtiUvum5bIYsjBLz6fMkI8o2qiIozht8ItQTBeVwOmUngtrzmishDil0pg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770359850; c=relaxed/simple; bh=hCSuUhyDepKovVFfLIXEK7iiZgvW4TMXo63DsbeUx+s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=l2vQDIo/R6LOJXrKSRclo2B9tep1cRgT6qnXhLLbwlLOqGEJn0yXi5uMHfOvAva80h9PSMbuAUuBsVhnJpaGwdMM6T6S3VgDyUyM/voV+mexWLnlM7yBckrcCU8atLcp+hDX8eTHDKhcPIGu+lQ7ZCKIbuMJ2P4e6u6KPRnzPH0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com; spf=pass smtp.mailfrom=oss.qualcomm.com; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b=PMdB0Eyg; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b=B56WGijz; arc=none smtp.client-ip=205.220.168.131 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=oss.qualcomm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=qualcomm.com header.i=@qualcomm.com header.b="PMdB0Eyg"; dkim=pass (2048-bit key) header.d=oss.qualcomm.com header.i=@oss.qualcomm.com header.b="B56WGijz" Received: from pps.filterd (m0279863.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.11/8.18.1.11) with ESMTP id 6160xdJE1630197 for ; Fri, 6 Feb 2026 06:37:30 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qualcomm.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to; s=qcppdkim1; bh= YQ77QTJWVPIZC+3oQok+biilGV/ElhSJIADxlZKOIi4=; b=PMdB0EygjMwZ2v4s 8JWvxgJZt8aBWH/dFEJ92zCZnJ2gL7g2Kb+jSOCvCR8XuCgViI3hNnrL6u6mZtqq I5ASHxMsmh/SFTukk3uadZXbBeeES5mkB7HGuDNpdXvMYGuho8j8ea3t5yLW0jus AFWPKzh4WOFrte/Vvw0vCwGPKBLrktHLRiesGy2fPzFP34JpMt6Q6xeecvOrzuss ZwODlJHN/7GOi2d30ezxTx7cGwU6rD3R0aFYGPVkrBnrY6d0Mw8Jx2uB6M/AY13I 24j5+7od4inTon7ffDGJeEZO7r4LQWuYxsOwmj1jGXFYZ0+kEWdHVsmNV0SwDSTW o4maEw== Received: from mail-dy1-f200.google.com (mail-dy1-f200.google.com [74.125.82.200]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 4c4tm8udea-1 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Fri, 06 Feb 2026 06:37:29 +0000 (GMT) Received: by mail-dy1-f200.google.com with SMTP id 5a478bee46e88-2b7ef896edcso13482416eec.0 for ; Thu, 05 Feb 2026 22:37:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oss.qualcomm.com; s=google; t=1770359849; x=1770964649; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=YQ77QTJWVPIZC+3oQok+biilGV/ElhSJIADxlZKOIi4=; b=B56WGijzSNOwQy7KVyLVzuL4F2TgINrbSFhQj6WzFqPO5dFixquRfzIUoHJWe0C6+0 PXluzXGqE1k7AcJBd7tyerCR51EQDzvSjBZ2lknjeZbfkWfFTooRQxYv8FZXwflJeBdM CDl0qhrIz+bswMtqccemtJV9aOuMJYlcnPfPZlrA2Ub62MmGcaevzn4pmcdik4sku1g7 jQFnWG221c2wEU/r7w52wTkBIQ3RuKkbvzHaYpWRKYRdhyGh0OfWZ2PS3LfmvJfyqppV gAcDegdBggdyY4pMr3v0b4V1zvXSYSf4gyc6C1bE4fqDFy2Xk+h76eiOoMOVB8v2zB8G wNdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770359849; x=1770964649; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YQ77QTJWVPIZC+3oQok+biilGV/ElhSJIADxlZKOIi4=; b=mDloFpwFSjPpl1C92XP5PJbkNzqM0vysyS9bqz0/Vuk7jRPQoCf3rb5D96wLZZwi5p ltGtcsvqBI2wMWBJJFpPuqC2mQGz5N/TmqBHnF3o3jtUWlTK1fFpTAarr0QDHtW7DCIn V5p8my4O2J0n9/ypEHz9gISpJaTjb9fqBc86ChLJ5fsHzY2WEiZW58suHB8EetVzqz2M KZ462kpwwgSxhDmNbSSuUh7ce5XJaqapQ2B1xfAkcxBdOkNRb0R15p+kSGydrxNirru7 zJ5oIbACEpQez9tUMZ9ewbClT+3kqozLlLMs7i2iJyyP+pR/H7ZHWRQ2Ohr4xHpLN0xF 1okw== X-Forwarded-Encrypted: i=1; AJvYcCXGe46Z9X5ESl4WFCRbRdTFbvnWZa7MQwSMWhrLdYA4dZvx8zICZHOFvghbPXtzG+E6ojlGcZxxA5bVxgo=@vger.kernel.org X-Gm-Message-State: AOJu0YxIOPg6HCpG4TZVQTZfSp3JU6YP9yQ30vo9NuzD43ccxrIeYv7L 0z5kWxsrL7tHGoOc6aRyIIq44FNggGYvLGtsaucobMz3Z0A1XCDdZwKSoqxMNd6OHacoHYhVpaB dIHaFuA4/9ING6VQL6juScMXX397seSdB6vh1VizmvLX5XEjN5H7iEJCetJJzqJ0U19U= X-Gm-Gg: AZuq6aKYIVsmBsaEY0qZPm/rysc4+2KU3IGCzHh8scurjpUyggl3V2cll2g8cKDjc9H 0G2iBFPlShTB4JAzQYedF60yv4BS25ftLRcngLNKPLDeAJlFc9hkOtstRQnNCyig2/A7rQlMxNd tHfC9H66d4H/Yqw6mu20yTSu+dEaHqg1JiRBpB9LMBz/w15R90lYrAdnXIa3hzbTT1bTMGZAwan VD7qPu5WpBGCn1c5lYlgkaHXyEQhD5c82NjudsmkipDozsbDN3jCjl2CVppx2bVMa7lVLE3j44d JKngVcRIBGn0D6sqdCaCtVIu4rsp7AsKkZw4kcZqcV/ELczP/K7hH9lgT6MQ7qOD+pqZSYjydb8 KlRO6kY24YOvJgLwJ+CFk35wg5VUiLhpBsLg35JbG/WM= X-Received: by 2002:a05:7300:fb97:b0:2ae:5ffa:8daa with SMTP id 5a478bee46e88-2b8563d94dbmr847096eec.5.1770359849131; Thu, 05 Feb 2026 22:37:29 -0800 (PST) X-Received: by 2002:a05:7300:fb97:b0:2ae:5ffa:8daa with SMTP id 5a478bee46e88-2b8563d94dbmr847072eec.5.1770359848561; Thu, 05 Feb 2026 22:37:28 -0800 (PST) Received: from [192.168.86.165] ([76.176.48.107]) by smtp.gmail.com with ESMTPSA id 5a478bee46e88-2b855af7806sm1181131eec.10.2026.02.05.22.37.27 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 05 Feb 2026 22:37:28 -0800 (PST) Message-ID: <8ff96355-4a53-4790-9d2c-ea7d63be77c4@oss.qualcomm.com> Date: Thu, 5 Feb 2026 22:37:26 -0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 1/1] firmware: smccc: add support for Live Firmware Activation (LFA) To: Salman Nabi , vvidwans@nvidia.com, andre.przywara@arm.com, sudeep.holla@arm.com, mark.rutland@arm.com, lpieralisi@kernel.org Cc: ardb@kernel.org, chao.gao@intel.com, linux-arm-kernel@lists.infradead.org, linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org, sdonthineni@nvidia.com, vsethi@nvidia.com, vwadekar@nvidia.com References: <20260119122729.287522-1-salman.nabi@arm.com> <20260119122729.287522-2-salman.nabi@arm.com> Content-Language: en-US From: Trilok Soni In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Authority-Analysis: v=2.4 cv=Vd76/Vp9 c=1 sm=1 tr=0 ts=69858c29 cx=c_pps a=PfFC4Oe2JQzmKTvty2cRDw==:117 a=lsoD3MMNObdLvy1227ExmA==:17 a=IkcTkHD0fZMA:10 a=HzLeVaNsDn8A:10 a=s4-Qcg_JpJYA:10 a=VkNPw1HP01LnGYTKEx00:22 a=Mpw57Om8IfrbqaoTuvik:22 a=GgsMoib0sEa3-_RKJdDe:22 a=6HHVuAIMxnVHkOBFbdoA:9 a=QEXdDO2ut3YA:10 a=6Ab_bkdmUrQuMsNx7PHu:22 X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwMjA2MDAzNiBTYWx0ZWRfX6x+HYatKaQuz UpF3nDLEgdM8ozAbgu6oqtYSmit9lKVmP9JL2hGLRX6roE585lsSuk4GPkhM50SjKNHR+90Jhr4 qyxuOtYeyfg7pjXKfax1CGwy9Y8fcA8JcuwTcrMJAVfZ4MwMzN6NvmchSJ0j6S+fWrdrrJ9C7KA 2nnoK+8SA0JdwDu24LsVCZA6rAOgaVfOPyKdkmIuvkr7xV7nirCiJye0a0JXaxYFLGh8w/dkhRM ncq8pdBmjVKbWrRDVqr5XhQBmMdH9DWto6CjT4vSBFVPZXcN/KmPy/VP6mdsQn5Ah6HrZp1wkH5 ZW14f+pZz0EH2/QhXSzFAHWh/7NvGQflSEeGpyrCXI4BFB2ZdncBJcKlAqWU5tJXhrV5soQtR9O T0iK3Hr624pruFVKEtOv8NPspJOZLSbM8YZrlS1O1fsd0y68pESeAiT4OYrMw0nvBIj//tSzKE9 cg3Oxbe7AuQ4kizbAfw== X-Proofpoint-ORIG-GUID: _7Eg8SXHSnCixO09lnPedaCCKdBYQcXw X-Proofpoint-GUID: _7Eg8SXHSnCixO09lnPedaCCKdBYQcXw X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1121,Hydra:6.1.51,FMLib:17.12.100.49 definitions=2026-02-06_01,2026-02-05_03,2025-10-01_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1015 impostorscore=0 bulkscore=0 phishscore=0 suspectscore=0 priorityscore=1501 lowpriorityscore=0 adultscore=0 spamscore=0 malwarescore=0 classifier=typeunknown authscore=0 authtc= authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.22.0-2601150000 definitions=main-2602060036 On 2/2/2026 7:52 AM, Salman Nabi wrote: > Hi Trilok, > > On 1/31/26 01:35, Trilok Soni wrote: >> On 1/19/2026 4:27 AM, Salman Nabi wrote: >>> The Arm Live Firmware Activation (LFA) is a specification [1] to describe >>> activating firmware components without a reboot. Those components >>> (like TF-A's BL31, EDK-II, TF-RMM, secure paylods) would be updated the s/paylods/payloads >>> usual way: via fwupd, FF-A or other secure storage methods, or via some >>> IMPDEF Out-Of-Bound method. The user can then activate this new firmware, >>> at system runtime, without requiring a reboot. >>> The specification covers the SMCCC interface to list and query available >>> components and eventually trigger the activation. >>> >>> Add a new directory under /sys/firmware to present firmware components >>> capable of live activation. Each of them is a directory under lfa/, >>> and is identified via its GUID. The activation will be triggered by echoing >>> "1" into the "activate" file: >>> ========================================== >>> /sys/firmware/lfa # ls -l . 6c* >>> .: >>> total 0 >>> drwxr-xr-x 2 0 0 0 Jan 19 11:33 47d4086d-4cfe-9846-9b95-2950cbbd5a00 >>> drwxr-xr-x 2 0 0 0 Jan 19 11:33 6c0762a6-12f2-4b56-92cb-ba8f633606d9 >>> drwxr-xr-x 2 0 0 0 Jan 19 11:33 d6d0eea7-fcea-d54b-9782-9934f234b6e4 >> Can you please explain or add a note on why we don't have name of the firmware >> as the directory name and why you have selected GUID as top-level >> directory name? > > > We obtain the GUIDs of firmware components from the LFA agent in TF-A, which does not provide their names. For convenience, we have added a C structure in the driver to associate each firmware GUID with its corresponding name. Because new firmware components may be supported in the LFA agent before their GUID-to-name mapping is added to the driver, we avoid using the firmware name as the directory (kobject) name. > > Additionally, sysfs requires directory names to be unique among siblings. Since GUIDs are inherently unique, they provide a convenient, collision-free choice for directory names. Thank you for the explanation. Please add these details in the commit text. ---Trilok Soni