From: Rob Herring <robh@kernel.org>
To: Thippeswamy Havalige <thippesw@amd.com>
Cc: lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pci@vger.kernel.org, thippeswamy.havalige@amd.com,
linux-arm-kernel@lists.infradead.org, michal.simek@amd.com
Subject: Re: [PATCH v3 1/2] dt-bindings: PCI: xilinx-xdma: Add schemas for Xilinx QDMA PCIe Root Port Bridge
Date: Fri, 9 Aug 2024 12:10:07 -0600 [thread overview]
Message-ID: <20240809181007.GA967711-robh@kernel.org> (raw)
In-Reply-To: <20240809060955.1982335-2-thippesw@amd.com>
On Fri, Aug 09, 2024 at 11:39:54AM +0530, Thippeswamy Havalige wrote:
> Add YAML devicetree schemas for Xilinx QDMA Soft IP PCIe Root Port
> Bridge.
>
> Signed-off-by: Thippeswamy Havalige <thippesw@amd.com>
> ---
> .../devicetree/bindings/pci/xlnx,xdma-host.yaml | 36 ++++++++++++++++++++--
> 1 file changed, 34 insertions(+), 2 deletions(-)
> ---
> changes in v3
> - constrain the new entry to only the new compatible.
> - Remove example.
>
> changes in v2
> - update dt node label with pcie.
> ---
> diff --git a/Documentation/devicetree/bindings/pci/xlnx,xdma-host.yaml b/Documentation/devicetree/bindings/pci/xlnx,xdma-host.yaml
> index 2f59b3a..f1efd919 100644
> --- a/Documentation/devicetree/bindings/pci/xlnx,xdma-host.yaml
> +++ b/Documentation/devicetree/bindings/pci/xlnx,xdma-host.yaml
> @@ -14,10 +14,21 @@ allOf:
>
> properties:
> compatible:
> - const: xlnx,xdma-host-3.00
> + enum:
> + - xlnx,xdma-host-3.00
> + - xlnx,qdma-host-3.00
Kind of odd that both IP have the exact same version number. Please
explain in the commit message where it comes from. If you just copied it
from the previous one, then nak.
>
> reg:
> - maxItems: 1
> + items:
> + - description: configuration region and XDMA bridge register.
> + - description: QDMA bridge register.
> + minItems: 1
> +
> + reg-names:
> + items:
> + - const: cfg
> + - const: breg
> + minItems: 1
>
> ranges:
> maxItems: 2
> @@ -76,6 +87,27 @@ required:
> - "#interrupt-cells"
> - interrupt-controller
>
> +if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - xlnx,qdma-host-3.00
> +then:
> + properties:
> + reg:
> + minItems: 2
> + reg-names:
> + minItems: 2
> + required:
> + - reg-names
> +else:
> + properties:
> + reg:
> + maxItems: 1
> + reg-names:
> + maxItems: 1
> +
> unevaluatedProperties: false
>
> examples:
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2024-08-09 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 6:09 [PATCH v3 0/2] Add support for Xilinx XDMA Soft IP as Root Port Thippeswamy Havalige
2024-08-09 6:09 ` [PATCH v3 1/2] dt-bindings: PCI: xilinx-xdma: Add schemas for Xilinx QDMA PCIe Root Port Bridge Thippeswamy Havalige
2024-08-09 14:50 ` Conor Dooley
2024-08-09 18:10 ` Rob Herring [this message]
2024-08-11 2:13 ` Havalige, Thippeswamy
2024-08-09 6:09 ` [PATCH v3 2/2] PCI: xilinx-xdma: Add Xilinx QDMA Root Port driver Thippeswamy Havalige
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=20240809181007.GA967711-robh@kernel.org \
--to=robh@kernel.org \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=michal.simek@amd.com \
--cc=thippesw@amd.com \
--cc=thippeswamy.havalige@amd.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).