public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: marc.zyngier@arm•com (Marc Zyngier)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/5] arm64: Allow booting with GICv3 in GICv2 mode
Date: Thu, 08 Oct 2015 17:09:20 +0100	[thread overview]
Message-ID: <56169530.9030902@arm.com> (raw)
In-Reply-To: <20151008155655.GO17192@e104818-lin.cambridge.arm.com>

On 08/10/15 16:56, Catalin Marinas wrote:
> On Fri, Oct 02, 2015 at 05:37:49PM +0100, Marc Zyngier wrote:
>> Recent evolutions of the ARM Trusted Firmware have outlined issues
>> when the system is equipped with a GICv3 interrupt controller, but the
>> firmware has decided to restrict it to GICv2 compatibility mode.
>>
>> In this mode, system registers cannot be enabled, and the firmware is
>> expected to pass a GICv2 description (DT or ACPI tables).
>>
>> This series makes sure that system register access is checked at EL2
>> setup time and when the feature detection is performed. Additionally,
>> the GICv2 driver checks that system registers are disabled, and warns
>> if they are enabled.
>>
>> The booting requirements are also updated to make the above explicit.
>>
>> Marc Zyngier (5):
>>   arm64: el2_setup: Make sure ICC_SRE_EL2.SRE sticks before using GICv3
>>     sysregs
>>   irqchip/gic-v3: Make gic_enable_sre an inline function
>>   arm64: cpufeatures: Check ICC_EL1_SRE.SRE before enabling
>>     ARM64_HAS_SYSREG_GIC_CPUIF
>>   irqchip/gic: Warn if GICv3 system registers are enabled
>>   arm64: Update booting requirements for GICv3 in GICv2 mode
>>
>>  Documentation/arm64/booting.txt    | 11 ++++++++++-
>>  arch/arm64/kernel/cpufeature.c     | 19 ++++++++++++++++++-
>>  arch/arm64/kernel/head.S           |  2 ++
>>  drivers/irqchip/irq-gic-v3.c       | 32 +++++++++-----------------------
>>  drivers/irqchip/irq-gic.c          | 15 +++++++++++++++
>>  include/linux/irqchip/arm-gic-v3.h | 16 ++++++++++++++++
>>  6 files changed, 70 insertions(+), 25 deletions(-)
> 
> Reviewed-by: Catalin Marinas <catalin.marinas@arm•com>
> 
> How do you plan to merge these patches? I'm fine for them to go via the
> irqchip maintainers since they are all GIC related.

I guess we can direct this via tip if Thomas is OK with it.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2015-10-08 16:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 16:37 [PATCH 0/5] arm64: Allow booting with GICv3 in GICv2 mode Marc Zyngier
2015-10-02 16:37 ` [PATCH 1/5] arm64: el2_setup: Make sure ICC_SRE_EL2.SRE sticks before using GICv3 sysregs Marc Zyngier
2015-10-02 16:37 ` [PATCH 2/5] irqchip/gic-v3: Make gic_enable_sre an inline function Marc Zyngier
2015-10-08 15:54   ` Catalin Marinas
2015-10-08 16:02     ` Marc Zyngier
2015-10-02 16:37 ` [PATCH 3/5] arm64: cpufeatures: Check ICC_EL1_SRE.SRE before enabling ARM64_HAS_SYSREG_GIC_CPUIF Marc Zyngier
2015-10-02 16:37 ` [PATCH 4/5] irqchip/gic: Warn if GICv3 system registers are enabled Marc Zyngier
2015-10-02 16:37 ` [PATCH 5/5] arm64: Update booting requirements for GICv3 in GICv2 mode Marc Zyngier
2015-10-08 15:56 ` [PATCH 0/5] arm64: Allow booting with " Catalin Marinas
2015-10-08 16:09   ` 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=56169530.9030902@arm.com \
    --to=marc.zyngier@arm$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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