From: Marc Zyngier <maz@kernel.org>
To: Heyi Guo <guoheyi@huawei.com>
Cc: linux-kernel@vger.kernel.org, wanghaibin.wang@huawei.com,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [PATCH] irq-gic-v3-its: fix access width for gicr_syncr
Date: Tue, 25 Feb 2020 16:17:08 +0000 [thread overview]
Message-ID: <740ba8790b72a42d400cc9fc317c4dba@kernel.org> (raw)
In-Reply-To: <20200225090023.28020-1-guoheyi@huawei.com>
On 2020-02-25 09:00, Heyi Guo wrote:
> GICR_SYNCR is a 32bit register, so it is better to access it with
> 32bit access width, though we have not seen any real problem.
>
> Signed-off-by: Heyi Guo <guoheyi@huawei.com>
>
> ---
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Jason Cooper <jason@lakedaemon.net>
> ---
> drivers/irqchip/irq-gic-v3-its.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/irq-gic-v3-its.c
> b/drivers/irqchip/irq-gic-v3-its.c
> index 65a11257d220..5c6790e3bfbf 100644
> --- a/drivers/irqchip/irq-gic-v3-its.c
> +++ b/drivers/irqchip/irq-gic-v3-its.c
> @@ -1321,7 +1321,7 @@ static void lpi_write_config(struct irq_data *d,
> u8 clr, u8 set)
>
> static void wait_for_syncr(void __iomem *rdbase)
> {
> - while (gic_read_lpir(rdbase + GICR_SYNCR) & 1)
> + while (readl_relaxed(rdbase + GICR_SYNCR) & 1)
> cpu_relax();
> }
Yup, nice catch. Looks like no implementation really cares about it,
but still worth fixing.
I'll take it for 5.7.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-02-25 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 9:00 [PATCH] irq-gic-v3-its: fix access width for gicr_syncr Heyi Guo
2020-02-25 16:17 ` Marc Zyngier [this message]
2020-03-29 20:26 ` [tip: irq/core] irqchip/gic-v3-its: Fix " tip-bot2 for Heyi Guo
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=740ba8790b72a42d400cc9fc317c4dba@kernel.org \
--to=maz@kernel.org \
--cc=guoheyi@huawei.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.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 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.