From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sricharan R <quic_srichara@quicinc.com>,
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
Subject: Re: [PATCH RFC 2/2] mailbox: tmelite-qmp: Introduce QCOM TMEL QMP mailbox driver
Date: Thu, 5 Dec 2024 09:14:43 +0100 [thread overview]
Message-ID: <06b48a7f-de53-4b53-b3ac-be9efcee5558@kernel.org> (raw)
In-Reply-To: <20241205080633.2623142-3-quic_srichara@quicinc.com>
On 05/12/2024 09:06, Sricharan R wrote:
> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>
> The QMP mailbox is the primary means of communication between TME-L 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 TME-L for security services. The inbound
> mailboxes are used to send IPC requests to TME-L, which are then processed
> by TME-L firmware and accordingly the responses are sent to the requestor
> via outbound mailboxes.
>
> It is an IPC transport protocol which is light weight and supports
> a subset of API's. It handles link initialization, negotiation,
> establishment and communication across client(APPSS/BTSS/AUDIOSS)
> and server(TME-L SS).
>
> ----------------------------------------------- ---------------------------------------------------
> | | | |
> | SOC CLIENT | SOC | TME-L SS |
> | | AHB | |
> | ---------- --------- --------- | | ------ ------- -------- ------------ |
> | | | | | | | | WO | | | R | | | | |SERVICES | |
> | | APPS |<-->| TMEL |<->| |------------->| | IN |-->| | | TMEL | |-------- | |
> | | | | COM | | QMP | | RO | | | W | QMP |<--->| COM |<-->| a) ATTEST | |
> | | | | | | |<-------------| | OUT |<--| | | | | b) CRYPTO | |
> | | | | | | | | | | | | | | | | .. more | |
> | --------- --------- --------- | | ------ ------- ------- ------------ |
> | | | |
> ----------------------------------------------- --------------------------------------------------
Hardware description is much more suitable for the binding, not to the
driver. You wrote the same in cover letter and here... but not in actual
hardware description - binding.
>
> TME-L 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.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Remote proc driver subscribes to this mailbox and uses the mbox_send_message to use
> TME-L to securely authenticate/teardown the images.
>
> The intention of posting this is to get the design reviewed/corrected since there are also
> other possible ways of having this SS support.
If you do not Cc maintainers, don't expect much answer. Missing Qcom amd
remoteproc maintainers.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-05 8:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:06 [PATCH RFC 0/2] " Sricharan R
2024-12-05 8:06 ` [PATCH RFC 1/2] dt-bindings: mailbox: qcom: Document qcom,tmelite-qmp Sricharan R
2024-12-05 8:12 ` Krzysztof Kozlowski
2024-12-05 9:17 ` Sricharan Ramabadhran
2024-12-05 11:43 ` Krzysztof Kozlowski
2024-12-06 5:27 ` Sricharan Ramabadhran
2024-12-05 12:24 ` Dmitry Baryshkov
2024-12-06 5:30 ` Sricharan Ramabadhran
2024-12-05 8:06 ` [PATCH RFC 2/2] mailbox: tmelite-qmp: Introduce QCOM TMEL QMP mailbox driver Sricharan R
2024-12-05 8:14 ` Krzysztof Kozlowski [this message]
2024-12-05 9:07 ` 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=06b48a7f-de53-4b53-b3ac-be9efcee5558@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®