linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Cc: bluesmoke-devel@lists.sourceforge.net,
	Grant Erickson <gerickson@nuovations.com>
Subject: Re: [PATCH v2] powerpc/4xx: DTS: Add Add'l SDRAM0 Compatible and Interrupt Info
Date: Thu, 18 Dec 2008 09:04:23 +0100	[thread overview]
Message-ID: <200812180904.23593.sr@denx.de> (raw)
In-Reply-To: <1229563900-10447-1-git-send-email-gerickson@nuovations.com>

On Thursday 18 December 2008, Grant Erickson wrote:
> Added additional information for type and compatibility strings and
> interrupt information to the SDRAM0 memory-controller device tree
> nodes for AMCC PowerPC 405EX[r]-based boards to facilitate binding
> with the new "ibm,sdram-4xx-ddr2" EDAC memory controller adapter driver.
>
> Signed-off-by: Grant Erickson <gerickson@nuovations.com>
> ---
> As support in the associated EDAC adapter driver is added over time,
> similar changes will/should be made to the DTS files for boards
> leveraging realizations of this "ibm,sdram-4xx-ddr2" controller,
> including the 440SP, 440SPe, 460EX, 460GT and 460SX.
>
> Patch v2, based on review from David Gibson, removes the 'device_type'
> field because it is only used for legacy OpenFirmware method
> interfaces and no such compatibility is warranted here. In addition,
> removed address- and size-cells as this node has no children.
>
>  arch/powerpc/boot/dts/haleakala.dts |    8 +-
>  arch/powerpc/boot/dts/kilauea.dts   |    8 +-
>  arch/powerpc/boot/dts/makalu.dts    |    8 +-
>  3 files changed, 21 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/boot/dts/haleakala.dts
> b/arch/powerpc/boot/dts/haleakala.dts index 513bc43..64880ab 100644
> --- a/arch/powerpc/boot/dts/haleakala.dts
> +++ b/arch/powerpc/boot/dts/haleakala.dts
> @@ -89,8 +89,14 @@
>  		clock-frequency = <0>; /* Filled in by U-Boot */
>
>  		SDRAM0: memory-controller {
> -			compatible = "ibm,sdram-405exr";
> +			compatible = "ibm,sdram-405exr", "ibm,sdram-4xx-ddr2";
>  			dcr-reg = <0x010 0x002>;
> +			#interrupt-cells = <1>;
> +			interrupt-parent = <&SDRAM0>;
> +			interrupts = <0x0 0x1>;
> +			interrupt-map = </* ECCDED Error */ 0x0 &UIC2 0x5 0x4
> +					 /* ECCSEC Error */ 0x1 &UIC2 0x6 0x4>;
> +			interrupt-map-mask = <0xffffffff>;

When all interrupts are mapped the same parent, this should do as well:

			interrupt-parent = <&UIC2>;
			interrupts = <0x5 0x4	/* ECCDED Error */
				      0x6 0x4>; /* ECCSEC Error */

Other than this:

Acked-by: Stefan Roese <sr@denx.de>

Thanks.

Best regards,
Stefan

  parent reply	other threads:[~2008-12-18  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  1:31 [PATCH v2] powerpc/4xx: DTS: Add Add'l SDRAM0 Compatible and Interrupt Info Grant Erickson
2008-12-18  1:54 ` David Gibson
2008-12-18  8:04 ` Stefan Roese [this message]
2008-12-18 17:56   ` Josh Boyer
2008-12-18 18:04     ` Grant Erickson
2008-12-18 18:34       ` Josh Boyer

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=200812180904.23593.sr@denx.de \
    --to=sr@denx.de \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=gerickson@nuovations.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).