From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <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 1/2] dt-bindings: mailbox: qcom: Document qcom,tmelite-qmp
Date: Fri, 6 Dec 2024 10:57:31 +0530 [thread overview]
Message-ID: <01a4eb57-d7bc-4d0b-82f6-d3c19a089966@quicinc.com> (raw)
In-Reply-To: <640201c7-84d5-4564-8ef3-afcc39929fd9@kernel.org>
On 12/5/2024 5:13 PM, Krzysztof Kozlowski wrote:
> On 05/12/2024 10:17, Sricharan Ramabadhran wrote:
>>
>>
>> On 12/5/2024 1:42 PM, Krzysztof Kozlowski wrote:
>>> On 05/12/2024 09:06, Sricharan R wrote:
>>>> From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
>>>>
>>>> This binding describes the component responsible for communication
>>>> between the TME-L server based subsystems (Q6) and the TME-L 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 TME-L SS. The protocol used to communicate in the message RAM
>>>> is known as Qualcomm Messaging Protocol (QMP).
>>>
>>> This is RFC, so only limited review follows. I will review more once
>>> this is ready for review.
>>>
>> Thanks. Once i get the design/approach confirmed, will post the V1.
>
> Not a v1, but next version. This was v1 already, because we do not count
> from 0. Please use b4 to avoid such mistakes.
Ok, understand.
Regards,
Sricharan
next prev parent reply other threads:[~2024-12-06 5:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 8:06 [PATCH RFC 0/2] mailbox: tmelite-qmp: Introduce QCOM TMEL QMP mailbox driver 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 [this message]
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
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=01a4eb57-d7bc-4d0b-82f6-d3c19a089966@quicinc.com \
--to=quic_srichara@quicinc.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®