From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"A.s. Dong" <aisheng.dong@nxp.com>,
Jassi Brar <jassisinghbrar@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v9 4/4] mailbox: Add support for i.MX messaging unit
Date: Thu, 2 Aug 2018 11:47:03 +0200 [thread overview]
Message-ID: <df93c03d-a982-2aa4-f3eb-11caa4817dab@pengutronix.de> (raw)
In-Reply-To: <4d6931be-8caa-5168-d980-40dbe949386c@mentor.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3507 bytes --]
Hi Vladimir,
thank you for review.
Jassi, Dong, any other comments? If no, i'll send tomorrow updated version.
On 02.08.2018 09:54, Vladimir Zapolskiy wrote:
> Hi Oleksij,
>
> two more nitpickings fro my side.
>
> On 08/02/2018 10:23 AM, Oleksij Rempel wrote:
>> The i.MX Messaging Unit is a two side block which allows applications
>> implement communication over this sides.
>>
>> The MU includes the following features:
>> - Messaging control by interrupts or by polling
>> - Four general-purpose interrupt requests reflected to the other side
>> - Three general-purpose flags reflected to the other side
>> - Four receive registers with maskable interrupt
>> - Four transmit registers with maskable interrupt
>>
>> Reviewed-by: Vladimir Zapolskiy <vz@mleia.com>
>> Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
>> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
>
> [snip]
>
>> +static irqreturn_t imx_mu_isr(int irq, void *p)
>> +{
>> + struct mbox_chan *chan = p;
>> + struct imx_mu_priv *priv = to_imx_mu_priv(chan->mbox);
>> + struct imx_mu_con_priv *cp = chan->con_priv;
>> + u32 val, ctrl, dat;
>> +
>> + ctrl = imx_mu_read(priv, IMX_MU_xCR);
>> + val = imx_mu_read(priv, IMX_MU_xSR);
>> +
>> + switch (cp->type) {
>> + case IMX_MU_TYPE_TX:
>> + val &= IMX_MU_xSR_TEn(cp->idx) &
>> + (ctrl & IMX_MU_xCR_TIEn(cp->idx));
>> + break;
>> + case IMX_MU_TYPE_RX:
>> + val &= IMX_MU_xSR_RFn(cp->idx) &
>> + (ctrl & IMX_MU_xCR_RIEn(cp->idx));
>> + break;
>> + case IMX_MU_TYPE_RXDB:
>> + val &= IMX_MU_xSR_GIPn(cp->idx) &
>> + (ctrl & IMX_MU_xCR_GIEn(cp->idx));
>> + break;
>> + default:
>> + break;
>> + }
>> +
>> + if (!val) {
>> + return IRQ_NONE;
>> + } else if (val == IMX_MU_xSR_TEn(cp->idx)) {
>
> Please drop the 'else' branch above.
>
> Here you can either just start from a new 'if', or all together drop 'if (!val)'
> and return IRQ_NONE at the end of the if-else construction.
>
>> + imx_mu_xcr_rmw(priv, 0, IMX_MU_xCR_TIEn(cp->idx));
>> + mbox_chan_txdone(chan, 0);
>> + } else if (val == IMX_MU_xSR_RFn(cp->idx)) {
>> + dat = imx_mu_read(priv, IMX_MU_xRRn(cp->idx));
>> + mbox_chan_received_data(chan, (void *)&dat);
>> + } else if (val == IMX_MU_xSR_GIPn(cp->idx)) {
>> + imx_mu_write(priv, IMX_MU_xSR_GIPn(cp->idx), IMX_MU_xSR);
>> + mbox_chan_received_data(chan, NULL);
>> + } else {
>> + dev_warn_ratelimited(priv->dev, "Not handled interrupt\n");
>> + return IRQ_NONE;
>> + }
>> +
>> + return IRQ_HANDLED;
>> +}
>
> [snip]
>
>> + for (i = 0; i < IMX_MU_CHANS; i++) {
>> + struct imx_mu_con_priv *cp = &priv->con_priv[i];
>> +
>> + cp->idx = i % 4;
>> + cp->type = (i - cp->idx) >> 2;
>
> cp->type = i >> 2;
>
>> + cp->chan = &priv->mbox_chans[i];
>> + priv->mbox_chans[i].con_priv = cp;
>> + snprintf(cp->irq_desc, sizeof(cp->irq_desc),
>> + "imx_mu_chan[%i-%i]", cp->type, cp->idx);
>> + }
>> +
>> + priv->side_b = of_property_read_bool(np, "fsl,mu-side-b");
>> +
>> + spin_lock_init(&priv->xcr_lock);
>> +
>> + priv->mbox.dev = dev;
>> + priv->mbox.ops = &imx_mu_ops;
>> + priv->mbox.chans = priv->mbox_chans;
>> + priv->mbox.num_chans = IMX_MU_CHANS;
>> + priv->mbox.of_xlate = imx_mu_xlate;
>> + priv->mbox.txdone_irq = true;
>> +
>> + platform_set_drvdata(pdev, priv);
>> +
>> + imx_mu_init_generic(priv);
>> +
>> + return mbox_controller_register(&priv->mbox);
>> +}
>
> --
> Best wishes,
> Vladimir
>
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2018-08-02 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 7:23 [PATCH v9 0/4] add mailbox support for i.MX7D Oleksij Rempel
2018-08-02 7:23 ` [PATCH v9 1/4] dt-bindings: arm: fsl: add mu binding doc Oleksij Rempel
2018-08-02 7:23 ` [PATCH v9 2/4] dt-bindings: mailbox: imx-mu: add generic MU channel support Oleksij Rempel
2018-08-02 7:23 ` [PATCH v9 3/4] ARM: dts: imx7s: add i.MX7 messaging unit support Oleksij Rempel
2018-08-02 7:23 ` [PATCH v9 4/4] mailbox: Add support for i.MX messaging unit Oleksij Rempel
2018-08-02 7:54 ` Vladimir Zapolskiy
2018-08-02 9:47 ` Oleksij Rempel [this message]
2018-08-02 14:30 ` Jassi Brar
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=df93c03d-a982-2aa4-f3eb-11caa4817dab@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=jassisinghbrar@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
--cc=vladimir_zapolskiy@mentor.com \
/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).