From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] irqchip: irq-gic: forward SGI to itself for cortex-a7 single core
Date: Mon, 8 Aug 2016 14:39:35 +0100 [thread overview]
Message-ID: <20160808143935.2d946210@arm.com> (raw)
In-Reply-To: <1470642594-30455-1-git-send-email-peter.chen@nxp.com>
On Mon, 8 Aug 2016 15:49:54 +0800
Peter Chen <peter.chen@nxp.com> wrote:
+Tony
> According to Cortex-A7 MPCore TRM, ch8.3.1, Distributor register summary,
> GICD_ITARGETSRn:
>
> The register that contains the SGI and PPI interrupts is
> read-only and the value is implementation defined. For
> Cortex-A7 configurations with only one processor, these
> registers are RAZ/WI.
>
> So, the GICD_ITARGETSR[0..7] is read-only, and the value is 0 for
> cortex-a7 single core platform if the SoC is cortex-a7 mpcore version.
> So the cupmask from gic_get_cpumask is 0.
>
> At ARM Generic Interrupt Controller Architecture version 2.0,
> ch4.3.15 Software Generated Interrupt Register, GICD_SGIR,
> The distributor will process the requested SGI according to
> register TargetListFilter and CPUTargetList. At current gic code,
> it takes TargetListFilter as 0b00, and forward the interrupt to
> cpumask (variable map at gic_raise_softirq) getting from gic_get_cpumask.
> but cpumask is 0 according to above explanation for cortex-a7 single core
> platform, so, both TargetListFilter and CPUTargetList are 0, and the
> distributor does not forward the interrupt to any CPU interface according
> to gic documentation, then the SGI can't be occurred.
>
> We have found this problem at nxp imx6ul platform, which is a cortex-a7
> single core platform, the irq work (triggered by SGI at ARM) can't be
> occurred which is needed for cpufreq, then the system has failed to boot
> and reboot [1].
I'm really not keep on this, as even if we paper over the problem for
platforms using a GIC, we still leave behind all the platform that are
not capable of self-IPI (which is the vast majority of ARM UP systems).
Can you please provide a backtrace of the failing use case? Have you
tried this patch [1], which did solve the issue for OMAP?
Also, if we're going to mandate a self-IPI mechanism for all UP
systems, we do need way to do this in a generic way, as a fallback for
systems that are not SMP aware.
Thanks,
M.
[1]: https://patchwork.kernel.org/patch/8318231/
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2016-08-08 13:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 7:49 [PATCH 1/1] irqchip: irq-gic: forward SGI to itself for cortex-a7 single core Peter Chen
2016-08-08 10:50 ` Mark Rutland
2016-08-08 12:00 ` Peter Chen
2016-08-08 13:07 ` Mark Rutland
2016-08-08 13:28 ` Peter Chen
2016-08-08 13:48 ` Mark Rutland
2016-08-08 13:59 ` Marc Zyngier
2016-08-09 3:46 ` Peter Chen
2016-08-09 5:34 ` Marc Zyngier
2016-08-09 5:57 ` Peter Chen
2016-08-09 6:59 ` Marc Zyngier
2016-08-09 7:18 ` Peter Chen
2016-08-09 8:54 ` Marc Zyngier
2016-08-09 9:39 ` Peter Chen
2016-08-09 10:08 ` Marc Zyngier
2016-08-09 11:50 ` Peter Chen
2016-08-09 13:03 ` Fabio Estevam
2016-08-16 16:29 ` Fabio Estevam
2016-08-16 16:48 ` Marc Zyngier
2016-08-16 17:03 ` Fabio Estevam
2016-08-16 18:09 ` Fabio Estevam
2016-08-09 9:30 ` Russell King - ARM Linux
2016-08-08 13:39 ` Marc Zyngier [this message]
2016-08-09 3:16 ` Peter Chen
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=20160808143935.2d946210@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).