From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.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>,
Kevin Chen <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: Re: [PATCH v3 1/2] dt-bindings: interrupt-controller: aspeed: Add parent node compatibles and refine documentation
Date: Wed, 23 Jul 2025 08:11:44 +0200 [thread overview]
Message-ID: <a9294387-ce7f-482e-89e1-7c85feaeeee9@kernel.org> (raw)
In-Reply-To: <20250722095156.1672873-2-ryan_chen@aspeedtech.com>
On 22/07/2025 11:51, Ryan Chen wrote:
> The AST2700 SoC contains two independent top-level interrupt controllers
> (INTC0 and INTC1), each responsible for handling different peripheral
> groups and occupying separate register spaces. Above them, PSP(CA35) GIC
> controller acts as the root interrupt aggregator. Accurately describing
> this hierarchical hardware structure in the device tree requires distinct
> compatible strings for the parent nodes of INTC0 and INTC1.
>
> - Adds 'aspeed,ast2700-intc0' and 'aspeed,ast2700-intc1' compatible
> strings for parent interrupt controller nodes. (in addition to the
> existing 'aspeed,ast2700-intc-ic' for child nodes)
I don't understand how this solves your problem at all. Look at old
diagram - is it correct? If not, what makes you think that new diagram
is correct?
What is the meaning of existing binding and existing intc-ic compatible?
> - Clarifies the relationship and function of INTC0 parent
> (intc0_0~x: child), INTC1 parent (intc1_0~x: child), and the GIC
> in the documentation.
> - Updates block diagrams and device tree examples to illustrate
> the hierarchy and compatible usage.
> - Refines documentation and example formatting.
>
> This change allows the device tree and driver to distinguish between
> parent (top-level) and child (group) interrupt controller nodes,
> enabling more precise driver matching SOC register space allocation.
And how it was not possible before? That's poor argument especially that
DT does not have to ever distinguish that.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-23 6:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 9:51 [PATCH v3 0/2] irqchip: aspeed: Add AST2700 INTC debugfs support and yaml update Ryan Chen
2025-07-22 9:51 ` [PATCH v3 1/2] dt-bindings: interrupt-controller: aspeed: Add parent node compatibles and refine documentation Ryan Chen
2025-07-22 15:28 ` Thomas Gleixner
2025-07-23 7:47 ` Ryan Chen
2025-07-23 5:01 ` Rob Herring
2025-07-23 7:56 ` Ryan Chen
2025-07-23 6:11 ` Krzysztof Kozlowski [this message]
2025-07-23 8:18 ` Ryan Chen
2025-07-25 7:18 ` Ryan Chen
2025-07-25 7:41 ` Krzysztof Kozlowski
2025-07-23 6:13 ` Krzysztof Kozlowski
2025-07-23 8:08 ` Ryan Chen
2025-07-25 7:40 ` Krzysztof Kozlowski
2025-07-27 1:47 ` Ryan Chen
2025-07-27 9:36 ` Krzysztof Kozlowski
2025-07-28 2:54 ` Ryan Chen
2025-07-22 9:51 ` [PATCH v3 2/2] irqchip: aspeed: add debugfs support and AST2700 INTC0/INTC1 routing/protection display Ryan Chen
2025-07-22 15:27 ` Thomas Gleixner
2025-07-23 6:02 ` Ryan Chen
2025-07-23 17:37 ` Thomas Gleixner
2025-07-24 2:19 ` 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=a9294387-ce7f-482e-89e1-7c85feaeeee9@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=kevin_chen@aspeedtech.com \
--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=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 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.