From: Krzysztof Kozlowski <krzk@kernel.org>
To: Matt Ranostay <mranostay@ti.com>, vigneshr@ti.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] dt-bindings: PCI: ti,j721e-pci-*: Add missing interrupt properties
Date: Fri, 23 Sep 2022 13:29:30 +0200 [thread overview]
Message-ID: <cd4cb9f2-b9c2-afc5-fa01-4a6ec946aef4@kernel.org> (raw)
In-Reply-To: <20220922204434.74764-3-mranostay@ti.com>
On 22/09/2022 22:44, Matt Ranostay wrote:
> Both interrupts, and interrupt names weren't defined in both EP and host
> yaml. Also define the only possible interrupt-name as link_state, and
> maxItems of interrupts to one.
>
> This patch resolves the following warning:
>
> arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb: pcie-ep@2910000: Unevaluated properties are not allowed ('interrupt-names', 'interrupts' were unexpected)
> From schema Documentation/devicetree/bindings/pci/ti,j721e-pci-ep.yaml
Use scripts/get_maintainers.pl to CC all maintainers and relevant
mailing lists.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-09-23 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:44 [PATCH 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings Matt Ranostay
2022-09-22 20:44 ` [PATCH 1/2] dt-bindings: PCI: ti,j721e-pci-host: add interrupt controller definition Matt Ranostay
2022-09-23 9:31 ` Krzysztof Kozlowski
2022-09-24 20:46 ` Matt Ranostay
2022-09-25 7:38 ` Krzysztof Kozlowski
2022-09-22 20:44 ` [PATCH 2/2] dt-bindings: PCI: ti,j721e-pci-*: Add missing interrupt properties Matt Ranostay
2022-09-23 11:29 ` Krzysztof Kozlowski [this message]
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=cd4cb9f2-b9c2-afc5-fa01-4a6ec946aef4@kernel.org \
--to=krzk@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mranostay@ti.com \
--cc=vigneshr@ti.com \
/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).