From: Ryan Chen <ryan_chen@aspeedtech.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.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:08:22 +0000 [thread overview]
Message-ID: <OS8PR06MB7541F8D3AEE1A618DB31F07BF25FA@OS8PR06MB7541.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <001d37c7-f704-4554-a4db-0cc130e07dd6@kernel.org>
> Subject: Re: [PATCH v3 1/2] dt-bindings: interrupt-controller: aspeed: Add
> parent node compatibles and refine documentation
>
> On 22/07/2025 11:51, Ryan Chen wrote:
> > + INTC0 is used to assert GIC if interrupt in INTC1 asserted.
> > + INTC1 is used to assert INTC0 if interrupt of modules asserted.
> > + +-----+ +---------+
> > + | GIC |---| INTC0 |
> > + +-----+ +---------+
> > + +---------+
> > + | |---module0
> > + | INTC0_0 |---module1
> > + | |---...
> > + +---------+---module31
> > + |---.... |
> > + +---------+
> > + | | +---------+
> > + | INTC0_11| +---| INTC1 |
> > + | | +---------+
> > + +---------+ +---------+---module0
> > + | INTC1_0 |---module1
> > + | |---...
> > + +---------+---module31
> > + ...
> > + +---------+---module0
> > + | INTC1_5 |---module1
> > + | |---...
> > + +---------+---module31
>
> You binding also said intc1 is the parent of intc-ic, so where is here intc-ic?
>
> This diagram and new binding do not match at all.
The corresponded compatible is following.
+-----+ +---------+
| GIC |---| INTC0 | -> (parent : aspeed,ast2700-intc0)
+-----+ +---------+
+---------+
| |---module0
| INTC0_0 |---module1
(child : aspeed,ast2700-intc-ic)
| |---...
+---------+---module31
|---.... |
+---------+
| | +---------+
| INTC0_11 | +---------------------------- | INTC1 | -> -> (parent : aspeed,ast2700-intc1)
(child : aspeed,ast2700-intc-ic)
| | +---------+
+---------+ +-------- -+---module0
| INTC1_0 | --> (child : aspeed,ast2700-intc-ic)
| |---...
+--------- +---module31
...
+--------- +---module0
| INTC1_5 | --> ((child : aspeed,ast2700-intc-ic))
| |---...
+--------- +---module31
>
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-07-23 8:08 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
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 [this message]
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=OS8PR06MB7541F8D3AEE1A618DB31F07BF25FA@OS8PR06MB7541.apcprd06.prod.outlook.com \
--to=ryan_chen@aspeedtech.com \
--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=krzk@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
all inboxes | Powered by JetHome®