[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <479b9613-8244-4a29-9735-cec47e473946@quicinc.com>
Date: Tue, 1 Apr 2025 16:56:07 +0530
From: Sricharan Ramabadhran <quic_srichara@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
CC: <jassisinghbrar@...il.com>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <linux-arm-msm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
<andersson@...nel.org>, <konradybcio@...nel.org>,
<manivannan.sadhasivam@...aro.org>, <dmitry.baryshkov@...aro.org>
Subject: Re: [PATCH V4 1/2] dt-bindings: mailbox: Document qcom,ipq5424-tmel
[Resending, since my previous response had some wrapping issue]
>> TMEL(Trust Management Engine Lite) subsystem provides different kinds of
>
> Trust whatever SubSystem (TMEL SS) ...
>
> different to what?
To the ARM TrustZone firmware(TZ). So these services (secureboot,
authentication etc) were provided by the TZ in some SOCs. Here,
TMEL provides those. Can add those details here.
>
>> services like secureboot, remote image authentication, key management,
>> crypto, OEM provisioning etc.
>>
>> The QMP mailbox is the primary means of communication between TMEL SS and
>
> What is QMP?
Qualcomm Messaging Protocol
>
>> other subsystem on the SoC. A dedicated pair of inbound and outbound
>> mailboxes is implemented for each subsystem/external execution environment
>
> Is it implemented in the driver? Is it provided by the hardware? By the
> firmware?
>
TMEL firmware provides and processes the inbound requests and responds
back on the outbound channel. Can mention this explicitly in the above.
Regards,
Sricharan
Powered by blists - more mailing lists