From: Krzysztof Kozlowski <krzk@kernel.org>
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 V2 1/2] dt-bindings: mailbox: Document qcom,tmel-qmp
Date: Fri, 3 Jan 2025 19:43:18 +0100 [thread overview]
Message-ID: <d78bc184-b035-41bb-b5eb-088a86c6b77d@kernel.org> (raw)
In-Reply-To: <ac15561f-b9e7-4434-af1a-04408172d46c@quicinc.com>
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.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-03 18:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 5:48 [PATCH V2 0/2] mailbox: tmel-qmp: Introduce QCOM TMEL QMP mailbox driver Sricharan R
2024-12-31 5:48 ` [PATCH V2 1/2] dt-bindings: mailbox: Document qcom,tmel-qmp Sricharan R
2024-12-31 5:57 ` Varadarajan Narayanan
2025-01-03 11:56 ` Sricharan Ramabadhran
2024-12-31 8:32 ` Krzysztof Kozlowski
2025-01-03 18:34 ` Sricharan Ramabadhran
2025-01-03 18:43 ` Krzysztof Kozlowski [this message]
2025-01-06 5:36 ` Sricharan Ramabadhran
2024-12-31 9:32 ` Konrad Dybcio
2025-01-03 18:34 ` Sricharan Ramabadhran
2024-12-31 5:49 ` [PATCH V2 2/2] mailbox: tmelite-qmp: Introduce TMEL QMP mailbox driver Sricharan R
2024-12-31 6:21 ` Varadarajan Narayanan
2025-01-03 12:09 ` Sricharan Ramabadhran
2024-12-31 8:06 ` Krzysztof Kozlowski
2025-01-03 12:29 ` Sricharan Ramabadhran
2024-12-31 16:22 ` Dmitry Baryshkov
2025-01-06 10:29 ` Sricharan Ramabadhran
2024-12-31 18:59 ` kernel test robot
2025-01-01 9:34 ` kernel test robot
2024-12-31 7:57 ` [PATCH V2 0/2] mailbox: tmel-qmp: Introduce QCOM " Krzysztof Kozlowski
2025-01-03 12:10 ` Sricharan Ramabadhran
2025-01-03 12:41 ` Krzysztof Kozlowski
2025-01-24 5:53 ` Jeff Johnson
2025-01-27 10:27 ` 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=d78bc184-b035-41bb-b5eb-088a86c6b77d@kernel.org \
--to=krzk@kernel.org \
--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