From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Sricharan Ramabadhran <quic_srichara@quicinc.com>
Cc: jassisinghbrar@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
andersson@kernel.org, konradybcio@kernel.org,
manivannan.sadhasivam@linaro.org, dmitry.baryshkov@linaro.org
Subject: Re: [PATCH V4 1/2] dt-bindings: mailbox: Document qcom,ipq5424-tmel
Date: Tue, 1 Apr 2025 16:16:36 +0300 [thread overview]
Message-ID: <9efea174-80db-4e5c-b0a9-4c5fbc7e166a@oss.qualcomm.com> (raw)
In-Reply-To: <479b9613-8244-4a29-9735-cec47e473946@quicinc.com>
On 01/04/2025 14:26, Sricharan Ramabadhran wrote:
>
> [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.
Yes, please (and all other answers too).
>
>>
>>> 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
--
With best wishes
Dmitry
next prev parent reply other threads:[~2025-04-01 13:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 18:17 [PATCH V4 0/2] mailbox: tmel-qmp: Introduce QCOM TMEL QMP mailbox driver Sricharan R
2025-03-27 18:17 ` [PATCH V4 1/2] dt-bindings: mailbox: Document qcom,ipq5424-tmel Sricharan R
2025-03-28 8:02 ` Krzysztof Kozlowski
2025-04-01 7:29 ` Sricharan Ramabadhran
2025-04-15 11:08 ` Sricharan Ramabadhran
2025-12-18 4:26 ` Bjorn Andersson
2025-12-19 6:08 ` Kathiravan Thirumoorthy
2025-03-28 12:51 ` Dmitry Baryshkov
2025-04-01 8:33 ` Sricharan Ramabadhran
2025-04-01 11:26 ` Sricharan Ramabadhran
2025-04-01 13:16 ` Dmitry Baryshkov [this message]
2025-03-27 18:17 ` [PATCH V4 2/2] mailbox: tmelite-qmp: Introduce TMEL QMP mailbox driver Sricharan R
2025-04-26 9:44 ` Konrad Dybcio
2025-05-05 12:41 ` Sricharan Ramabadhran
2025-04-26 9:49 ` Konrad Dybcio
2025-05-05 13:00 ` Sricharan Ramabadhran
2025-05-20 9:36 ` Sricharan Ramabadhran
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=9efea174-80db-4e5c-b0a9-4c5fbc7e166a@oss.qualcomm.com \
--to=dmitry.baryshkov@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=jassisinghbrar@gmail.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=quic_srichara@quicinc.com \
--cc=robh@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