From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Sricharan R <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: Tue, 31 Dec 2024 11:27:52 +0530 [thread overview]
Message-ID: <Z3OH4E6YIAJ2varv@hu-varada-blr.qualcomm.com> (raw)
In-Reply-To: <20241231054900.2144961-2-quic_srichara@quicinc.com>
On Tue, Dec 31, 2024 at 11:18:59AM +0530, Sricharan R wrote:
> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>
> 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.
>
> 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(TMEL SS).
>
> ----------------------------------------------- ---------------------------------------------------
> | | | |
> | SOC CLIENT | SOC | TMEL SS |
Fix alignment for last character in above line.
> | | AHB | |
> | ---------- --------- --------- | | ------ ------- -------- ------------ |
> | | | | | | | | WO | | | R | | | | |SERVICES | |
> | | APPS |<-->| TMEL |<->| |------------->| | IN |-->| | | TMEL | |-------- | |
> | | | | COM | | QMP | | RO | | | W | QMP |<--->| COM |<-->| a) ATTEST | |
> | | | | | | |<-------------| | OUT |<--| | | | | b) CRYPTO | |
> | | | | | | | | | | | | | | | | .. more | |
> | --------- --------- --------- | | ------ ------- ------- ------------ |
> | | | |
> ----------------------------------------------- --------------------------------------------------
>
> This binding describes the component responsible for communication between the
> TMEL server based subsystems (Q6) and the TMEL client (APPSS/BTSS/AUDIOSS),
> used for security services like secure image authentication, enable/disable
> efuses, crypto services. Each client in the SoC has its own block of message
> RAM and IRQ for communication with the TMEL SS.
>
> Signed-off-by: Sricharan Ramabadhran <quic_srichara@quicinc.com>
> ---
> [V2] Added HW description as per comments.
> Removed the fallback compatible.
> Fixed naming convention to TME-L in all places.
> Fixed indendation for example.
> Removed the 'description' for some items.
>
> .../bindings/mailbox/qcom,tmel-qmp.yaml | 65 +++++++++++++++++++
> 1 file changed, 65 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/qcom,tmel-qmp.yaml
>
> diff --git a/Documentation/devicetree/bindings/mailbox/qcom,tmel-qmp.yaml b/Documentation/devicetree/bindings/mailbox/qcom,tmel-qmp.yaml
> new file mode 100644
> index 000000000000..a434359e0a2c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/qcom,tmel-qmp.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/mailbox/qcom,tmel-qmp.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Qualcomm TMEL IPCC channel
> +
> +maintainers:
> + - Sricharan Ramabadhran <quic_srichara@quicinc.com>
> +
> +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
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + mboxes:
> + maxItems: 1
> +
> + "#mbox-cells":
> + const: 2
> + description:
> + The first cell is the client-id, and the second cell is the signal-id.
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - mboxes
Should 'mbox-cells' also be a required property? Since tmel_qmp_parse_devicetree -> mbox_request_channel seems to expect it.
-Varada
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + tmel_qmp: mailbox@32090000 {
> + compatible = "qcom,ipq5424-tmel-qmp";
> + reg = <0x32090000 0x2000>;
> + interrupts = <GIC_SPI 126 IRQ_TYPE_EDGE_RISING>;
> + mboxes = <&apcs_glb 20>;
> + #mbox-cells = <2>;
> + };
> +
> +...
> --
> 2.34.1
>
>
next prev parent reply other threads:[~2024-12-31 5:58 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 [this message]
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
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=Z3OH4E6YIAJ2varv@hu-varada-blr.qualcomm.com \
--to=quic_varada@quicinc.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