From: Jean-Philippe Brucker <jean-philippe@linaro.org>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
virtualization@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: virtio: pci-iommu: Add ref to pci-device.yaml
Date: Tue, 8 Apr 2025 08:35:27 +0100 [thread overview]
Message-ID: <20250408073527.GA2279090@myrica> (raw)
In-Reply-To: <20250407165341.2934499-1-robh@kernel.org>
On Mon, Apr 07, 2025 at 11:53:40AM -0500, Rob Herring (Arm) wrote:
> The virtio pci-iommu is a PCI device, so it should have a reference to
> the pci-device.yaml schema. The pci-device.yaml schema defines the 'reg'
> format as a schema, so the text description for 'reg' can be dropped.
>
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> .../devicetree/bindings/virtio/pci-iommu.yaml | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/virtio/pci-iommu.yaml b/Documentation/devicetree/bindings/virtio/pci-iommu.yaml
> index 972a785a42de..8bd6ad72ac7a 100644
> --- a/Documentation/devicetree/bindings/virtio/pci-iommu.yaml
> +++ b/Documentation/devicetree/bindings/virtio/pci-iommu.yaml
> @@ -20,6 +20,9 @@ description: |
> virtio-iommu node doesn't have an "iommus" property, and is omitted from
> the iommu-map property of the root complex.
>
> +allOf:
> + - $ref: /schemas/pci/pci-device.yaml#
> +
> properties:
> # If compatible is present, it should contain the vendor and device ID
> # according to the PCI Bus Binding specification. Since PCI provides
> @@ -33,12 +36,7 @@ properties:
> - const: pci1af4,1057
>
> reg:
> - description: |
> - PCI address of the IOMMU. As defined in the PCI Bus Binding
> - reference, the reg property is a five-cell address encoded as (phys.hi
> - phys.mid phys.lo size.hi size.lo). phys.hi should contain the device's
> - BDF as 0b00000000 bbbbbbbb dddddfff 00000000. The other cells should be
> - zero. See Documentation/devicetree/bindings/pci/pci.txt
> + maxItems: 1
>
> '#iommu-cells':
> const: 1
> --
> 2.47.2
>
next prev parent reply other threads:[~2025-04-08 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 16:53 [PATCH] dt-bindings: virtio: pci-iommu: Add ref to pci-device.yaml Rob Herring (Arm)
2025-04-08 7:35 ` Jean-Philippe Brucker [this message]
2025-04-17 12:49 ` Rob Herring (Arm)
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=20250408073527.GA2279090@myrica \
--to=jean-philippe@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=robh@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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