From: Kevin Chen <kevin_chen@aspeedtech.com>
To: <tglx@linutronix.de>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <joel@jms.id.au>,
<andrew@codeconstruct.com.au>, <kevin_chen@aspeedtech.com>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-aspeed@lists.ozlabs.org>
Subject: [PATCH v4 0/2] Add support for AST2700 INTC driver
Date: Wed, 16 Oct 2024 10:24:08 +0800 [thread overview]
Message-ID: <20241016022410.1154574-1-kevin_chen@aspeedtech.com> (raw)
---
v4:
aspeed,ast2700-intc.yaml:
- Add |' to preserve formatting.
- Remove the interrupt nubmer accroding to maxItems of interrupts.
drivers/irqchip/irq-aspeed-intc.c
- Reduce scope of variables, which are bit and status.
- Replace 32 with INTC_IRQS_PER_WORD define.
- Remove reduendant tab.
v3:
aspeed,ast2700-intc.yaml:
- Change reg with maxIntems:10 only.
- Change interrupt with maxIntems:10 only.
- Add description of INT0 and INTC1.
- Fix the indentation.
drivers/irqchip/irq-aspeed-intc.c:
- Change to use CONFIG_ARCH_ASPEED.
- Fix indentation.
- Remove irq_domain name assignment.
- Check all irq numbers first, and set chained.
Kevin Chen (2):
dt-bindings: interrupt-controller: Add support for ASPEED AST27XX INTC
irqchip/aspeed-intc: Add AST27XX INTC support
.../aspeed,ast2700-intc.yaml | 86 +++++++++++
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-aspeed-intc.c | 140 ++++++++++++++++++
3 files changed, 227 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/aspeed,ast2700-intc.yaml
create mode 100644 drivers/irqchip/irq-aspeed-intc.c
--
2.34.1
next reply other threads:[~2024-10-16 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 2:24 Kevin Chen [this message]
2024-10-16 2:24 ` [PATCH v4 1/2] dt-bindings: interrupt-controller: Add support for ASPEED AST27XX INTC Kevin Chen
2024-10-16 17:27 ` Rob Herring (Arm)
2024-10-16 2:24 ` [PATCH v4 2/2] irqchip/aspeed-intc: Add AST27XX INTC support Kevin 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=20241016022410.1154574-1-kevin_chen@aspeedtech.com \
--to=kevin_chen@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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 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).