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 8D22D2E762A for ; Thu, 26 Jun 2025 13:49:38 +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=1750945780; cv=none; b=ENzpLg5kuHW1MAhNk+snptOO7wCyZ2/RynSPlD534dH4/GeglIGdTCkf6zpVhCkc1nLdjqN+Rxhi2pCCqJcC2Tfuhre25WENkjEeby/0CeMUEQXwmsKUo4PZAalKnnS8AkJDx5zz8MY7/RGcKIgkvkd9cfPR+P4s995HzFCZ9Yw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1750945780; c=relaxed/simple; bh=7soQAPGLWq1wxtwbCSjjPgm0cssslz7RgCt8zlMExqg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=SbdmcGA0J4wixq48+v+HpwlO8mjrYcHw4pvaugkb5VZtaqEVSBektILTQsHql+fPSLlbE7vk8XiE6aIBgO8WeoW2pzCXY8IAoqLEK49VeoSH9xrUZ3C9e9LbeqFe9McMAZKpxfeHQMwBbxW4xSojP6Qkz2H4GnTIIGjhL25XdBM= 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=Xn+dBHrN; 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="Xn+dBHrN" Received: from pps.filterd (m0279865.ppops.net [127.0.0.1]) by mx0a-0031df01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 55Q9Untn026632 for ; Thu, 26 Jun 2025 13:49:38 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= FKzdM9fMZXWLUOkRuS4r8lfC3OfMj540spQyqtt5veg=; b=Xn+dBHrN5VKvXc0D Uel7/VLxwftzvNcg9Eh+UXA2oDIDPpCMUrSFrToVuR/GTtxbE6cIaM6uB2Py1laP nxcMhFb9KNHBVokxxOa67AfuKG74utUlMGRlw4//o/kc5UvfBtYoezg6vpD1UoaB WqauyTTAPfuEVu9UMgd6nzlYj4/jq50NGJGxvyZI/UWnn05tJOh3E4cL4fvUsxCQ CXOaB+HaksjOHqBrFUZX16ZSs/oCBbfPgDQGmjyNKpOm23EajMWnHOahiUPXI+gF AbM4Vr0SAZMY+6UrVka8bOOBDDE9qxdoTJOwvYjPQh+z+HMyKEs4rRjgn9NnsPU7 LL17ag== Received: from mail-qt1-f199.google.com (mail-qt1-f199.google.com [209.85.160.199]) by mx0a-0031df01.pphosted.com (PPS) with ESMTPS id 47evc5vnte-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 26 Jun 2025 13:49:37 +0000 (GMT) Received: by mail-qt1-f199.google.com with SMTP id d75a77b69052e-4a7fb1710f9so53401cf.0 for ; Thu, 26 Jun 2025 06:49:37 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750945776; x=1751550576; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=FKzdM9fMZXWLUOkRuS4r8lfC3OfMj540spQyqtt5veg=; b=NapAvJXy/kO9BMlt/kejQIS7XL7wW/meEIOsJcJi3PEy5JyKVza8vWuDBU/RQbwzuT cUUco8DBHQ0+76Hkd8yKoZyFmWgJhkMqNaPrTSWQb9CNCXp2D28yNW+GsVC8qOSkj3VT /FcokW6PhvauhBcboUU6buCUS6L8IkcW+iBjVoXsQ/guPw3X/kshAA66JWCwXktkUB48 MjRYmHPbzkUCdwiZzdn3Q2kaOXRC7Tq9yflXgKN8RB2W2rBZQ8u1AxvR1X5/t5BU/+W+ XLJxkjojZ/JIYa6i5jzMnjGXQEtXKfTXw2XtCRGbF+ZrkbRIot4KicaJutwc1BGX87OG sAvA== X-Forwarded-Encrypted: i=1; AJvYcCXP04Q76foMP3/r6uFuRkpVnzDQJyvzUWJmnlYNp2XclQHAn+xlT1bk2IrTZx4msqHTr2GDYZjfJ8oidGM=@vger.kernel.org X-Gm-Message-State: AOJu0YzUJqSyLgOmK3a6y69WszM0NlR5dxfdI0kUxfwZ5oWqi0BPiKx2 0YBSRTIPeWhhUbnCOqBbd3JcwJzhcv2liQ9gqjdgfGYciol/GVnm/gIG303TCPmo9cCoqqcWm7i gq6uYlfO81N1UAvGSIdoPoPac0eYtq0OHxGF3tNHAVobwBmWaSO75v/fqhkTv/Ga1uLM= X-Gm-Gg: ASbGncu1oFvwbIFPt+cmqHJA8qc6vpTaynK9RaKXIo58mpKzMk+3cgAlwYaZJ1/SX0q lQTr4oQR3BNVdOApgkQzc3rtXglz1gC0NucwJK28S5bULCxzAx4T1rOund0mufs0xrjGvPtlTN0 eih0wFgDQGuXDdkF8TcnOfB1wpZqxnA4mXdn7dV+7YNWA7E2rQi78oGtl+vLzQjqHjmz6OAccaj ZQQH9bOLdy041D6QV6LwKVKjniZHFRdR8/TP+8MjKTOhv3exA9VFt+4N7Nnql6mZNahybYhkYeh MUeVlgD8VBRDgxN07acJ8y7qmQC4UrJ8AkeyWQGGk8LTlLabLGKjJOMC9R0S6HTmhaYFiRWbM2t Rt44= X-Received: by 2002:ac8:5cd2:0:b0:4a6:f7dc:d0ba with SMTP id d75a77b69052e-4a7c08a54ddmr40139491cf.3.1750945776235; Thu, 26 Jun 2025 06:49:36 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEytgFicUwxVtuRipp+MGkdKAo/DZIZy/PYmxSSSPftdTFihChTHOMq2r7K5wZn4pDMiN9TDw== X-Received: by 2002:ac8:5cd2:0:b0:4a6:f7dc:d0ba with SMTP id d75a77b69052e-4a7c08a54ddmr40139271cf.3.1750945775648; Thu, 26 Jun 2025 06:49:35 -0700 (PDT) Received: from [192.168.143.225] (078088045245.garwolin.vectranet.pl. [78.88.45.245]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-ae2143d8ee1sm2146366b.91.2025.06.26.06.49.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 26 Jun 2025 06:49:35 -0700 (PDT) Message-ID: Date: Thu, 26 Jun 2025 15:49:32 +0200 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 v2 2/4] firmware: qcom: uefisecapp: add support for R/O UEFI vars To: Johan Hovold , Dmitry Baryshkov Cc: Bjorn Andersson , Maximilian Luz , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org References: <20250621-more-qseecom-v2-0-6e8f635640c5@oss.qualcomm.com> <20250621-more-qseecom-v2-2-6e8f635640c5@oss.qualcomm.com> Content-Language: en-US From: Konrad Dybcio In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Proofpoint-GUID: JFRq3-xoZFxeoWPxZpHQRJJOyhVb5HTP X-Proofpoint-Spam-Details-Enc: AW1haW4tMjUwNjI2MDExNiBTYWx0ZWRfXyCy8vFWQ4V/s khsZsB7wkEA7qj8Wt3SDC6lg5hHWb+4M27Dt7J5d+F0A0fqkeDyUwMIrG+KHmXfY/HkmzN/9qSs Rr9EwgIWMBV9hhOlcQF8QkehT4C5m4bKukLXZSxoxS8+tIKqSA78O1CFHkdoAkmU7iGP0cwW6Ye T/Jrme/xL9Vg6kDrzY8meOp5Il7XDON7xySf3PA1Bf2FkoYaRlEj4FOyNEu3l5e2CvBb/R4uLy6 /3VnKyrcPvjXfPmdqIj6kQKRTZoTFDwQktrTNnTB8SoXscYM6VStKJlvohBP4ZzT+lQixLbfG8v /WyF0HG/z4/DakcU19KtDeJgz2UB/rOwOKeZi0QdTDeDwD4xbiIY7y1TqW0Wf0WmNLVlE/AtjL2 SHjiLi+G1PsWn4hUHwqejKV3HaRHpGJ6lH9ZWw5diZTtJtLJwXlmdWlGRA039dJywEl7BlNK X-Authority-Analysis: v=2.4 cv=caHSrmDM c=1 sm=1 tr=0 ts=685d4ff1 cx=c_pps a=WeENfcodrlLV9YRTxbY/uA==:117 a=FpWmc02/iXfjRdCD7H54yg==:17 a=IkcTkHD0fZMA:10 a=6IFa9wvqVegA:10 a=S-ZiAtxHWdWJY4AEpg4A:9 a=QEXdDO2ut3YA:10 a=kacYvNCVWA4VmyqE58fU:22 X-Proofpoint-ORIG-GUID: JFRq3-xoZFxeoWPxZpHQRJJOyhVb5HTP X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1099,Hydra:6.1.7,FMLib:17.12.80.40 definitions=2025-06-26_06,2025-06-26_04,2025-03-28_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 impostorscore=0 mlxlogscore=999 suspectscore=0 priorityscore=1501 lowpriorityscore=0 bulkscore=0 adultscore=0 mlxscore=0 spamscore=0 malwarescore=0 phishscore=0 clxscore=1015 classifier=spam authscore=0 authtc=n/a authcc= route=outbound adjust=0 reason=mlx scancount=1 engine=8.19.0-2505280000 definitions=main-2506260116 On 6/26/25 3:13 PM, Johan Hovold wrote: > On Thu, Jun 26, 2025 at 02:15:26PM +0300, Dmitry Baryshkov wrote: >> On Thu, Jun 26, 2025 at 11:42:50AM +0200, Johan Hovold wrote: >>> On Tue, Jun 24, 2025 at 04:13:34AM +0300, Dmitry Baryshkov wrote: >>>> On Mon, Jun 23, 2025 at 04:50:27PM +0200, Johan Hovold wrote: >>>>> On Mon, Jun 23, 2025 at 04:45:30PM +0200, Johan Hovold wrote: >>> >>>>>> Also not sure how useful it is to only be able to read variables, >>>>>> including for the RTC where you'll end up with an RTC that's always >>>>>> slightly off due to drift (even if you can set it when booting into >>>>>> Windows or possibly from the UEFI setup). >>>>>> >>>>>> Don't you have any SDAM blocks in the PMICs that you can use instead for >>>>>> a proper functioning RTC on these machines? >>>> >>>> I'd rather not poke into an SDAM, especially since we don't have docs >>>> which SDAM blocks are used and which are not. >>> >>> You're with Qualcomm now so you should be able to dig up this >>> information like we did for the X13s (even if I'm quite aware that it >>> may still be easier said than done). >> >> I'd rather try to find information on how to update UEFI vars on the >> storage. > > You can do both, especially if it turns out you won't be able to have > persistent variables on these machines. The danger here is that we only know what Qualcomm uses these cells for, not necessarily what the vendors with a similar idea could have come up with. This is especially important since (unfortunately without going into detail), you *really* don't want to mess up some existing values in there. Konrad