From: Ryan Chen <ryan_chen@aspeedtech.com>
To: ryan_chen <ryan_chen@aspeedtech.com>,
Eddie James <eajames@linux.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
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: [PATCH 0/2] irqchip: Add support for Aspeed AST2700 SCU interrupt controller
Date: Mon, 4 Aug 2025 13:34:43 +0800 [thread overview]
Message-ID: <20250804053445.1482749-1-ryan_chen@aspeedtech.com> (raw)
This patch series adds support for the SCU (System Control Unit) interrupt
controllers found in the Aspeed AST2700 SoC.
The AST2700 integrates multiple SCU interrupt groups, architecturally
similar to those in the AST2600, but using split registers for interrupt
enable (IER) and interrupt status (ISR), whereas AST2600 uses combined
registers.
Ryan Chen (2):
dt-bindings: interrupt-controller: aspeed: add AST2700 SCU IC
compatibles
irqchip/aspeed-scu-ic: Add support for AST2700 SCU interrupt
controllers
.../aspeed,ast2500-scu-ic.yaml | 6 +-
drivers/irqchip/irq-aspeed-scu-ic.c | 240 ++++++++++++++----
2 files changed, 200 insertions(+), 46 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-04 5:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 5:34 Ryan Chen [this message]
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
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=20250804053445.1482749-1-ryan_chen@aspeedtech.com \
--to=ryan_chen@aspeedtech.com \
--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=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 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.