All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, robh+dt@kernel.org,
	 eauger@redhat.com
Subject: Re: [PATCH 10/10] hw/arm/virt: Fix devicetree warnings about the virtio-iommu node
Date: Wed, 24 Aug 2022 20:51:18 +0100	[thread overview]
Message-ID: <CAFEAcA-Kv16weckhxM-mQrwiPZa5JMY4YkXcD5UfCzDKr4xGtQ@mail.gmail.com> (raw)
In-Reply-To: <20220824155113.286730-11-jean-philippe@linaro.org>

On Wed, 24 Aug 2022 at 16:51, Jean-Philippe Brucker
<jean-philippe@linaro.org> wrote:
>
> dt-validate and dtc throw a few warnings when parsing the virtio-iommu
> node:
>
>   pcie@10000000: virtio_iommu@16:compatible: ['virtio,pci-iommu'] does not contain items matching the given schema
>   pcie@10000000: Unevaluated properties are not allowed (... 'virtio_iommu@16' were unexpected)
>   From schema: linux/Documentation/devicetree/bindings/pci/host-generic-pci.yaml
>   pcie@10000000: virtio_iommu@16:compatible: ['virtio,pci-iommu'] does not contain items matching the given schema
>   From schema: dtschema/schemas/pci/pci-bus.yaml
>
>   Warning (pci_device_reg): /pcie@10000000/virtio_iommu@16: PCI unit address format error, expected "2,0"
>
> The compatible property for a PCI child node should follow the rules
> from "PCI Bus Binding to: IEEE Std 1275-1994". It should contain the
> Vendor ID and Device ID (or class code).
>
> The unit-name should be "device,function".
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe@linaro.org>
> ---
> Note that this doesn't follow
> linux/Documentation/devicetree/bindings/virtio/iommu.txt, I'll update
> that document when converting it to yaml, hopefully this Linux cycle.
> The "virtio,pci-iommu" compatible string is not actually used by any
> driver and only QEMU implements it, so we can get rid of it.

I'm not sure you can just change the compat string like that,
unless you can guarantee that nobody anywhere has ever
looked for it in a dtb. Also, "virtio,pci-iommu" is much
clearer than "pci1af4,1057"...

-- PMM


  reply	other threads:[~2022-08-24 19:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 15:51 [PATCH 00/10] hw/arm/virt: Fix dt-schema warnings Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 01/10] hw/arm/virt: Fix devicetree warning about the root node Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 02/10] hw/arm/boot: Fix devicetree warning about the PSCI node Jean-Philippe Brucker
2022-08-24 19:33   ` Peter Maydell
2022-09-01 14:53     ` Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 03/10] hw/arm/virt: Fix devicetree warnings about the GIC node Jean-Philippe Brucker
2022-08-24 19:36   ` Peter Maydell
2022-09-01 14:55     ` Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 04/10] hw/arm/virt: Use "msi-map" devicetree property for PCI Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 05/10] hw/arm/virt: Fix devicetree warning about the timer node Jean-Philippe Brucker
2022-08-24 19:40   ` Peter Maydell
2022-09-01 14:58     ` Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 06/10] hw/arm/virt: Fix devicetree warning about the gpio-key node Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 07/10] hw/arm/virt: Fix devicetree warnings about node names Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 08/10] hw/arm/virt: Fix devicetree warnings about the GPIO node Jean-Philippe Brucker
2022-08-24 19:48   ` Peter Maydell
2022-09-01 14:59     ` Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 09/10] hw/arm/virt: Fix devicetree warnings about the SMMU node Jean-Philippe Brucker
2022-08-24 19:45   ` Peter Maydell
2022-09-01 15:01     ` Jean-Philippe Brucker
2022-08-24 15:51 ` [PATCH 10/10] hw/arm/virt: Fix devicetree warnings about the virtio-iommu node Jean-Philippe Brucker
2022-08-24 19:51   ` Peter Maydell [this message]
2022-09-01 15:04     ` Jean-Philippe Brucker

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=CAFEAcA-Kv16weckhxM-mQrwiPZa5JMY4YkXcD5UfCzDKr4xGtQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=eauger@redhat.com \
    --cc=jean-philippe@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=robh+dt@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.