From: peng.fan@nxp.com
To: shawnguo@kernel.org, s.hauer@pengutronix.de,
jassisinghbrar@gmail.com, o.rempel@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
Anson.Huang@nxp.com, leonard.crestez@nxp.com,
aisheng.dong@nxp.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V4 0/4] mailbox/firmware: imx: support SCU channel type
Date: Tue, 3 Mar 2020 09:52:56 +0800 [thread overview]
Message-ID: <1583200380-15623-1-git-send-email-peng.fan@nxp.com> (raw)
From: Peng Fan <peng.fan@nxp.com>
V4:
Drop IMX_MU_TYPE_[GENERIC, SCU]
Pack MU chans init to separate function
Add separate function for SCU chans init and xlate
Add santity check to msg hdr.size
Limit SCU MU chans to 6, TX0/RX0/RXDB[0-3]
V3:
Rebase to Shawn's for-next
Include fsl,imx8-mu-scu compatible
Per Oleksij's comments, introduce generic tx/rx and added scu mu type
Check fsl,imx8-mu-scu in firmware driver for fast_ipc
V2:
Drop patch 1/3 which added fsl,scu property
Force to use scu channel type when machine has node compatible "fsl,imx-scu"
Force imx-scu to use fast_ipc
I not found a generic method to make SCFW message generic enough, SCFW
message is not fixed length including TX and RX. And it use TR0/RR0
interrupt.
V1:
Sorry to bind the mailbox/firmware patch together. This is make it
to understand what changed to support using 1 TX and 1 RX channel
for SCFW message.
Per i.MX8QXP Reference mannual, there are several message using
examples. One of them is:
Passing short messages: Transmit register(s) can be used to pass
short messages from one to four words in length. For example,
when a four-word message is desired, only one of the registers
needs to have its corresponding interrupt enable bit set at the
receiver side.
This patchset is to using this for SCFW message to replace four TX
and four RX method.
Peng Fan (4):
dt-bindings: mailbox: imx-mu: add SCU MU support
mailbox: imx: restructure code to make easy for new MU
mailbox: imx: add SCU MU support
firmware: imx-scu: Support one TX and one RX
.../devicetree/bindings/mailbox/fsl,mu.txt | 2 +
drivers/firmware/imx/imx-scu.c | 54 ++++-
drivers/mailbox/imx-mailbox.c | 253 +++++++++++++++++----
3 files changed, 249 insertions(+), 60 deletions(-)
base-commit: 770fbb32d34e5d6298cc2be590c9d2fd6069aa17
--
2.16.4
next reply other threads:[~2020-03-03 1:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 1:52 peng.fan [this message]
2020-03-03 1:52 ` [PATCH V4 1/4] dt-bindings: mailbox: imx-mu: add SCU MU support peng.fan
2020-03-03 1:52 ` [PATCH V4 2/4] mailbox: imx: restructure code to make easy for new MU peng.fan
2020-03-03 6:13 ` Oleksij Rempel
2020-03-03 6:27 ` Peng Fan
2020-03-03 6:47 ` Oleksij Rempel
2020-03-03 1:52 ` [PATCH V4 3/4] mailbox: imx: add SCU MU support peng.fan
2020-03-03 6:46 ` Oleksij Rempel
2020-03-03 6:53 ` Peng Fan
2020-03-03 1:53 ` [PATCH V4 4/4] firmware: imx-scu: Support one TX and one RX 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=1583200380-15623-1-git-send-email-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=Anson.Huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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).