From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 A43BC275B18 for ; Fri, 12 Dec 2025 01:14:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765502076; cv=none; b=L42j6fHF4yBumXxRY6UOqHGVB7v9sAXQQS98ePQ70DdWWP51XpoEfhw736S44KJaTrdQI4MsfOy/iON+B1YUwA+aVp6RuXE+tvbTFCQorv/stcygKIOgCG7OIqAYRfJNQFpZ4oDC28/A5o7o0ap2Bnm5M+VHE6EaDk2sG18Okv8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765502076; c=relaxed/simple; bh=WiUtEdsxpAhcP+33WtOqvbqjVPW0IOOkxSjPEJ17vTg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IDQPvoYwNAEkH7VifZeENI8gNwnlMmj2NlRqZNtZlQGXQ1ZPrt9op8AeQE9VMYOo+vNH0vOgcmUwjS4QOil3CLDcKqz53fF4CToTIkKUNI+i7MSxdpnuty/GPorhA/Y64k/jzPOvW1b+8eQ+ZFL/kpDNG9+MOdNYMuM63Om+ilI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Pjd4VigT; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Pjd4VigT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B6FA8C4CEF7; Fri, 12 Dec 2025 01:14:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1765502076; bh=WiUtEdsxpAhcP+33WtOqvbqjVPW0IOOkxSjPEJ17vTg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Pjd4VigTeKcSZQRM1m7x0n1uaNz5WtekPGe1ycasYp034U31nyn/Eqf1FyYTJv5Ey mfWSqRVwmwJvIcRpEBcpw1hxWj+rBBmtdvzq3aYXsQAxOSxHw1pN8dnaLgi3AN+avl Dr7kEx5lnk39MaWWNzbE5pXSMGy1u3kgWXnm6z3vgz+1qJDdAXzz8xgxbGBSx+8Ja6 iFDJToXY4XF9/YBbetl8vcav6fln4SDWvO9gAGn7nruM/r+x751XQc+PX+zdm5oQ0g iYNdxe3VvM9s48oxKwcMwB32qmF5971Br6S++cDME6dnigggcKSnRx8lB4JdeASZBC fZN/Bc62gqH2Q== Date: Fri, 12 Dec 2025 10:14:29 +0900 From: Sumit Garg To: Krzysztof Kozlowski Cc: Harshal Dev , Bjorn Andersson , Konrad Dybcio , Dmitry Baryshkov , Jens Wiklander , Amirreza Zarrabi , Arnd Bergmann , Geert Uytterhoeven , op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] arm64: defconfig: Enable QCOMTEE on Qualcomm SM8650+ Message-ID: References: <20251208-qcom_qcomtee_defconfig-v3-1-b50dcf8ab45e@oss.qualcomm.com> <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <309e0391-58a3-466b-a113-ab864188f6fe@kernel.org> On Tue, Dec 09, 2025 at 06:58:27AM +0100, Krzysztof Kozlowski wrote: > On 08/12/2025 13:18, Harshal Dev wrote: > > Enable QCOMTEE driver on Qualcomm SM8650+ SoCs to facilitate communication > > with the Qualcomm Trusted Execution Environment (QTEE). > > (No enablement required in DTS files since QCOMTEE device is dynamically > > registered by the QCOM_SCM firmware driver) > > > > Signed-off-by: Harshal Dev > > --- > > Changes in v3: > > - Updated the commit message to reflect the supported Qualcomm platforms. > > - Link to v2: https://lore.kernel.org/r/20251205-qcom_qcomtee_defconfig-v2-1-c92560b0346e@qti.qualcomm.com > > > > I gave you the exact example to follow. Maybe it is not that important > for others, so I will not object, but OTOH it is important for me, thus > I will not give reviewed by. I damn asked VERY CLEARLY: > > "Just mention which UPSTREAM boards (which you called Qualcomm > platforms) use this driver." > > Usage of something on SoC is not a proof that it actually is used by > upstream platforms and we absolutely do not care at all about downstream > users. I spent way too much time on this and even very specific > instructions were not working, so I don't know how else I can help. Harsal, I remember myself following a list of instructions to run QTEE test application on RB5 which were part of QTEE patch-set. And I do know there are contributions going on in meta-qcom regarding those libraries here [1][2]. [1] https://github.com/qualcomm-linux/meta-qcom/pull/1167 [2] https://github.com/qualcomm-linux/meta-qcom/pull/1094 So, it would be nice if you could point people to a coherent documentation which can list instructions to reproduce setup preferably based on meta-qcom. -Sumit