From: Rob Herring <robh@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>
Cc: Eddie James <eajames@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] irqchip/aspeed-scu-ic: Add support for AST2700 SCU interrupt controllers
Date: Tue, 5 Aug 2025 10:39:08 -0500 [thread overview]
Message-ID: <20250805153908.GA1807801-robh@kernel.org> (raw)
In-Reply-To: <20250804053445.1482749-3-ryan_chen@aspeedtech.com>
On Mon, Aug 04, 2025 at 01:34:45PM +0800, Ryan Chen wrote:
> The AST2700 SoC follows the multi-instance interrupt controller architecture
> introduced in the AST2600, where each SCU interrupt group (IC0–IC3) is treated
> as an independent interrupt domain.
>
> Unlike the AST2600, which uses a combined register for interrupt enable and
> status bits, the AST2700 separates these into distinct registers: one for
> interrupt enable (IER) and another for interrupt status (ISR). This architectural
> change requires explicit handling of split registers for interrupt control.
>
> - Register definitions and configuration for AST2700 SCU IC instances
> (compatible: aspeed,ast2700-scu-ic0/1/2/3)
> - Initialization logic for handling split IER/ISR registers
> - Chained IRQ handling and mask/unmask logic
> - Table-driven registration using IRQCHIP_DECLARE per compatible
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> drivers/irqchip/irq-aspeed-scu-ic.c | 240 ++++++++++++++++++++++------
> 1 file changed, 195 insertions(+), 45 deletions(-)
>
> diff --git a/drivers/irqchip/irq-aspeed-scu-ic.c b/drivers/irqchip/irq-aspeed-scu-ic.c
> index 1c7045467c48..b6f3ba269c5b 100644
> --- a/drivers/irqchip/irq-aspeed-scu-ic.c
> +++ b/drivers/irqchip/irq-aspeed-scu-ic.c
> @@ -1,6 +1,6 @@
> // SPDX-License-Identifier: GPL-2.0-or-later
> /*
> - * Aspeed AST24XX, AST25XX, and AST26XX SCU Interrupt Controller
> + * Aspeed AST24XX, AST25XX, AST26XX, AST27XX SCU Interrupt Controller
> * Copyright 2019 IBM Corporation
> *
> * Eddie James <eajames@linux.ibm.com>
> @@ -34,11 +34,42 @@
> GENMASK(5, ASPEED_AST2600_SCU_IC1_SHIFT)
> #define ASPEED_AST2600_SCU_IC1_NUM_IRQS 2
>
> +#define ASPEED_AST2700_SCU_IC0_EN_REG 0x1d0
> +#define ASPEED_AST2700_SCU_IC0_STS_REG 0x1d4
> +#define ASPEED_AST2700_SCU_IC0_SHIFT 0
> +#define ASPEED_AST2700_SCU_IC0_ENABLE \
> + GENMASK(3, ASPEED_AST2700_SCU_IC0_SHIFT)
> +#define ASPEED_AST2700_SCU_IC0_NUM_IRQS 4
> +
> +#define ASPEED_AST2700_SCU_IC1_EN_REG 0x1e0
> +#define ASPEED_AST2700_SCU_IC1_STS_REG 0x1e4
> +#define ASPEED_AST2700_SCU_IC1_SHIFT 0
> +#define ASPEED_AST2700_SCU_IC1_ENABLE \
> + GENMASK(3, ASPEED_AST2700_SCU_IC1_SHIFT)
> +#define ASPEED_AST2700_SCU_IC1_NUM_IRQS 4
> +
> +#define ASPEED_AST2700_SCU_IC2_EN_REG 0x104
> +#define ASPEED_AST2700_SCU_IC2_STS_REG 0x100
> +#define ASPEED_AST2700_SCU_IC2_SHIFT 0
> +#define ASPEED_AST2700_SCU_IC2_ENABLE \
> + GENMASK(3, ASPEED_AST2700_SCU_IC2_SHIFT)
> +#define ASPEED_AST2700_SCU_IC2_NUM_IRQS 4
> +
> +#define ASPEED_AST2700_SCU_IC3_EN_REG 0x10c
> +#define ASPEED_AST2700_SCU_IC3_STS_REG 0x108
> +#define ASPEED_AST2700_SCU_IC3_SHIFT 0
> +#define ASPEED_AST2700_SCU_IC3_ENABLE \
> + GENMASK(1, ASPEED_AST2700_SCU_IC3_SHIFT)
> +#define ASPEED_AST2700_SCU_IC3_NUM_IRQS 2
> +
The reason for ic0/ic1 compatibles before was the enable field was
different. Now it's at least at the same shift. Do you really need a
different value for IC3?
The register addresses should come from "reg". I don't understand why
they are hardcoded in the driver.
Rob
next prev parent reply other threads:[~2025-08-05 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 5:34 [PATCH 0/2] irqchip: Add support for Aspeed AST2700 SCU interrupt controller Ryan Chen
2025-08-04 5:34 ` [PATCH 1/2] dt-bindings: interrupt-controller: aspeed: add AST2700 SCU IC compatibles Ryan Chen
2025-08-04 7:32 ` Krzysztof Kozlowski
2025-08-05 1:39 ` Ryan Chen
2025-08-04 5:34 ` [PATCH 2/2] irqchip/aspeed-scu-ic: Add support for AST2700 SCU interrupt controllers Ryan Chen
2025-08-05 7:50 ` Thomas Gleixner
2025-08-06 6:43 ` Ryan Chen
2025-08-05 15:39 ` Rob Herring [this message]
2025-08-06 7:14 ` Ryan Chen
2025-08-06 13:41 ` Eddie James
2025-08-06 14:44 ` Thomas Gleixner
2025-08-07 0:23 ` Ryan 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=20250805153908.GA1807801-robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan_chen@aspeedtech.com \
--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;
as well as URLs for NNTP newsgroup(s).