From: Marc Zyngier <maz@kernel.org>
To: "Colin King (gmail)" <colin.i.king@gmail.com>,
Frank Li <Frank.Li@nxp.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: irqchip: Add IMX MU MSI controller driver
Date: Tue, 04 Oct 2022 20:44:27 +0100 [thread overview]
Message-ID: <868rlv8jc4.wl-maz@kernel.org> (raw)
In-Reply-To: <e5992130-ce33-9377-e3f3-9bfdb240f9b8@gmail.com>
On Tue, 04 Oct 2022 20:37:46 +0100,
"Colin King (gmail)" <colin.i.king@gmail.com> wrote:
>
> Hi,
>
> Static analysis with clang scan-build detected an issue with the
> following commit in linux-next:
>
> commit 70afdab904d2d1e68bffe75fe08e7e48e0b0ff8e
> Author: Frank Li <Frank.Li@nxp.com>
> Date: Thu Sep 22 11:12:43 2022 -0500
>
> irqchip: Add IMX MU MSI controller driver
>
> The issue is as follows in source drivers/irqchip/irq-imx-mu-msi.c :
>
>
> static const struct imx_mu_dcfg imx_mu_cfg_imx8ulp = {
> .type = IMX_MU_V2,
> .xTR = 0x200,
> .xRR = 0x280,
> .xSR = {
> [IMX_MU_SR] = 0xC,
> [IMX_MU_GSR] = 0x118,
> [IMX_MU_GSR] = 0x124, /* <--- issue here */
> [IMX_MU_RSR] = 0x12C,
> },
> .xCR = {
> [IMX_MU_GIER] = 0x110,
> [IMX_MU_GCR] = 0x114,
> [IMX_MU_TCR] = 0x120,
> [IMX_MU_RCR] = 0x128
> },
> };
>
> The .xSR object with index IMX_MU_GSR is being set twice, once with
> 0x118 and again with 0x128. I believe the first one should be
> IMX_MU_TSR but w/o the datasheet I don't want to make any assumptions.
Huh, nice catch.
Frank, can you please provide a fix for this ASAP?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-10-04 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 19:37 irqchip: Add IMX MU MSI controller driver Colin King (gmail)
2022-10-04 19:44 ` Marc Zyngier [this message]
2022-10-04 19:49 ` [EXT] " Frank Li
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=868rlv8jc4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=colin.i.king@gmail.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/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 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.