From: Marc Zyngier <marc.zyngier@arm.com>
To: Feng Kan <fkan@apm.com>
Cc: "tglx\@linutronix.de" <tglx@linutronix.de>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vinayak Kale <vkale@apm.com>
Subject: Re: [PATCH V5] gic: preserve gic V2 bypass bits in cpu ctrl register
Date: Thu, 08 May 2014 13:54:27 +0100 [thread overview]
Message-ID: <87ha50mnwc.fsf@approximate.cambridge.arm.com> (raw)
In-Reply-To: <1399507310-2791-1-git-send-email-fkan@apm.com> (Feng Kan's message of "Thu, 8 May 2014 01:01:50 +0100")
On Thu, May 08 2014 at 1:01:50 am BST, Feng Kan <fkan@apm.com> wrote:
> This change is made to preserve the GIC v2 bypass bits in the
> GIC_CPU_CTRL register (also known as the GICC_CTLR register in spec).
> This code will preserve all bits configured by the bootload regarding
> v2 bypass group bits. In the X-Gene platform, the bypass functionality
> is not used and bypass bits should not be changed by the kernel gic
> code as it could lead to incorrect behavior.
>
> Signed-off-by: Vinayak Kale <vkale@apm.com>
> Acked-by: Anup Patel <apatel@apm.com>
> Signed-off-by: Feng Kan <fkan@apm.com>
> ---
> V5: Use macro to replace read modify write of cpu_ctrl register.
> V4: Change to use bypass mask, change ot user more suitable variable name.
> drivers/irqchip/irq-gic.c | 16 +++++++++++++---
> 1 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index 4300b66..42e9bf4 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -97,6 +97,13 @@ struct irq_chip gic_arch_extn = {
> #define MAX_GIC_NR 1
> #endif
>
> +#define set_cpuctrl(base, val) \
> + do { \
> + u32 bypass; \
> + bypass = readl(base + GIC_CPU_CTRL) & 0x1e0; \
> + writel_relaxed(bypass | val, base + GIC_CPU_CTRL);\
> + } while (0)
> +
Please use a function. A macro doesn't buy us anything here, and lacks
type safety.
Your previous patch was nicer in that respect. You just had to move the
enable code to a gic_cpu_if_up() function, and you were done...
> static struct gic_chip_data gic_data[MAX_GIC_NR] __read_mostly;
>
> #ifdef CONFIG_GIC_NON_BANKED
> @@ -449,13 +456,15 @@ static void gic_cpu_init(struct gic_chip_data *gic)
> writel_relaxed(0xa0a0a0a0, dist_base + GIC_DIST_PRI + i * 4 / 4);
>
> writel_relaxed(0xf0, base + GIC_CPU_PRIMASK);
> - writel_relaxed(1, base + GIC_CPU_CTRL);
> +
> + set_cpuctrl(base, 1);
> }
>
> void gic_cpu_if_down(void)
> {
> void __iomem *cpu_base = gic_data_cpu_base(&gic_data[0]);
> - writel_relaxed(0, cpu_base + GIC_CPU_CTRL);
> +
> + set_cpuctrl(cpu_base, 0);
> }
>
> #ifdef CONFIG_CPU_PM
> @@ -590,7 +599,8 @@ static void gic_cpu_restore(unsigned int gic_nr)
> writel_relaxed(0xa0a0a0a0, dist_base + GIC_DIST_PRI + i * 4);
>
> writel_relaxed(0xf0, cpu_base + GIC_CPU_PRIMASK);
> - writel_relaxed(1, cpu_base + GIC_CPU_CTRL);
> +
> + set_cpuctrl(cpu_base, 1);
> }
>
> static int gic_notifier(struct notifier_block *self, unsigned long cmd, void *v)
M.
--
Jazz is not dead. It just smells funny.
prev parent reply other threads:[~2014-05-08 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 0:01 [PATCH V5] gic: preserve gic V2 bypass bits in cpu ctrl register Feng Kan
2014-05-08 12:54 ` Marc Zyngier [this message]
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=87ha50mnwc.fsf@approximate.cambridge.arm.com \
--to=marc.zyngier@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=Will.Deacon@arm.com \
--cc=fkan@apm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vkale@apm.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