From: Jammy Huang <jammy_huang@aspeedtech.com>
To: Rob Herring <robh@kernel.org>
Cc: "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>
Subject: RE: [PATCH v5 1/2] dt-bindings: mailbox: Add ASPEED AST2700 series SoC
Date: Thu, 26 Jun 2025 03:41:42 +0000 [thread overview]
Message-ID: <TYZPR06MB6568CA1AD00A1D749CD06C8BF17AA@TYZPR06MB6568.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20250625155007.GA1489062-robh@kernel.org>
> On Wed, Jun 25, 2025 at 03:34:16PM +0800, Jammy Huang wrote:
> > Introduce the mailbox module for AST27XX series SoC, which is
> > responsible for interchanging messages between asymmetric processors.
> >
> > Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
>
> You didn't add Krzysztof's Reviewed-by...
Hi Rob,
I checked submitting patches' guide, and it says that if the patch has changed
substantially in following version, these tags might not be applicable anymore
and thus should be removed. I also mentioned this in changelog on the cover.
I am not sure about this, so may I keep Krzk's Reviewed-by tag?
If it's OK, I will add it back on next patch.
>
> > ---
> > .../mailbox/aspeed,ast2700-mailbox.yaml | 60
> +++++++++++++++++++
> > 1 file changed, 60 insertions(+)
> > create mode 100644
> > Documentation/devicetree/bindings/mailbox/aspeed,ast2700-mailbox.yaml
> >
> > diff --git
> > a/Documentation/devicetree/bindings/mailbox/aspeed,ast2700-mailbox.yam
> > l
> > b/Documentation/devicetree/bindings/mailbox/aspeed,ast2700-mailbox.yam
> > l
> > new file mode 100644
> > index 000000000000..0a5f43de5f28
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mailbox/aspeed,ast2700-mailbox
> > +++ .yaml
> > @@ -0,0 +1,60 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) %YAML 1.2
> > +---
> > +$id:
> > +http://devicetree.org/schemas/mailbox/aspeed,ast2700-mailbox.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: ASPEED AST2700 mailbox controller
> > +
> > +maintainers:
> > + - Jammy Huang <jammy_huang@aspeedtech.com>
> > +
> > +description:
>
> You need '>' to preserve paragraphs.
OK
>
> > + ASPEED AST2700 has multiple processors that need to communicate
> > + with each other. The mailbox controller provides a way for these
> > + processors to send messages to each other. It is a hardware-based
> > + inter-processor communication mechanism that allows processors to
> > + send and receive messages through dedicated channels.
>
> And a blank line between paragraphs.
>
OK
> > + The mailbox's tx/rx are independent, meaning that one processor can
> > + send a message while another processor is receiving a message
> simultaneously.
> > + There are 4 channels available for both tx and rx operations. Each
> > + channel has a FIFO buffer that can hold messages of a fixed size
> > + (32 bytes in this case).
>
> And here.
>
Sure.
> > + The mailbox controller also supports interrupt generation, allowing
> > + processors to notify each other when a message is available or when
> > + an event occurs.
> > +
> > +properties:
> > + compatible:
> > + const: aspeed,ast2700-mailbox
> > +
> > + reg:
> > + maxItems: 2
> > + description:
> > + Contains the base addresses and sizes of the mailbox controller. 1st
> one
> > + is for TX control register; 2nd one is for RX control register.
>
> Instead, just:
>
> items:
> - description: TX control register
> - description: RX control register
>
Agree.
> > +
> > + interrupts:
> > + maxItems: 1
> > +
> > + "#mbox-cells":
> > + const: 1
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - interrupts
> > + - "#mbox-cells"
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + #include <dt-bindings/interrupt-controller/arm-gic.h>
> > +
> > + mailbox@12c1c200 {
> > + compatible = "aspeed,ast2700-mailbox";
> > + reg = <0x12c1c200 0x100>, <0x12c1c300 0x100>;
> > + interrupts = <GIC_SPI 103 IRQ_TYPE_LEVEL_HIGH>;
> > + #mbox-cells = <1>;
> > + };
> > --
> > 2.25.1
> >
Thanks for your help.
Regards
Jammy
next prev parent reply other threads:[~2025-06-26 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 7:34 [PATCH v5 0/2] ASPEED: Add mailbox driver for AST2700 series Jammy Huang
2025-06-25 7:34 ` [PATCH v5 1/2] dt-bindings: mailbox: Add ASPEED AST2700 series SoC Jammy Huang
2025-06-25 15:50 ` Rob Herring
2025-06-26 3:41 ` Jammy Huang [this message]
2025-06-27 1:52 ` Andrew Jeffery
2025-06-27 2:22 ` Jammy Huang
2025-06-25 7:34 ` [PATCH v5 2/2] mailbox: aspeed: add mailbox driver for AST27XX " Jammy Huang
2025-06-27 1:54 ` Andrew Jeffery
2025-06-27 2:21 ` Jammy Huang
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=TYZPR06MB6568CA1AD00A1D749CD06C8BF17AA@TYZPR06MB6568.apcprd06.prod.outlook.com \
--to=jammy_huang@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.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
all inboxes | Powered by JetHome®