From: Jammy Huang <jammy_huang@aspeedtech.com>
To: <jassisinghbrar@gmail.com>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <jammy_huang@aspeedtech.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] ASPEED: Add mailbox driver for AST2700 series
Date: Wed, 4 Jun 2025 20:55:56 +0800 [thread overview]
Message-ID: <20250604125558.1614523-1-jammy_huang@aspeedtech.com> (raw)
Add mailbox controller driver for AST27XX SoCs, which provides
independent tx/rx mailbox between different processors. There are 4
channels for each tx/rx mailbox and each channel has an 32-byte FIFO.
v2 changes:
- Update document
Jammy Huang (2):
dt-bindings: mailbox: Add ASPEED AST2700 series SoC
mailbox: aspeed: add mailbox driver for AST27XX series SoC
.../mailbox/aspeed,ast2700-mailbox.yaml | 57 +++++
drivers/mailbox/Kconfig | 8 +
drivers/mailbox/Makefile | 2 +
drivers/mailbox/ast2700-mailbox.c | 226 ++++++++++++++++++
4 files changed, 293 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mailbox/aspeed,ast2700-mailbox.yaml
create mode 100644 drivers/mailbox/ast2700-mailbox.c
base-commit: 546b1c9e93c2bb8cf5ed24e0be1c86bb089b3253
--
2.25.1
next reply other threads:[~2025-06-04 12:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 12:55 Jammy Huang [this message]
2025-06-04 12:55 ` [PATCH v2 1/2] dt-bindings: mailbox: Add ASPEED AST2700 series SoC Jammy Huang
2025-06-04 14:10 ` Krzysztof Kozlowski
2025-06-04 14:35 ` Rob Herring (Arm)
2025-06-04 15:19 ` Krzysztof Kozlowski
2025-06-05 1:44 ` Jammy Huang
2025-06-05 5:48 ` Krzysztof Kozlowski
2025-06-04 12:55 ` [PATCH v2 2/2] mailbox: aspeed: add mailbox driver for AST27XX " Jammy Huang
2025-06-04 12:57 ` [PATCH v2 0/2] ASPEED: Add mailbox driver for AST2700 series Krzysztof Kozlowski
2025-06-04 13:07 ` Jammy Huang
2025-06-04 14:10 ` Krzysztof Kozlowski
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=20250604125558.1614523-1-jammy_huang@aspeedtech.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®