From: Randy Dunlap <rdunlap@xenotime.net>
To: Kyle Moffett <Kyle.D.Moffett@boeing.com>
Cc: linux-doc@vger.kernel.org,
Lucas De Marchi <lucas.demarchi@profusion.mobi>,
devicetree-discuss@lists.ozlabs.org,
Rob Herring <rob.herring@calxeda.com>,
Stuart Yoder <stuart.yoder@freescale.com>,
Paul Mackerras <paulus@samba.org>,
Josh Boyer <jwboyer@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsl/mpic: Document and use the "big-endian" device-tree flag
Date: Wed, 04 Jan 2012 15:22:56 -0800 [thread overview]
Message-ID: <4F04DF50.4070201@xenotime.net> (raw)
In-Reply-To: <1324571123-11577-1-git-send-email-Kyle.D.Moffett@boeing.com>
On 12/22/2011 08:25 AM, Kyle Moffett wrote:
> The MPIC code checks for a "big-endian" property and sets the flag
> MPIC_BIG_ENDIAN if one is present. Unfortunately, the PowerQUICC-III
> compatible device-tree does not specify it, so all of the board ports
> need to manually set that flag when calling mpic_alloc().
>
> Document the flag and add it to the pq3 device tree. Existing code
> will still need to pass the MPIC_BIG_ENDIAN flag because their dtb may
> not have this property, but new platforms shouldn't need to do so.
>
> Signed-off-by: Kyle Moffett <Kyle.D.Moffett@boeing.com>
Grant, are you merging this patch?
I don't think I should merge the patch to arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi.
> ---
> .../devicetree/bindings/powerpc/fsl/mpic.txt | 9 ++++++++-
> arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi | 1 +
> 2 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/mpic.txt b/Documentation/devicetree/bindings/powerpc/fsl/mpic.txt
> index 2cf38bd..ebafba2 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/mpic.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/mpic.txt
> @@ -56,7 +56,14 @@ PROPERTIES
> 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.
> -
> +
> + - big-endian
> + Usage: optional
> + Value type: <empty>
> + If present the MPIC will be assumed to be big-endian. Some
> + device-trees omit this property on MPIC nodes even when the MPIC is
> + in fact big-endian, so certain boards override this property.
> +
> INTERRUPT SPECIFIER DEFINITION
>
> Interrupt specifiers consists of 4 cells encoded as
> diff --git a/arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi b/arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi
> index 5c80460..47f2b67 100644
> --- a/arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi
> +++ b/arch/powerpc/boot/dts/fsl/pq3-mpic.dtsi
> @@ -39,6 +39,7 @@ mpic: pic@40000 {
> reg = <0x40000 0x40000>;
> compatible = "fsl,mpic";
> device_type = "open-pic";
> + big-endian;
> };
>
> timer@41100 {
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-01-04 22:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 16:25 [PATCH] fsl/mpic: Document and use the "big-endian" device-tree flag Kyle Moffett
2012-01-04 23:22 ` Randy Dunlap [this message]
2012-01-04 23:08 ` Benjamin Herrenschmidt
2012-01-05 18:35 ` 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=4F04DF50.4070201@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Kyle.D.Moffett@boeing.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lucas.demarchi@profusion.mobi \
--cc=paulus@samba.org \
--cc=rob.herring@calxeda.com \
--cc=stuart.yoder@freescale.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).