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>,
"patches\@apm.com" <patches@apm.com>,
Vinayak Kale <vkale@apm.com>
Subject: Re: [PATCH V4] gic: preserve gic V2 bypass bits in cpu ctrl register
Date: Wed, 07 May 2014 10:37:26 +0100 [thread overview]
Message-ID: <877g5yorop.fsf@approximate.cambridge.arm.com> (raw)
In-Reply-To: <1399424025-4199-1-git-send-email-fkan@apm.com> (Feng Kan's message of "Wed, 7 May 2014 01:53:45 +0100")
On Wed, May 07 2014 at 1:53:45 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
bootloader
> v2 bypass group bits. In the X-Gene platform (as well others), the
Which other platform? It'd be interesting to know which one, as you're
implying they haven't managed to boot a mainline kernel so far...
> bypass functionality is not generally used and bypass bits should not
> be changed by the kernel gic code as it could lead to incorrect behavior.
> Tested on X-Gene mustang board.
>
> Signed-off-by: Vinayak Kale <vkale@apm.com>
> Acked-by: Anup Patel <apatel@apm.com>
> Signed-off-by: Feng Kan <fkan@apm.com>
> ---
> V4: Change to use bypass mask, change to use more suitable variable name.
> V3: Fix code not touch other bits other than bypass bits.
>
> drivers/irqchip/irq-gic.c | 20 +++++++++++++++++---
> 1 files changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index 4300b66..50a7bb2 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -97,6 +97,8 @@ struct irq_chip gic_arch_extn = {
> #define MAX_GIC_NR 1
> #endif
>
> +#define GIC_BYPASS_MASK 0x1e0
> +
> static struct gic_chip_data gic_data[MAX_GIC_NR] __read_mostly;
>
> #ifdef CONFIG_GIC_NON_BANKED
> @@ -418,6 +420,7 @@ static void gic_cpu_init(struct gic_chip_data *gic)
> void __iomem *dist_base = gic_data_dist_base(gic);
> void __iomem *base = gic_data_cpu_base(gic);
> unsigned int cpu_mask, cpu = smp_processor_id();
> + unsigned int bypass;
Please use a type that corresponds to the width of the access (u32 in
this case).
> int i;
>
> /*
> @@ -449,13 +452,20 @@ 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);
> +
> + bypass = readl(base + GIC_CPU_CTRL);
> + bypass &= GIC_BYPASS_MASK;
> + writel_relaxed(bypass | 0x1, base + GIC_CPU_CTRL);
> }
>
> 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);
> + unsigned int bypass;
> +
> + bypass = readl(cpu_base + GIC_CPU_CTRL);
> + bypass &= GIC_BYPASS_MASK;
> + writel_relaxed(bypass, cpu_base + GIC_CPU_CTRL);
> }
>
> #ifdef CONFIG_CPU_PM
> @@ -566,6 +576,7 @@ static void gic_cpu_restore(unsigned int gic_nr)
> {
> int i;
> u32 *ptr;
> + unsigned int bypass;
> void __iomem *dist_base;
> void __iomem *cpu_base;
>
> @@ -590,7 +601,10 @@ 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);
> +
> + bypass = readl(cpu_base + GIC_CPU_CTRL);
> + bypass &= GIC_BYPASS_MASK;
> + writel_relaxed(bypass | 0x1, cpu_base + GIC_CPU_CTRL);
It would be good to turn these into a static function (gic_cpu_if_up,
matching gic_cpu_if_down?), and use it in both gic_cpu_init and
gic_cpu_restore.
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2014-05-07 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 0:53 [PATCH V4] gic: preserve gic V2 bypass bits in cpu ctrl register Feng Kan
2014-05-07 9:37 ` Marc Zyngier [this message]
2014-05-07 23:59 ` Feng Kan
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=877g5yorop.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=patches@apm.com \
--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