mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Sumit Garg <sumit.garg@kernel.org>,
	Jens Wiklander <jens.wiklander@linaro.org>
Cc: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: defconfig: Enable QCOMTEE for Qualcomm SoCs
Date: Fri, 5 Dec 2025 12:12:39 +0100	[thread overview]
Message-ID: <083ebd3c-6d19-44c4-9a46-f7fba01111bf@kernel.org> (raw)
In-Reply-To: <4d4a6614-9460-48b4-8e6a-77d3395abfbf@oss.qualcomm.com>

On 05/12/2025 11:58, Harshal Dev wrote:
> Hi Krzysztof
> 
> On 12/5/2025 1:45 PM, Krzysztof Kozlowski wrote:
>> On 05/12/2025 09:12, Harshal Dev wrote:
>>> Enable config 'm' for the QCOMTEE driver to facilitate communication with
>>> the Qualcomm Trusted Execution Environment (QTEE) on Qualcomm platforms.
>>
>> I can do it forever, but next time I will just NAK.
>>
>> Which platforms need this? Which platforms use this?
> 
> Looks like I misunderstood your comment on the last patch regarding Qualcomm
> platform support for this driver as more of a generic question instead of being
> a hard request to update the commit message. 
> https://lore.kernel.org/all/f20833a4-1571-41f8-875a-d27086be3090@oss.qualcomm.com/
> 
> I will take care of this now, however I am still a bit confused regarding how many
> platforms should I explicitly list out in the commit message. I took reference of

Just mention which UPSTREAM boards (which you called Qualcomm platforms)
use this driver. It's enough to mention one, for justification of
commit. You can mention two as well. Or three.

> these below patches merged earlier in the defconfig for enabling the QCE crypto block driver,
> Qualcomm Watchdog driver and Qualcomm RNG driver. And I did not see them listing out
> any specific Qualcomm platforms which need/use these drivers. I understand that this is
> because the drivers provide generic functionality applicable on all Qualcomm SoCs.
> https://lore.kernel.org/all/20220921045602.1462007-5-bhupesh.sharma@linaro.org/
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f27dbbda5900c20e07418c6893ca6e95b634f4ff
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2774e558151a6e325e1f9f278722479601319f78

:) unfortunately all poor examples. And from 2019! You can find many
poor examples in the kernel - in commit msgs or code. You can find many
obsolete drivers written in old, not updated style. These are not
examples to be based on.

Usually it is the best to take LATEST reviewed code, not something 6
years old, so the process would be:

tig -- arch/arm64/configs/defconfig
/Qualcomm
(or whatever search query you want)
Which would give you commit c5d02bbaa217b2454ba1ce7528113aa2ecf14f3c
from June for example. It even caries two review tags.

> 
> Similarly, all Qualcomm SoCs have ARM TrustZone support with a QTEE firmware OS running.
> The version of the firmware might differ, but it is always there, and so the QCOMTEE driver is
> applicable to all Qualcomm SoCs just like the Watchdog or RNG driver.

You can say that all Qualcomm platforms use it... but I would challange
it, because not all platforms use watchdog or RNG.

Best regards,
Krzysztof

  reply	other threads:[~2025-12-05 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  8:12 Harshal Dev
2025-12-05  8:15 ` Krzysztof Kozlowski
2025-12-05 10:58   ` Harshal Dev
2025-12-05 11:12     ` Krzysztof Kozlowski [this message]
2025-12-07  7:50       ` Harshal Dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=083ebd3c-6d19-44c4-9a46-f7fba01111bf@kernel.org \
    --to=krzk@kernel.org \
    --cc=amirreza.zarrabi@oss.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=geert+renesas@glider.be \
    --cc=harshal.dev@oss.qualcomm.com \
    --cc=jens.wiklander@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=sumit.garg@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®