From: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
To: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
jassisinghbrar@gmail.com, shawnguo@kernel.org,
s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V2 0/2] mailbox: imx: support RST channel
Date: Wed, 15 Jun 2022 21:00:07 +0800 [thread overview]
Message-ID: <20220615130009.1457986-1-peng.fan@oss.nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V2:
Add R-b tag
Missed to add mailbox maintainer in V1, add in V2
To i.MX generic MU, when linux stop remote core, the MU-B side is not
reset because of hardware design, so MU-B contains valid configuration
when remote core stops. Then when linux start remote core again, linux
may notify remote core before remote core is ready for incoming message.
So we need make sure MU is in reset state before remote core start. So
add a RST channel which is only to reset MU when shutdown the RST mbox
channel.
Peng Fan (2):
dt-bindings: mailbox: imx-mu: add RST channel
mailbox: imx: support RST channel
.../devicetree/bindings/mailbox/fsl,mu.yaml | 6 ++--
drivers/mailbox/imx-mailbox.c | 29 +++++++++++++++----
2 files changed, 27 insertions(+), 8 deletions(-)
--
2.25.1
next reply other threads:[~2022-06-15 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 13:00 Peng Fan (OSS) [this message]
2022-06-15 13:00 ` [PATCH V2 1/2] dt-bindings: mailbox: imx-mu: add RST channel Peng Fan (OSS)
2022-06-15 13:00 ` [PATCH V2 2/2] mailbox: imx: support " Peng Fan (OSS)
2022-08-24 9:36 ` Liu Ying
2022-08-29 0:41 ` Peng Fan
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=20220615130009.1457986-1-peng.fan@oss.nxp.com \
--to=peng.fan@oss.nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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).