From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: jassisinghbrar@gmail.com, robh+dt@kernel.org, shawnguo@kernel.org
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
krzysztof.kozlowski@canonical.com, daniel.baluta@nxp.com,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V3 0/5] mailbox: imx: support i.MX93
Date: Fri, 11 Feb 2022 14:02:56 +0800 [thread overview]
Message-ID: <20220211060301.1852772-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V3:
Add R-b for 1/5 2/5
Split V2 patch 4/4 into two patch 4/5, patch 5/5
V2:
Fix dt bindings in patch 1/4 2/4
Squash author/copyright patch into patch 4/4
Based on: https://lkml.org/lkml/2022/2/6/304
Add i.MX93 Generic MU and S4 MU support
i.MX93 S4 MU has some changes compared with i.MX8ULP S4 MU, it
has two interrupts, tx/rx, so also update dt binding doc.
Peng Fan (5):
dt-bindings: mailbox: imx-mu: add i.MX93 MU
dt-bindings: mailbox: imx-mu: add i.MX93 S4 MU support
mailbox: imx: extend irq to an array
mailbox: imx: support dual interrupts
mailbox: imx: support i.MX93 S401 MU
.../devicetree/bindings/mailbox/fsl,mu.yaml | 24 +++++++++
drivers/mailbox/imx-mailbox.c | 53 +++++++++++++++----
2 files changed, 66 insertions(+), 11 deletions(-)
--
2.25.1
next reply other threads:[~2022-02-11 6:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 6:02 Peng Fan (OSS) [this message]
2022-02-11 6:02 ` [PATCH V3 1/5] dt-bindings: mailbox: imx-mu: add i.MX93 MU Peng Fan (OSS)
2022-02-17 23:21 ` Rob Herring
2022-02-11 6:02 ` [PATCH V3 2/5] dt-bindings: mailbox: imx-mu: add i.MX93 S4 MU support Peng Fan (OSS)
2022-02-17 23:23 ` Rob Herring
2022-02-11 6:02 ` [PATCH V3 3/5] mailbox: imx: extend irq to an array Peng Fan (OSS)
2022-02-11 6:03 ` [PATCH V3 4/5] mailbox: imx: support dual interrupts Peng Fan (OSS)
2022-02-11 6:03 ` [PATCH V3 5/5] mailbox: imx: support i.MX93 S401 MU Peng Fan (OSS)
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=20220211060301.1852772-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).