[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ae1d7f9-63da-47fd-8c39-4a87e2ce97c8@quicinc.com>
Date: Mon, 6 Jan 2025 11:06:21 +0530
From: Sricharan Ramabadhran <quic_srichara@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
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 V2 1/2] dt-bindings: mailbox: Document qcom,tmel-qmp
On 1/4/2025 12:13 AM, Krzysztof Kozlowski wrote:
> On 03/01/2025 19:34, Sricharan Ramabadhran wrote:
>>>> +description:
>>>> + TMEL SS provides different kinds of services like secureboot, remote image
>>>> + authentication, key management, crypto, OEM provisioning etc. This patch adds
>>>> + support for remote image authentication. Support for rest of the services can
>>>> + be added.
>>>> +
>>>> + The QMP mailbox is the primary means of communication between TMEL SS and
>>>> + other subsystem on the SoC. A dedicated pair of inbound and outbound mailboxes
>>>> + is implemented for each subsystem/external execution environment which needs to
>>>> + communicate with TMEL for security services. The inbound mailboxes are used to
>>>> + send IPC requests to TMEL, which are then processed by TMEL firmware and
>>>> + accordingly the responses are sent to the requestor via outbound mailboxes.
>>>> +
>>>> +properties:
>>>> + compatible:
>>>> + items:
>>>> + - enum:
>>>> + - qcom,ipq5424-tmel-qmp
>>>
>>>
>>> Why qmp? Can TMEL on IPQ5424 be anything else? Can TMEL be SMEM or using
>>> any other remoteproc?
>>>
>> TMEL on IPQ5424 uses only QMP protocol for communication.
>
>
> Then keep just "tmel". It completely defines this device.
ok.
Regards,
Sricharan
Powered by blists - more mailing lists