linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: kishon@ti.com, devicetree@vger.kernel.org,
	linux-pci@vger.kernel.org, bhelgaas@google.com, krzk@kernel.org,
	vigneshr@ti.com, robh+dt@kernel.org
Subject: Re: [PATCH v2 2/2] dt-bindings: PCI: ti,j721e-pci-*: Add missing interrupt properties
Date: Thu, 29 Sep 2022 15:12:37 -0500	[thread overview]
Message-ID: <166448233656.2661829.7240169247803923570.robh@kernel.org> (raw)
In-Reply-To: <20220924223517.123343-3-mranostay@ti.com>

On Sat, 24 Sep 2022 15:35:17 -0700, 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
> 
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> ---
>  Documentation/devicetree/bindings/pci/ti,j721e-pci-ep.yaml | 7 +++++++
>  .../devicetree/bindings/pci/ti,j721e-pci-host.yaml         | 7 +++++++
>  2 files changed, 14 insertions(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-09-29 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-24 22:35 [PATCH v2 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings Matt Ranostay
2022-09-24 22:35 ` [PATCH v2 1/2] dt-bindings: PCI: ti,j721e-pci-host: add interrupt controller definition Matt Ranostay
2022-09-29 20:11   ` Rob Herring
2022-09-24 22:35 ` [PATCH v2 2/2] dt-bindings: PCI: ti,j721e-pci-*: Add missing interrupt properties Matt Ranostay
2022-09-29 20:12   ` Rob Herring [this message]
2022-09-25  9:21 ` [PATCH v2 0/2] dt-bindings: PCI: ti,j721e-pci-*: resolve unexpected property warnings Krzysztof Kozlowski
2022-09-26  3:06   ` Matt Ranostay
2022-09-26  6:18     ` Krzysztof Kozlowski

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=166448233656.2661829.7240169247803923570.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=krzk@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mranostay@ti.com \
    --cc=robh+dt@kernel.org \
    --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).