From: Peng Fan <peng.fan@nxp.com> To: Peng Fan <peng.fan@nxp.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>, "o.rempel@pengutronix.de" <o.rempel@pengutronix.de>, Leonard Crestez <leonard.crestez@nxp.com> Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>, "festevam@gmail.com" <festevam@gmail.com>, dl-linux-imx <linux-imx@nxp.com>, Anson Huang <anson.huang@nxp.com>, Aisheng Dong <aisheng.dong@nxp.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org> Subject: RE: [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type Date: Tue, 31 Mar 2020 13:34:41 +0000 [thread overview] Message-ID: <AM0PR04MB44812577EF272CA1D457A1F788C80@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw) In-Reply-To: <1584604193-2945-1-git-send-email-peng.fan@nxp.com> Hi Jassi, > Subject: [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type Are you ok with the mailbox part? Thanks, Peng. > > From: Peng Fan <peng.fan@nxp.com> > > V7: > Per Leonard's comments, added check for TE/RE Passed test from > Leonard's https://github.com/cdleonard/imx-scu-test > > V6: > Add Oleksij's R-b tag > Patch 3/4, per > https://www.kernel.org/doc/Documentation/printk-formats.txt > should use %zu for printk sizeof > > V5: > Move imx_mu_dcfg below imx_mu_priv > Add init hooks to imx_mu_dcfg > drop __packed __aligned > Add more debug msg > code style cleanup > > 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 | 288 > +++++++++++++++++---- > 3 files changed, 281 insertions(+), 63 deletions(-) > > > base-commit: e506dba69a5e9aaff20fd73a108639f84e2c39d9 > -- > 2.16.4
WARNING: multiple messages have this Message-ID (diff)
From: Peng Fan <peng.fan@nxp.com> To: Peng Fan <peng.fan@nxp.com>, "shawnguo@kernel.org" <shawnguo@kernel.org>, "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>, "jassisinghbrar@gmail.com" <jassisinghbrar@gmail.com>, "o.rempel@pengutronix.de" <o.rempel@pengutronix.de>, Leonard Crestez <leonard.crestez@nxp.com> Cc: Aisheng Dong <aisheng.dong@nxp.com>, Anson Huang <anson.huang@nxp.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, dl-linux-imx <linux-imx@nxp.com>, "kernel@pengutronix.de" <kernel@pengutronix.de>, "festevam@gmail.com" <festevam@gmail.com>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org> Subject: RE: [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type Date: Tue, 31 Mar 2020 13:34:41 +0000 [thread overview] Message-ID: <AM0PR04MB44812577EF272CA1D457A1F788C80@AM0PR04MB4481.eurprd04.prod.outlook.com> (raw) In-Reply-To: <1584604193-2945-1-git-send-email-peng.fan@nxp.com> Hi Jassi, > Subject: [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type Are you ok with the mailbox part? Thanks, Peng. > > From: Peng Fan <peng.fan@nxp.com> > > V7: > Per Leonard's comments, added check for TE/RE Passed test from > Leonard's https://github.com/cdleonard/imx-scu-test > > V6: > Add Oleksij's R-b tag > Patch 3/4, per > https://www.kernel.org/doc/Documentation/printk-formats.txt > should use %zu for printk sizeof > > V5: > Move imx_mu_dcfg below imx_mu_priv > Add init hooks to imx_mu_dcfg > drop __packed __aligned > Add more debug msg > code style cleanup > > 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 | 288 > +++++++++++++++++---- > 3 files changed, 281 insertions(+), 63 deletions(-) > > > base-commit: e506dba69a5e9aaff20fd73a108639f84e2c39d9 > -- > 2.16.4 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-31 13:34 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-19 7:49 [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type peng.fan 2020-03-19 7:49 ` peng.fan 2020-03-19 7:49 ` [PATCH V7 1/4] dt-bindings: mailbox: imx-mu: add SCU MU support peng.fan 2020-03-19 7:49 ` peng.fan 2020-03-19 7:49 ` [PATCH V7 2/4] mailbox: imx: restructure code to make easy for new MU peng.fan 2020-03-19 7:49 ` peng.fan 2020-03-19 7:49 ` [PATCH V7 3/4] mailbox: imx: add SCU MU support peng.fan 2020-03-19 7:49 ` peng.fan 2020-03-20 13:36 ` Oleksij Rempel 2020-03-20 13:36 ` Oleksij Rempel 2020-03-19 7:49 ` [PATCH V7 4/4] firmware: imx-scu: Support one TX and one RX peng.fan 2020-03-19 7:49 ` peng.fan 2020-04-20 14:46 ` Shawn Guo 2020-04-20 14:46 ` Shawn Guo 2020-03-31 13:34 ` Peng Fan [this message] 2020-03-31 13:34 ` [PATCH V7 0/4] mailbox/firmware: imx: support SCU channel type Peng Fan 2020-04-01 4:23 ` Jassi Brar 2020-04-01 4:23 ` Jassi Brar 2020-04-01 5:42 ` Peng Fan 2020-04-01 5:42 ` 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=AM0PR04MB44812577EF272CA1D457A1F788C80@AM0PR04MB4481.eurprd04.prod.outlook.com \ --to=peng.fan@nxp.com \ --cc=aisheng.dong@nxp.com \ --cc=anson.huang@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.