Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Sricharan Ramabadhran <quic_srichara@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
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 V4 1/2] dt-bindings: mailbox: Document qcom,ipq5424-tmel
Date: Tue, 15 Apr 2025 16:38:44 +0530	[thread overview]
Message-ID: <2b132133-9c03-4b7a-b59a-e0f701dfbd01@quicinc.com> (raw)
In-Reply-To: <321e1d4a-5aa3-49cb-8a85-e05dbaa08e78@quicinc.com>



On 4/1/2025 12:59 PM, Sricharan Ramabadhran wrote:
> 
> 
> On 3/28/2025 1:32 PM, Krzysztof Kozlowski wrote:
>> On Thu, Mar 27, 2025 at 11:47:49PM +0530, Sricharan R wrote:
>>> +properties:
>>> +  compatible:
>>> +    items:
>>> +      - enum:
>>> +          - qcom,ipq5424-tmel
>>
>> blank line
> ok
> 
>>
>>> +  reg:
>>> +    maxItems: 1
>>> +
>>> +  interrupts:
>>> +    maxItems: 1
>>> +
>>> +  mboxes:
>>> +    maxItems: 1
>>
>> Why mbox is having an mbox? This does not look right and suggest the
>> block is misrepresented. I read the diagram and description two times
>> and still do not see how this fits there.
> TMEL/QMP secure functionalities are exposed to clients (like rproc) by 
> registering TMEL as mailbox controller. The IPC bit to communicate with 
> the TMEL/QMP controller itself is handled by the apcs mailbox. Hence
> it looks like a mbox inside mbox.
> 
> Alternatively, would it be fine to fold the IPC bit handling in this 
> driver itself for doing the regmap_write (instead of connecting to
> apcs mailbox separately) ?
> 
> Also, there are couple of other ways of designing this as well.
> Earlier i mentioned this in the RFC post [1] for getting the design
> sorted out.
> 
> [1] https://lore.kernel.org/lkml/20241205080633.2623142-1- 
> quic_srichara@quicinc.com/T/
> 
> -------------------------------------------------------------
> Had the below mentioned in the RFC earlier.
> 
> The intention of posting this is to get the design reviewed/corrected 
> since there are also other possible ways of having this SS support like:
> 
> a) Make TMEL QMP as a 'rpmsg' driver and clients can connect using
>     rmpsg_send
> 
> b) Keep TMEL APIs seperately in drivers/firmware which would export APIs
>     and QMP mailbox seperately.
>     Clients can then call the exported APIS.
> 
> c) Combine both TMEL and QMP as mailbox (this is the approach used here)
> 

Hi Krysztof,

Can you kindly provide your suggestion on how to proceed for the above ?
Would want to align on the design approach before posting the next
version.

Regards,
  Sricharan

  reply	other threads:[~2025-04-15 11:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-27 18:17 [PATCH V4 0/2] mailbox: tmel-qmp: Introduce QCOM TMEL QMP mailbox driver Sricharan R
2025-03-27 18:17 ` [PATCH V4 1/2] dt-bindings: mailbox: Document qcom,ipq5424-tmel Sricharan R
2025-03-28  8:02   ` Krzysztof Kozlowski
2025-04-01  7:29     ` Sricharan Ramabadhran
2025-04-15 11:08       ` Sricharan Ramabadhran [this message]
2025-12-18  4:26         ` Bjorn Andersson
2025-12-19  6:08           ` Kathiravan Thirumoorthy
2025-03-28 12:51   ` Dmitry Baryshkov
2025-04-01  8:33     ` Sricharan Ramabadhran
2025-04-01 11:26     ` Sricharan Ramabadhran
2025-04-01 13:16       ` Dmitry Baryshkov
2025-03-27 18:17 ` [PATCH V4 2/2] mailbox: tmelite-qmp: Introduce TMEL QMP mailbox driver Sricharan R
2025-04-26  9:44   ` Konrad Dybcio
2025-05-05 12:41     ` Sricharan Ramabadhran
2025-04-26  9:49   ` Konrad Dybcio
2025-05-05 13:00     ` Sricharan Ramabadhran
2025-05-20  9:36     ` 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=2b132133-9c03-4b7a-b59a-e0f701dfbd01@quicinc.com \
    --to=quic_srichara@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=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.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