From: Krzysztof Kozlowski <krzk@kernel.org>
To: Justin Chen <justin.chen@broadcom.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: florian.fainelli@broadcom.com, conor+dt@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, jassisinghbrar@gmail.com,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 2/2] dt-bindings: mailbox: Add devicetree binding for bcm74110 mbox
Date: Sat, 29 Mar 2025 05:35:09 +0100 [thread overview]
Message-ID: <5a460228-ab50-490d-a222-d6a10aea3ff0@kernel.org> (raw)
In-Reply-To: <cb0905ec-1e80-4c56-befd-b90243dcfa31@broadcom.com>
On 28/03/2025 19:36, Justin Chen wrote:
>>> + const: 2
>>> + description:
>>> + The first cell is channel type and second cell is shared memory slot
>>> +
>>> + brcm,mbox_tx:
>>
>> No underscores. See DTS coding style.
>>
>
> Acked. I already had this fixed in the driver, but not in the doc. Woops!
So this did not even work and you did not test DTS.
Where is the DTS?
>
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description: Mailbox transmit doorbell
>>
>> Why is this needed in DT? How many instances do you have in one SoC?
>> Where is the SoC DTS?
>>
>
> We have 3 possible instances in our current SoC. We currently only
> implement one. arm,scmi. But more will come in the future. I'll put a
> sample arm,scmi node as an example consumer in v2.
No. Post your DTS instead.
>
>>> +
>>> + brcm,mbox_rx:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description: Mailbox receive doorbell
>>> +
>>> + brcm,mbox_shmem:
>>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>>> + maxItems: 2
>>> + description: Mailbox shared memory region and size
>>
>> No, use existing properties, e.g. memory region.
>>
>
> This is a region from the on chip memory. I will rename to be clear. It
memory? so reserved region is for what? Not memory?
If this is memory, then reserved region. If this is not memory, but
MMIO, then you have reg for that.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-03-29 4:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:16 [PATCH 0/2] mailbox: Add support for bcm74110 mailbox justin.chen
2025-03-27 22:16 ` [PATCH 1/2] " justin.chen
2025-03-28 7:35 ` Krzysztof Kozlowski
2025-03-27 22:16 ` [PATCH 2/2] dt-bindings: mailbox: Add devicetree binding for bcm74110 mbox justin.chen
2025-03-28 7:31 ` Krzysztof Kozlowski
2025-03-28 18:36 ` Justin Chen
2025-03-29 4:35 ` Krzysztof Kozlowski [this message]
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=5a460228-ab50-490d-a222-d6a10aea3ff0@kernel.org \
--to=krzk@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=jassisinghbrar@gmail.com \
--cc=justin.chen@broadcom.com \
--cc=krzk+dt@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