From: Christian Bruel <christian.bruel@foss.st.com>
To: Marc Zyngier <maz@kernel.org>
Cc: <tglx@linutronix.de>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@foss.st.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH 2/3] irqchip/gic: Use 0x10000 offset to access GICC_DIR on STM32MP2
Date: Fri, 4 Apr 2025 14:15:05 +0200 [thread overview]
Message-ID: <1213dbfb-821a-4534-947b-acc4eac9da81@foss.st.com> (raw)
In-Reply-To: <8734epyw17.wl-maz@kernel.org>
On 4/3/25 19:50, Marc Zyngier wrote:
> On Thu, 03 Apr 2025 13:28:04 +0100,
> Christian Bruel <christian.bruel@foss.st.com> wrote:
>>
>> When GIC_4KNOT64K bit in the GIC configuration register is
>> 0 (64KB), address block is modified in such a way than only the
>> first 4KB of the GIC cpu interface are accessible with default
>> offsets.
>> With this bit mapping GICC_DIR register is accessible at
>> offset 0x10000 instead of 0x1000, thus remap accordingly
>
> And I'm pretty sure the whole of the GICC range is correctly
> accessible at offset 0xF000, giving you the full 8kB you need. That's
> because each page of the GIC is aliased over two 64kB blocks, as per
> the integration guidelines so that MMU isolation can be provided on a
> 64kB boundary.
Thanks a lot for this explanation, indeed this works like a charm.
>
> Funnily enough, all it takes is to adjust GICC region. You can either:
>
> - make it 128kB wide, and the driver will take care of it (details in
> gic_check_eoimode()). On one of my boxes that is similarly
> configured, I get:
>
> [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> [ 0.000000] GIC: Adjusting CPU interface base to 0x00000000780af000
> [ 0.000000] Root IRQ handler: gic_handle_irq
> [ 0.000000] GIC: Using split EOI/Deactivate mode
>
> See below for what I expect to be the correct fix.
>
> - make it 8kB wide from offset 0xF000.
I checked both and they work. I will go for the former to show real 8kB
size to be exposed in the DT. And there are a few other platforms that
use this alias
>
> Unless the ST HW folks have been even more creative, none of this
> overly complicated stuff should be necessary. Just describe the HW
> correctly.
I was unable to find this information in the GIC-400 trm
(https://developer.arm.com/documentation/ddi0471/b/programmers-model/gic-400-register-map).
Now I also prefer to use GICC alias at
offset 0xf000 as suggested rather than the quirk solution
thank you very much
Christian
>
> M.
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index f3c6cdfd7008..97b7a7106a02 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -120,7 +120,7 @@ intc: interrupt-controller@4ac00000 {
> #address-cells = <1>;
> interrupt-controller;
> reg = <0x0 0x4ac10000 0x0 0x1000>,
> - <0x0 0x4ac20000 0x0 0x2000>,
> + <0x0 0x4ac20000 0x0 0x20000>,
> <0x0 0x4ac40000 0x0 0x2000>,
> <0x0 0x4ac60000 0x0 0x2000>;
> };
>
next prev parent reply other threads:[~2025-04-04 13:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 12:28 [PATCH 0/3] Add ST STM32MP2 GICv2 quirk for EOI split mode Christian Bruel
2025-04-03 12:28 ` [PATCH 1/3] dt-bindings: interrupt-controller: arm,gic: Add st,stm32mp2-cortex-a7-gic Christian Bruel
2025-04-03 12:28 ` [PATCH 2/3] irqchip/gic: Use 0x10000 offset to access GICC_DIR on STM32MP2 Christian Bruel
2025-04-03 15:43 ` Thomas Gleixner
2025-04-04 12:25 ` Christian Bruel
2025-04-03 17:50 ` Marc Zyngier
2025-04-04 12:15 ` Christian Bruel [this message]
2025-04-04 13:36 ` Marc Zyngier
2025-04-04 16:18 ` Christian Bruel
2025-04-04 16:19 ` Christian Bruel
2025-04-03 12:28 ` [PATCH 3/3] arm64: dts: st: add st,stm32mp2-cortex-a7-gic in intc node in stm32mp251.dtsi Christian Bruel
2025-04-03 17:27 ` Marc Zyngier
2025-04-04 12:17 ` Christian Bruel
2025-04-04 12:45 ` Marc Zyngier
2025-04-03 14:35 ` [PATCH 0/3] Add ST STM32MP2 GICv2 quirk for EOI split mode Rob Herring (Arm)
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=1213dbfb-821a-4534-947b-acc4eac9da81@foss.st.com \
--to=christian.bruel@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=maz@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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®