[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <640201c7-84d5-4564-8ef3-afcc39929fd9@kernel.org>
Date: Thu, 5 Dec 2024 12:43:23 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sricharan Ramabadhran <quic_srichara@...cinc.com>,
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
Subject: Re: [PATCH RFC 1/2] dt-bindings: mailbox: qcom: Document
qcom,tmelite-qmp
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@...cinc.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.
Best regards,
Krzysztof
Powered by blists - more mailing lists