From: Marc Zyngier <marc.zyngier@arm.com>
To: Feng Kan <fkan@apm.com>
Cc: "tglx\@linutronix.de" <tglx@linutronix.de>,
"patches\@apm.com" <patches@apm.com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vinayak Kale <vkale@apm.com>
Subject: Re: [PATCH V2] irqchip:gic: change access of gicc_ctrl register to read modify write.
Date: Thu, 27 Feb 2014 21:29:30 +0000 [thread overview]
Message-ID: <87wqggmeh1.fsf@sofa.wild-wind.fr.eu.org> (raw)
In-Reply-To: <CAL85gmDk0hxaVbSbqTaVeVFsY4Xt1aKrBx=Pm57g0m0d_Qw-KQ@mail.gmail.com> (Feng Kan's message of "Thu, 27 Feb 2014 21:00:07 +0000")
On Thu, Feb 27 2014 at 9:00:07 pm GMT, Feng Kan <fkan@apm.com> wrote:
> On Thu, Feb 27, 2014 at 10:54 AM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> On Thu, Feb 27 2014 at 6:34:55 pm GMT, Feng Kan <fkan@apm.com> wrote:
>>> This change is made to preserve the GIC v2 releated bits in the
>>> GIC_CPU_CTRL register (also known as the GICC_CTLR register in spec).
>>> The original code only set the enable/disable group bit in this register.
>>> This code will preserve the bypass bits configured by the bootload except
>>> the enable/disable bit. The main reason for this change is to allow the
>>> bypass bits specified in the v2 spec to remain untouched by the current
>>> GIC code. In the X-Gene platform, the bypass functionality is not used
>>> and bypass must be disabled at all time.
>>>
>>> Signed-off-by: Vinayak Kale <vkale@apm.com>
>>> Acked-by: Anup Patel <apatel@apm.com>
>>> Signed-off-by: Feng Kan <fkan@apm.com>
>>> ---
>>> V2 Changes:
>>> - only mask off v2 bypass bits
>>>
>>> drivers/irqchip/irq-gic.c | 22 +++++++++++++++++++---
>>> 1 files changed, 19 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
>>> index 341c601..757581b 100644
>>> --- a/drivers/irqchip/irq-gic.c
>>> +++ b/drivers/irqchip/irq-gic.c
>>> @@ -418,6 +418,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 ctrl_mask;
>>> int i;
>>>
>>> /*
>>> @@ -449,13 +450,24 @@ 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);
>>> +
>>> + ctrl_mask = readl(base + GIC_CPU_CTRL);
>>> + ctrl_mask |= 0x1;
>>> + writel_relaxed(ctrl_mask, base + GIC_CPU_CTRL);
>>
>> I think I'm quickly loosing the will to live, or at least to review this
>> patch any further.
> Hang in there Marc, though I had nothing to do with the flood in England. Maybe
> I can instill a bit more will for you to live.
I'll probably survive without your help. In the meantime, if you want
that patch to make it in the tree, you'd better fix it.
M.
--
AAAFNRAA
prev parent reply other threads:[~2014-02-27 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:34 Feng Kan
2014-02-27 18:54 ` Marc Zyngier
2014-02-27 21:00 ` Feng Kan
2014-02-27 21:29 ` 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=87wqggmeh1.fsf@sofa.wild-wind.fr.eu.org \
--to=marc.zyngier@arm.com \
--cc=fkan@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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
all inboxes | Powered by JetHome®