mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin <robin.toplinux@gmail.com>
To: Ming Wang <wangming01@loongson.cn>,
	Huacai Chen <chenhuacai@kernel.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] irqchip/loongson-pch-lpc: Use legacy domain for PCH-LPC IRQ controller
Date: Thu, 11 Sep 2025 17:45:38 +0800	[thread overview]
Message-ID: <61dff58f-b425-4af5-b5b9-76d9981ccbd5@gmail.com> (raw)
In-Reply-To: <20250911083546.649949-1-wangming01@loongson.cn>



On 9/11/25 16:35, Ming Wang wrote:
> On certain Loongson platforms, drivers attempting to request a legacy
> ISA IRQ directly via request_irq() (e.g., IRQ 4) may fail. The
> virtual IRQ descriptor is not fully initialized and lacks a valid irqchip.
> 
> This issue does not affect ACPI-enumerated devices described in DSDT,
> as their interrupts are properly mapped via the GSI translation path.
> This indicates the LPC irqdomain itself is functional but is not correctly
> handling direct VIRQ-to-HWIRQ mappings.
> 
> The root cause is the use of irq_domain_create_linear(). This API sets
> up a domain for dynamic, on-demand mapping, typically triggered by a GSI
> request. It does not pre-populate the mappings for the legacy VIRQ range
> (0-15). Consequently, if no ACPI device claims a specific GSI
> (e.g., GSI 4), the corresponding VIRQ (e.g., VIRQ 4) is never mapped to
> the LPC domain. A direct call to request_irq(4, ...) then fails because
> the kernel cannot resolve this VIRQ to a hardware interrupt managed by
> the LPC controller.
> 
> The PCH-LPC interrupt controller is an i8259-compatible legacy device
> that requires a deterministic, static 1-to-1 mapping for IRQs 0-15 to
> support legacy drivers.
> 
> Fix this by replacing irq_domain_create_linear() with
> irq_domain_create_legacy(). This API is specifically designed for such
> controllers. It establishes the required static 1-to-1 VIRQ-to-HWIRQ
> mapping for the entire legacy range (0-15) immediately upon domain
> creation. This ensures that any VIRQ in this range is always resolvable,
> making direct calls to request_irq() for legacy IRQs function correctly.
> 
> Signed-off-by: Ming Wang <wangming01@loongson.cn>

I have tested this patch on a Loongson 3A6000 platform.

Tested-by: Robin <robin.toplinux@gmail.com>

> 
> ---
> Changes in v2:
>    - Address review comments from Huacai Chen.
>    - Fix function call indentation style.
> ---
>   drivers/irqchip/irq-loongson-pch-lpc.c | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-loongson-pch-lpc.c b/drivers/irqchip/irq-loongson-pch-lpc.c
> index 2d4c3ec128b8..01fe4325ff84 100644
> --- a/drivers/irqchip/irq-loongson-pch-lpc.c
> +++ b/drivers/irqchip/irq-loongson-pch-lpc.c
> @@ -200,8 +200,13 @@ int __init pch_lpc_acpi_init(struct irq_domain *parent,
>   		goto iounmap_base;
>   	}
>   
> -	priv->lpc_domain = irq_domain_create_linear(irq_handle, LPC_COUNT,
> -					&pch_lpc_domain_ops, priv);
> +	/*
> +	 * The LPC interrupt controller is a legacy i8259-compatible device,
> +	 * which requires a static 1:1 mapping for IRQs 0-15.
> +	 * Use irq_domain_create_legacy() to establish this static mapping early.
> +	 */
> +	priv->lpc_domain = irq_domain_create_legacy(irq_handle, LPC_COUNT, 0, 0,
> +						    &pch_lpc_domain_ops, priv);
>   	if (!priv->lpc_domain) {
>   		pr_err("Failed to create IRQ domain\n");
>   		goto free_irq_handle;


      parent reply	other threads:[~2025-09-11  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  8:35 Ming Wang
2025-09-11  8:42 ` Huacai Chen
2025-09-11  9:45 ` Robin [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=61dff58f-b425-4af5-b5b9-76d9981ccbd5@gmail.com \
    --to=robin.toplinux@gmail.com \
    --cc=chenhuacai@kernel.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wangming01@loongson.cn \
    /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®