devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Rob Herring <robh@kernel.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
	devicetree-compiler@vger.kernel.org,
	Brad Griffis <bgriffis@nvidia.com>
Subject: Re: [PATCH] checks: Warn about missing #address-cells for interrupt parents
Date: Wed, 18 Dec 2024 16:07:35 +1100	[thread overview]
Message-ID: <Z2JYlybB2TditOhj@zatzit> (raw)
In-Reply-To: <CAL_JsqLrttpfXyDBteq98NMp3WLbmoQwa6JaGkbX4hiT1y2k4A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On Mon, Dec 16, 2024 at 01:37:01PM -0600, Rob Herring wrote:
> On Fri, Dec 13, 2024 at 8:14 AM Thierry Reding <thierry.reding@gmail.com> wrote:
> >
> > From: Thierry Reding <treding@nvidia.com>
> >
> > The device tree specification (v0.4) suggests that #address-cells is
> > mandatory for interrupt parent nodes. If this property is missing, Linux
> > will default to the value of 0.
> >
> > A number of device tree files rely on Linux' fallback and don't specify
> > an explicit #address-cells as suggested by the specification. This can
> > cause issues when these device trees are passed to software with a more
> > pedantic interpretation of the DT spec.
> >
> > Add a warning when this case is detected so that device tree files can
> > be fixed.
> >
> > Reported-by: Brad Griffis <bgriffis@nvidia.com>
> > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > ---
> > Applying this to Linux' copy reports on the order of 1300 issues that
> > originate from 29 .dtsi files. If this proposal is acceptable/useful, I
> > volunteer to patch those up so we don't get spammed by them.
> 
> I could have sworn I did a check for this, but it seems not.
> 
> > ---
> >  checks.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> 
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>

Makes sense to me.  Applied.

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-12-18  5:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 14:14 [PATCH] checks: Warn about missing #address-cells for interrupt parents Thierry Reding
2024-12-16 19:37 ` Rob Herring
2024-12-18  5:07   ` David Gibson [this message]
2024-12-18  2:01 ` Brad Griffis
2024-12-18  5:03   ` David Gibson
2024-12-18 15:50   ` Rob Herring
2024-12-19  4:07     ` David Gibson

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=Z2JYlybB2TditOhj@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=bgriffis@nvidia.com \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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).