devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Devicetree Compiler
	<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Andre Przywara <andre.przywara-5wv7dgnIgG8@public.gmane.org>
Subject: Re: [PATCH 1/3] checks: Add an interrupt-map check
Date: Wed, 13 Oct 2021 14:43:39 +1100	[thread overview]
Message-ID: <YWZV67jAjwgo4rLm@yekko> (raw)
In-Reply-To: <CAL_JsqKrRAOiuY=71xsZ0RRojsOraXmSaLpDYSXx1E84SF_qDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

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

On Mon, Oct 11, 2021 at 11:56:19AM -0500, Rob Herring wrote:
> On Sun, Oct 10, 2021 at 11:58 PM David Gibson
> <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> >
> > On Tue, Sep 28, 2021 at 04:23:33PM -0500, Rob Herring wrote:
[snip]
> > > diff --git a/tests/bad-interrupt-map-parent.dts b/tests/bad-interrupt-map-parent.dts
> > > new file mode 100644
> > > index 000000000000..fe88ce2fe76f
> > > --- /dev/null
> > > +++ b/tests/bad-interrupt-map-parent.dts
> > > @@ -0,0 +1,17 @@
> > > +/dts-v1/;
> > > +
> > > +/ {
> > > +     interrupt-parent = <&intc>;
> > > +     intc: interrupt-controller {
> > > +     };
> > > +
> > > +     node {
> > > +             #address-cells = <0>;
> > > +             #interrupt-cells = <1>;
> > > +             interrupt-map = <1 &intc 1 2 3>;
> >
> > If you just want to verify the check on the bad parent, shouldn't you
> > have an interrupt-map-mask here?
> 
> No, a missing interrupt-map-mask is not an error. Only the wrong
> number of cells is an error. It's treated as all 1s mask if not
> present. So, in interest of having a minimal test, I omitted it.

Ah, sorry, my mistake.

-- 
David Gibson			| 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 --]

      parent reply	other threads:[~2021-10-13  3:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 21:23 [PATCH 1/3] checks: Add an interrupt-map check Rob Herring
     [not found] ` <20210928212335.2061125-1-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-09-28 21:23   ` [PATCH 2/3] checks: Drop interrupt provider '#address-cells' check Rob Herring
     [not found]     ` <20210928212335.2061125-2-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-10-11  4:57       ` David Gibson
2021-09-28 21:23   ` [PATCH 3/3] checks: Ensure '#interrupt-cells' only exists in interrupt providers Rob Herring
     [not found]     ` <20210928212335.2061125-3-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2021-10-11  4:58       ` David Gibson
2021-10-11  4:56   ` [PATCH 1/3] checks: Add an interrupt-map check David Gibson
2021-10-11 16:56     ` Rob Herring
     [not found]       ` <CAL_JsqKrRAOiuY=71xsZ0RRojsOraXmSaLpDYSXx1E84SF_qDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-10-13  3:43         ` David Gibson [this message]

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=YWZV67jAjwgo4rLm@yekko \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=andre.przywara-5wv7dgnIgG8@public.gmane.org \
    --cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).