From: Rob Herring <robh@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"open list:IRQCHIP DRIVERS" <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
imx@lists.linux.dev
Subject: Re: [PATCH v2 1/1] dt-bindings: interrupt-controller: Add arm,armv7m-nvic and fix #interrupt-cells
Date: Thu, 5 Jun 2025 07:54:44 -0500 [thread overview]
Message-ID: <20250605125444.GA2354143-robh@kernel.org> (raw)
In-Reply-To: <20250528163704.690840-1-Frank.Li@nxp.com>
On Wed, May 28, 2025 at 12:37:04PM -0400, Frank Li wrote:
> According to existed dts arch/arm/boot/dts/armv7-m.dtsi and driver
> drivers/irqchip/irq-nvic.c, compatible string should be arm,armv7m-nvic,
>
> Remove unused compatible string arm,v6m-nvic, arm,v7m-nvic and arm,v8m-nvic.
>
> Fix below CHECK_DTB warning:
>
> arch/arm/boot/dts/nxp/vf/vf610m4-cosmic.dtb: /interrupt-controller@e000e100:
> failed to match any schema with compatible: ['arm,armv7m-nvic']
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> change in v2:
> - fix example interrupt-cells
> - commit message add driver information
> - remove unused compatible string
> ---
> .../bindings/interrupt-controller/arm,nvic.yaml | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.yaml b/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.yaml
> index d89eca956c5fa..c0be00b450291 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/arm,nvic.yaml
> @@ -17,9 +17,7 @@ description:
> properties:
> compatible:
> enum:
> - - arm,v6m-nvic
> - - arm,v7m-nvic
> - - arm,v8m-nvic
These came from Zephyr and are in use:
https://docs.zephyrproject.org/latest/build/dts/api/bindings/interrupt-controller/arm%2Cv7m-nvic.html
> + - arm,armv7m-nvic
Add '# deprecated' after it.
>
> reg:
> maxItems: 1
> @@ -30,10 +28,10 @@ properties:
> interrupt-controller: true
>
> '#interrupt-cells':
> - const: 2
> + const: 1
Have to support both.
> description: |
> Number of cells to encode an interrupt source:
> - first = interrupt number, second = priority.
> + first = interrupt number.
>
> arm,num-irq-priority-bits:
> description: Number of priority bits implemented by the SoC
> @@ -45,15 +43,14 @@ required:
> - reg
> - interrupt-controller
> - '#interrupt-cells'
> - - arm,num-irq-priority-bits
Is there NVIC h/w without priority bits? If not, this should remain
required.
>
> additionalProperties: false
>
> examples:
> - |
> interrupt-controller@e000e100 {
> - compatible = "arm,v7m-nvic";
> - #interrupt-cells = <2>;
> + compatible = "arm,armv7m-nvic";
> + #interrupt-cells = <1>;
> #address-cells = <0>;
> interrupt-controller;
> reg = <0xe000e100 0xc00>;
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-06-05 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-28 16:37 [PATCH v2 1/1] dt-bindings: interrupt-controller: Add arm,armv7m-nvic and fix #interrupt-cells Frank Li
2025-06-05 12:54 ` Rob Herring [this message]
2025-06-05 15:16 ` Frank Li
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=20250605125444.GA2354143-robh@kernel.org \
--to=robh@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.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