From: Stuart Yoder <stuart.yoder@freescale.com>
To: <linuxppc-dev@ozlabs.org>
Cc: Stuart Yoder <stuart.yoder@freescale.com>
Subject: [PATCH] update name of pic-no-reset property
Date: Tue, 15 Mar 2011 12:37:58 -0600 [thread overview]
Message-ID: <1300214278-1588-1-git-send-email-stuart.yoder@freescale.com> (raw)
From: Stuart Yoder <stuart.yoder@freescale.com>
-changed name from 'no-reset' to 'pic-not-reset' be consisent with
Meador Inge's open pic binding patch
-update definition
Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
---
Documentation/powerpc/dts-bindings/fsl/mpic.txt | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/Documentation/powerpc/dts-bindings/fsl/mpic.txt b/Documentation/powerpc/dts-bindings/fsl/mpic.txt
index fdf97c5..8b76e0f 100644
--- a/Documentation/powerpc/dts-bindings/fsl/mpic.txt
+++ b/Documentation/powerpc/dts-bindings/fsl/mpic.txt
@@ -44,7 +44,7 @@ PROPERTIES
Value type: <u32>
Definition: Shall be 0.
- - no-reset
+ - pic-no-reset
Usage: optional
Value type: <empty>
Definition: The presence of this property specifies that the
@@ -53,7 +53,10 @@ PROPERTIES
configuration registers to a sane state-- masked or
directed at other cores. This ensures that the client
program will not receive interrupts for sources not belonging
- to the client.
+ to the client. The presence of this property also mandates
+ that any initialization related to interrupt sources shall
+ be limited to sources explicitly referenced in the device tree.
+
INTERRUPT SPECIFIER DEFINITION
--
1.7.2.2
next reply other threads:[~2011-03-15 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-15 18:37 Stuart Yoder [this message]
2011-03-15 19:09 ` [PATCH] update name of pic-no-reset property Kumar Gala
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=1300214278-1588-1-git-send-email-stuart.yoder@freescale.com \
--to=stuart.yoder@freescale.com \
--cc=linuxppc-dev@ozlabs.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).