From: Krzysztof Kozlowski <krzk@kernel.org>
To: Guomin chen <guomin.chen@cixtech.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, cix-kernel-upstream@cixtech.com,
Peter Chen <peter.chen@cixtech.com>,
Lihua Liu <Lihua.Liu@cixtech.com>
Subject: Re: [PATCH 1/2] dt-bindings: mailbox: cix: add device tree binding documentation.
Date: Fri, 14 Mar 2025 09:13:52 +0100 [thread overview]
Message-ID: <d0d82010-e311-4a41-a6c4-027626e408ba@kernel.org> (raw)
In-Reply-To: <Z9PkUxlQ1t5zZxuf@gchen>
On 14/03/2025 09:09, Guomin chen wrote:
>>
>>> +
>>> + This controller supports three types of unidirectional channels, they are
>>> + 1 register based channel, 1 fifo based channel and 8 fast channels.
>>> + A total of 10 channels for each controller. Following types are
>>> + supported:
>>> + channel 0_7 - Fast channel with 32bit transmit register and IRQ support.
>>> + channel 8 - Reg based channel with 32*32bit transsmit register and
>>> + Doorbell+transmit acknowledgment IRQ support
>>> + channel 9 - Fifo based channel with 32*32bit depth fifo and IRQ support.
>>> + const: 1
>>> +
>>> + cix,mbox-dir:
>>> + $ref: /schemas/types.yaml#/definitions/uint32
>>> + description: Direction of the mailbox (0:TX or 1:RX)
>>> + enum: [0, 1]
>>
>> I don't understand why do you need it. By not sending us driver patch,
>> you are not making it easier. Why would provider care how consumers use
>> the mbox channel? Maybe consumer should choose the direction?
>>
>
> As for the mbox-dir property, my driver code has already been submitted.
There is no thing in this thread, so next time be sure you use standard
submitting process, so your work will be threaded.
> On the Cixtech Soc platform, although each mbox is unidirectional,
> there are multiple mboxes—some for reading and some for writing.
So all mboxes in a controller have the same direction or not? Do you
configure it or is it defined by hardware?
> Therefore, the mbox controller has added the mbox-dir property.
>
> Consumers only need to reference the corresponding mbox controller node,
> and whether it is for reading or writing is already determined by the mbox controller,
> without needing to further understand the mbox-dir property.
Don't explain how DT works, I know. Why this property is needed in DT in
the first place?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-14 8:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 13:24 [PATCH 1/2] dt-bindings: mailbox: cix: add device tree binding documentation Guomin Chen
2025-03-13 13:28 ` Krzysztof Kozlowski
2025-03-14 8:09 ` Guomin chen
2025-03-14 8:13 ` Krzysztof Kozlowski [this message]
2025-03-14 7:25 ` Krzysztof Kozlowski
2025-03-14 8:21 ` Guomin chen
-- strict thread matches above, loose matches on Subject: below --
2025-03-13 13:22 Guomin Chen
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=d0d82010-e311-4a41-a6c4-027626e408ba@kernel.org \
--to=krzk@kernel.org \
--cc=Lihua.Liu@cixtech.com \
--cc=cix-kernel-upstream@cixtech.com \
--cc=conor+dt@kernel.org \
--cc=guomin.chen@cixtech.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.chen@cixtech.com \
--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