From: Krzysztof Kozlowski <krzk@kernel.org>
To: Luca Weiss <luca@z3ntu.xyz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] dt-bindings: soc: qcom,smsm: Allow specifying mboxes instead of qcom,ipc
Date: Wed, 22 May 2024 08:49:43 +0200 [thread overview]
Message-ID: <12896bf6-412c-40af-9ad5-f9391ff81f63@kernel.org> (raw)
In-Reply-To: <5780452.DvuYhMxLoT@g550jk>
On 21/05/2024 22:35, Luca Weiss wrote:
> On Dienstag, 21. Mai 2024 10:58:07 MESZ Krzysztof Kozlowski wrote:
>> On 20/05/2024 17:11, Luca Weiss wrote:
>>> Hi Krzysztof
>>>
>>> Ack, sounds good.
>>>
>>> Maybe also from you, any opinion between these two binding styles?
>>>
>>> So first using index of mboxes for the numbering, where for the known
>>> usages the first element (and sometimes the 3rd - ipc-2) are empty <>.
>>>
>>> The second variant is using mbox-names to get the correct channel-mbox
>>> mapping.
>>>
>>> - qcom,ipc-1 = <&apcs 8 13>;
>>> - qcom,ipc-2 = <&apcs 8 9>;
>>> - qcom,ipc-3 = <&apcs 8 19>;
>>> + mboxes = <0>, <&apcs 13>, <&apcs 9>, <&apcs 19>;
>>>
>>> vs.
>>>
>>> - qcom,ipc-1 = <&apcs 8 13>;
>>> - qcom,ipc-2 = <&apcs 8 9>;
>>> - qcom,ipc-3 = <&apcs 8 19>;
>>> + mboxes = <&apcs 13>, <&apcs 9>, <&apcs 19>;
>>> + mbox-names = "ipc-1", "ipc-2", "ipc-3";
>>
>> Sorry, don't get, ipc-1 is the first mailbox, so why would there be <0>
>> in first case?
>
> Actually not, ipc-0 would be permissible by the driver, used for the 0th host
>
> e.g. from:
>
> /* Iterate over all hosts to check whom wants a kick */
> for (host = 0; host < smsm->num_hosts; host++) {
> hostp = &smsm->hosts[host];
>
> Even though no mailbox is specified in any upstream dts for this 0th host I
> didn't want the bindings to restrict that, that's why in the first example
> there's an empty element (<0>) for the 0th smsm host
>
>> Anyway, the question is if you need to know that some
>> mailbox is missing. But then it is weird to name them "ipc-1" etc.
>
> In either case we'd just query the mbox (either by name or index) and then
> see if it's there? Not quite sure I understand the sentence..
> Pretty sure either binding would work the same way.
The question is: does the driver care only about having some mailboxes
or the driver cares about each specific mailbox? IOW, is skipping ipc-0
important for the driver?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-05-22 6:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 17:21 [PATCH RFC 0/2] Support mailbox interface in qcom,smsm driver Luca Weiss
2024-04-24 17:21 ` [PATCH RFC 1/2] dt-bindings: soc: qcom,smsm: Allow specifying mboxes instead of qcom,ipc Luca Weiss
2024-04-25 16:17 ` Rob Herring
2024-04-25 18:54 ` Luca Weiss
2024-05-15 15:06 ` Luca Weiss
2024-05-20 6:46 ` Krzysztof Kozlowski
2024-05-20 15:11 ` Luca Weiss
2024-05-21 8:58 ` Krzysztof Kozlowski
2024-05-21 20:35 ` Luca Weiss
2024-05-22 6:49 ` Krzysztof Kozlowski [this message]
2024-05-22 17:34 ` Luca Weiss
2024-05-23 6:02 ` Krzysztof Kozlowski
2024-05-23 6:16 ` Luca Weiss
2024-05-23 6:19 ` Krzysztof Kozlowski
2024-05-24 17:55 ` Luca Weiss
2024-05-25 16:47 ` Krzysztof Kozlowski
2024-05-29 15:28 ` Luca Weiss
2024-04-24 17:21 ` [PATCH RFC 2/2] soc: qcom: smsm: Support using mailbox interface Luca Weiss
2024-04-24 20:13 ` Konrad Dybcio
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=12896bf6-412c-40af-9ad5-f9391ff81f63@kernel.org \
--to=krzk@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).