All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh+dt@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 8/8] hw/arm/virt: Fix devicetree warnings about node names
Date: Thu, 13 Oct 2022 16:27:06 -0500	[thread overview]
Message-ID: <CAL_JsqKvXZ6J_H8zhsAkvpAyZvymVbxk1X-3JMV44-9yn7z+1w@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8uuzcHS3B3VY=J38gSrZUhnaTDKq1ei0rwtJtoG843bA@mail.gmail.com>

On Tue, Sep 27, 2022 at 6:28 AM Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Tue, 27 Sept 2022 at 11:12, Jean-Philippe Brucker
> <jean-philippe@linaro.org> wrote:
> >
> > The devicetree specification requires that nodes use a generic name
> > where appropriate. Fix the corresponding dt-validate warnings:
>
> Either:
> (1) guests are looking for devices in the DT by node name. In that
> case we can't change the node names without breaking them

Using node names is generally wrong unless the node name to use is
defined and that's the only way to identify them (e.g. /chosen).

> Or:
> (2) guest look for nodes by compatibility, in which case why
> do we care what the exact format of the node name is?

The spec[1] has defined standard class node names going back to 2008.
That covered all the names here except for 'iommu' and those names
date back to the 1990s. Obviously, there has been no checking of them
or many things for a long time, but now we can check much more than
reviews ever could we have a huge technical debt. The main reason on
care on these is just consistency.

Rob

[1] https://elinux.org/images/c/cf/Power_ePAPR_APPROVED_v1.1.pdf


  reply	other threads:[~2022-10-13 21:40 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 10:03 [PATCH v2 0/8] hw/arm/virt: Fix dt-schema warnings Jean-Philippe Brucker
2022-09-27 10:03 ` [PATCH v2 1/8] hw/arm/virt: Fix devicetree warning about the root node Jean-Philippe Brucker
2022-09-27 11:30   ` Peter Maydell
2022-09-27 12:48   ` Eric Auger
2022-09-27 10:03 ` [PATCH v2 2/8] hw/arm/virt: Fix devicetree warning about the GIC node Jean-Philippe Brucker
2022-09-27 11:33   ` Peter Maydell
2022-09-27 12:48   ` Eric Auger
2022-09-27 10:03 ` [PATCH v2 3/8] hw/arm/virt: Use "msi-map" devicetree property for PCI Jean-Philippe Brucker
2022-09-27 11:36   ` Peter Maydell
2022-09-27 12:48   ` Eric Auger
2022-09-27 10:03 ` [PATCH v2 4/8] hw/arm/virt: Fix devicetree warning about the gpio-key node Jean-Philippe Brucker
2022-09-27 11:56   ` Peter Maydell
2022-10-13 21:46     ` Rob Herring
2022-10-14 11:37       ` Peter Maydell
2022-09-27 12:48   ` Eric Auger
2022-09-27 10:03 ` [PATCH v2 5/8] hw/arm/virt: Fix devicetree warnings about the GPIO node Jean-Philippe Brucker
2022-09-27 11:25   ` Peter Maydell
2022-11-29 20:55     ` Rob Herring
2022-11-30 12:27       ` Peter Maydell
2022-09-27 10:03 ` [PATCH v2 6/8] hw/arm/virt: Fix devicetree warning about the SMMU node Jean-Philippe Brucker
2022-09-27 11:37   ` Peter Maydell
2022-09-27 13:24   ` Eric Auger
2022-09-27 10:03 ` [PATCH v2 7/8] hw/arm/virt: Fix devicetree warnings about the virtio-iommu node Jean-Philippe Brucker
2022-09-27 11:46   ` Peter Maydell
2022-09-27 14:35     ` Eric Auger
2022-10-21 14:33       ` Jean-Philippe Brucker
2022-10-24 10:44         ` Peter Maydell
2022-09-27 10:03 ` [PATCH v2 8/8] hw/arm/virt: Fix devicetree warnings about node names Jean-Philippe Brucker
2022-09-27 11:28   ` Peter Maydell
2022-10-13 21:27     ` Rob Herring [this message]
2022-09-29 16:53 ` [PATCH v2 0/8] hw/arm/virt: Fix dt-schema warnings Peter Maydell

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=CAL_JsqKvXZ6J_H8zhsAkvpAyZvymVbxk1X-3JMV44-9yn7z+1w@mail.gmail.com \
    --to=robh+dt@kernel.org \
    --cc=jean-philippe@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.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.