From: Rob Herring <robh@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Nishanth Menon <nm@ti.com>, "Andrew F. Davis" <afd@ti.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Lopes Ivo, Diogo Miguel (T CED IFD-PT)" <diogo.ivo@siemens.com>
Subject: Re: [PATCH] dt-bindings: PCI: ti,am65: Fix remaining binding warnings
Date: Thu, 15 Feb 2024 06:10:31 -0600 [thread overview]
Message-ID: <20240215121031.GA3671826-robh@kernel.org> (raw)
In-Reply-To: <d0f251f4-1c9e-4ed2-b7df-5a7fda28fe4e@siemens.com>
On Thu, Feb 15, 2024 at 09:14:47AM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> This adds the missing num-viewport, phys and phy-name properties to the
> schema. Based on driver code, num-viewport is required for the root
> complex, phys are optional. Their number corresponds to the number of
> lanes. The AM65x supports up to 2 lanes.
This is DW controller, right? num-viewport shouldn't be required. The
number of iATU entries is determined at runtime now. If it stays, it
should be deprecated.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> .../bindings/pci/ti,am65-pci-host.yaml | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/pci/ti,am65-pci-host.yaml b/Documentation/devicetree/bindings/pci/ti,am65-pci-host.yaml
> index a20dccbafd94..cdd6834f6a6f 100644
> --- a/Documentation/devicetree/bindings/pci/ti,am65-pci-host.yaml
> +++ b/Documentation/devicetree/bindings/pci/ti,am65-pci-host.yaml
> @@ -55,6 +55,20 @@ properties:
>
> dma-coherent: true
>
> + num-viewport:
> + $ref: /schemas/types.yaml#/definitions/uint32
> +
> + phys:
> + description: per-lane PHYs
> + minItems: 1
> + maxItems: 2
> +
> + phy-names:
> + minItems: 1
> + maxItems: 2
> + items:
> + pattern: '^pcie-phy[0-9]+$'
0-1 only
> +
> required:
> - compatible
> - reg
> @@ -74,6 +88,7 @@ then:
> - dma-coherent
> - power-domains
> - msi-map
> + - num-viewport
>
> unevaluatedProperties: false
>
> @@ -98,9 +113,13 @@ examples:
> ti,syscon-pcie-id = <&scm_conf 0x0210>;
> ti,syscon-pcie-mode = <&scm_conf 0x4060>;
> bus-range = <0x0 0xff>;
> + num-viewport = <16>;
> max-link-speed = <2>;
> dma-coherent;
> interrupts = <GIC_SPI 340 IRQ_TYPE_EDGE_RISING>;
> msi-map = <0x0 &gic_its 0x0 0x10000>;
> device_type = "pci";
> + num-lanes = <1>;
> + phys = <&serdes0 PHY_TYPE_PCIE 0>;
> + phy-names = "pcie-phy0";
> };
> --
> 2.35.3
next prev parent reply other threads:[~2024-02-15 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 8:14 [PATCH] dt-bindings: PCI: ti,am65: Fix remaining binding warnings Jan Kiszka
2024-02-15 9:17 ` Rob Herring
2024-02-15 12:10 ` Rob Herring [this message]
2024-02-15 12:22 ` Jan Kiszka
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=20240215121031.GA3671826-robh@kernel.org \
--to=robh@kernel.org \
--cc=afd@ti.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=kishon@ti.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nm@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).