[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h5vqyjs7.ffs@tglx>
Date: Wed, 22 Oct 2025 18:37:44 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Ryan Chen <ryan_chen@...eedtech.com>, ryan_chen
<ryan_chen@...eedtech.com>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Joel
Stanley <joel@....id.au>, Andrew Jeffery <andrew@...econstruct.com.au>,
jk@...econstruct.com.au, Kevin Chen <kevin_chen@...eedtech.com>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-aspeed@...ts.ozlabs.org
Subject: Re: [PATCH v5 2/3] Irqchip/ast2700-intc: add debugfs support for
routing/protection display
On Wed, Oct 22 2025 at 14:55, Ryan Chen wrote:
The prefix is: irqchip/ast....:
> AST2700 INTC0/INTC1 nodes ("aspeed,ast2700-intc0/1") not only
> include the interrupt controller child node ("aspeed,ast2700-intc-ic"),
> but also provide interrupt routing and register protection features.
Lacks a new line to open a new paragraph.
> Adds debugfs entries for interrupt routing and protection status for
Add
> AST2700 INTC0/INTC1.
But what you are failing to explain is why this is required and
useful. Just adding code because we can is not a real good reason.
Thanks,
tglx
Powered by blists - more mailing lists