From: David Gibson <david@gibson.dropbear.id.au>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: wd@denx.de, dzu@denx.de, linux-raid@vger.kernel.org,
linuxppc-dev@ozlabs.org, yanok@emcraft.com,
dan.j.williams@intel.com
Subject: Re: [PATCH 11/11][v2] ppc440spe-adma: ADMA driver for PPC440SP(e) systems
Date: Tue, 13 Jan 2009 13:23:16 +1100 [thread overview]
Message-ID: <20090113022316.GA3628@yookeroo.seuss> (raw)
In-Reply-To: <200901130343.56020.yur@emcraft.com>
On Tue, Jan 13, 2009 at 03:43:55AM +0300, Yuri Tikhonov wrote:
> Adds the platform device definitions and the architecture specific support
> routines for the ppc440spe adma driver.
>
> Any board equipped with PPC440SP(e) controller may utilize this driver.
>
> diff --git a/arch/powerpc/boot/dts/katmai.dts b/arch/powerpc/boot/dts/katmai.dts
> index 077819b..f2f77c8 100644
> --- a/arch/powerpc/boot/dts/katmai.dts
> +++ b/arch/powerpc/boot/dts/katmai.dts
> @@ -16,7 +16,7 @@
>
> / {
> #address-cells = <2>;
> - #size-cells = <1>;
> + #size-cells = <2>;
You've changed the root level size-cells, but haven't updated the
sub-nodes (such as /memory) accordingly.
> model = "amcc,katmai";
> compatible = "amcc,katmai";
> dcr-parent = <&{/cpus/cpu@0}>;
> @@ -392,6 +392,30 @@
> 0x0 0x0 0x0 0x3 &UIC3 0xa 0x4 /* swizzled int C */
> 0x0 0x0 0x0 0x4 &UIC3 0xb 0x4 /* swizzled int D */>;
> };
> + DMA0: dma0 {
No 'compatible' property, which seems dubious.
> + interrupt-parent = <&DMA0>;
> + interrupts = <0 1>;
> + #interrupt-cells = <1>;
> + #address-cells = <0>;
> + #size-cells = <0>;
> + interrupt-map = <
> + 0 &UIC0 0x14 4
> + 1 &UIC1 0x16 4>;
> + };
> + DMA1: dma1 {
> + interrupt-parent = <&DMA1>;
> + interrupts = <0 1>;
> + #interrupt-cells = <1>;
> + #address-cells = <0>;
> + #size-cells = <0>;
> + interrupt-map = <
> + 0 &UIC0 0x16 4
> + 1 &UIC1 0x16 4>;
Are these interrupt-maps correct? The second interrupt from both dma
controllers is routed to the same line on UIC1?
> + };
> + xor {
> + interrupt-parent = <&UIC1>;
> + interrupts = <0x1f 4>;
What the hell is this thing? No compatible property, nor even a
meaningful name.
> + };
> };
--
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
next prev parent reply other threads:[~2009-01-13 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 0:43 [PATCH 11/11][v2] ppc440spe-adma: ADMA driver for PPC440SP(e) systems Yuri Tikhonov
2009-01-13 2:23 ` David Gibson [this message]
2009-01-16 9:03 ` Re[2]: " Yuri Tikhonov
2009-01-15 2:24 ` Anton Vorontsov
2009-01-16 12:13 ` Re[2]: " Yuri Tikhonov
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=20090113022316.GA3628@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=dan.j.williams@intel.com \
--cc=dzu@denx.de \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.de \
--cc=yanok@emcraft.com \
--cc=yur@emcraft.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).