All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrianhoyin.ng@altera.com
To: maz@kernel.org, tglx@linutronix.de, catalin.marinas@arm.com,
	will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: adrianhoyin.ng@altera.com
Subject: [PATCH v2 0/1] irqchip/gic-v3: Add Altera Agilex5 address bus
Date: Fri,  4 Jul 2025 16:49:49 +0800	[thread overview]
Message-ID: <cover.1751618484.git.adrianhoyin.ng@altera.com> (raw)

From: Adrian Ng Ho Yin <adrianhoyin.ng@altera.com>

Agilex5 address bus width for the ACE-lite interface is only 32 bits.
Hence the GIC600 SoC integration for Agilex5 can only access the first
32bit of the physical address space.

Add quirk to configure the gfp flag to allocate memory within 32bit
addressable range. As the 0x0201743b GIC600 ID is not specific to
Altera, of_machine_is_compatible() is added.

Add config in arm64 Kconfig to enable quirk.

change log:
v2: - Reworked implementation to reuse existing infrastructure as
      requested by Marc Zyngier.

    - Add new config in arm64 Kconfig to enable quirk.

    - Dropped dt and binding changes.
---
v1: - https://lore.kernel.org/all/cover.1747368554.git.adrianhoyin.ng@altera.com/

Adrian Ng Ho Yin (1):
  irqchip/gic-v3: Add Altera Agilex5 address bus width limitation
    workaround

 arch/arm64/Kconfig               | 10 ++++++++++
 drivers/irqchip/irq-gic-v3-its.c | 18 ++++++++++++++++++
 2 files changed, 28 insertions(+)

-- 
2.49.GIT



             reply	other threads:[~2025-07-04 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-04  8:49 adrianhoyin.ng [this message]
2025-07-04  8:49 ` [PATCH v2 1/1] irqchip/gic-v3: Add Altera Agilex5 address bus width limitation workaround adrianhoyin.ng
2025-07-04 11:29   ` Marc Zyngier

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=cover.1751618484.git.adrianhoyin.ng@altera.com \
    --to=adrianhoyin.ng@altera.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.