From: Dan Williams <dan.j.williams@intel.com>
To: Scott Wood <scottwood@freescale.com>
Cc: "Nelson, Shannon" <shannon.nelson@intel.com>,
linuxppc-dev@ozlabs.org, paulus@samba.org,
galak@gate.crashing.org, akpm@linux-foundation.org,
leoli@freescale.com, wei.zhang@freescale.com
Subject: Re: [patch 1/1] fsldma: the MPC8377MDS board device tree node for fsldma driver
Date: Wed, 14 May 2008 16:36:30 -0700 [thread overview]
Message-ID: <1210808190.17120.1.camel@dwillia2-linux.ch.intel.com> (raw)
In-Reply-To: <482B7588.1010201@freescale.com>
[adding Li Yang (new fsldma maintainer) to the cc]
On Wed, 2008-05-14 at 16:28 -0700, Scott Wood wrote:
> akpm@linux-foundation.org wrote:
> > From: Zhang Wei <wei.zhang@freescale.com>
> >
> > The fsldma driver is tested on MPC8377MDS board. The patch adds fsldma driver
> > support into MPC8377MDS device tree.
> >
> > Signed-off-by: Zhang Wei <wei.zhang@freescale.com>
> > Cc: "Nelson, Shannon" <shannon.nelson@intel.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Cc: Kumar Gala <galak@gate.crashing.org>
> > Cc: Paul Mackerras <paulus@samba.org>
> > Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> > Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> > ---
> >
> > arch/powerpc/boot/dts/mpc8377_mds.dts | 27 ++++++++++++++++++++++++
> > 1 file changed, 27 insertions(+)
> >
> > diff -puN arch/powerpc/boot/dts/mpc8377_mds.dts~fsldma-the-mpc8377mds-board-device-tree-node-for-fsldma-driver arch/powerpc/boot/dts/mpc8377_mds.dts
> > --- a/arch/powerpc/boot/dts/mpc8377_mds.dts~fsldma-the-mpc8377mds-board-device-tree-node-for-fsldma-driver
> > +++ a/arch/powerpc/boot/dts/mpc8377_mds.dts
> > @@ -295,6 +295,33 @@
> > };
> > };
> >
> > + dma@82a8 {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + compatible = "fsl,mpc8349-dma";
> > + reg = <0x82a8 4>;
> > + ranges = <0 0x8100 0x1a8>;
> > + interrupt-parent = <&ipic>;
> > + interrupts = <0x47 8>;
> > + cell-index = <0>;
> > + dma-channel@0 {
> > + compatible = "fsl,mpc8349-dma-channel";
> > + reg = <0 0x80>;
> > + };
> > + dma-channel@80 {
> > + compatible = "fsl,mpc8349-dma-channel";
> > + reg = <0x80 0x80>;
> > + };
> > + dma-channel@100 {
> > + compatible = "fsl,mpc8349-dma-channel";
> > + reg = <0x100 0x80>;
> > + };
> > + dma-channel@180 {
> > + compatible = "fsl,mpc8349-dma-channel";
> > + reg = <0x180 0x28>;
> > + };
>
> According to booting-without-of.txt, the interrupts property should be
> repeated in each channel. The driver also needs to be fixed to remember
> whether it registered a DMA-block-level interrupt handler already, and
> not try to register a channel interrupt.
>
> -Scott
>
>
next prev parent reply other threads:[~2008-05-14 23:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 23:17 [patch 1/1] fsldma: the MPC8377MDS board device tree node for fsldma driver akpm
2008-05-14 23:28 ` Scott Wood
2008-05-14 23:36 ` Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-09 23:29 akpm
2008-06-10 5:16 ` 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=1210808190.17120.1.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=galak@gate.crashing.org \
--cc=leoli@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=shannon.nelson@intel.com \
--cc=wei.zhang@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).