devicetree-spec.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Boyd <stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] interrupt-mapping: Fix parent interrupt specifier description
Date: Wed,  9 Aug 2017 16:28:24 -0700	[thread overview]
Message-ID: <20170809232824.4959-1-stephen.boyd@linaro.org> (raw)

The number of cells here is not dictated by the #interrupt-cells
property of this node, but the same property in the interrupt
parent. This looks like a copy/paste mistake from child interrupt
specifier.

Signed-off-by: Stephen Boyd <stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
---
 source/devicetree-basics.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/source/devicetree-basics.rst b/source/devicetree-basics.rst
index df3d3c313574..02696bac15c7 100644
--- a/source/devicetree-basics.rst
+++ b/source/devicetree-basics.rst
@@ -1120,8 +1120,8 @@ Description:
    parent interrupt specifier
        The interrupt specifier in the parent domain. The number of 32-bit
        cells required to specify this component is described by the
-       *#interrupt-cells* property of this node—the nexus node containing
-       the *interrupt-map* property.
+       *#interrupt-cells* property of the node pointed to by the
+       interrupt-parent field.
 
    Lookups are performed on the interrupt mapping table by matching a
    unit-address/interrupt specifier pair against the child components in
-- 
2.7.4

             reply	other threads:[~2017-08-09 23:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-09 23:28 Stephen Boyd [this message]
     [not found] ` <20170809232824.4959-1-stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-08-11  3:19   ` [PATCH] interrupt-mapping: Fix parent interrupt specifier description Rob Herring

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=20170809232824.4959-1-stephen.boyd@linaro.org \
    --to=stephen.boyd-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
    --cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@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 NNTP newsgroup(s).