From: Timur Tabi <timur@freescale•com>
To: lhthanh <lhthanh@kobekara•com>
Cc: Scott Wood <scottwood@freescale•com>, linuxppc-dev@ozlabs•org
Subject: Re: MPC8349E's DMA controller like ISA controller but with more feature?
Date: Fri, 24 Apr 2009 09:40:59 -0500 [thread overview]
Message-ID: <49F1CF7B.2080703@freescale.com> (raw)
In-Reply-To: <49F15831.9080507@kobekara.com>
lhthanh wrote:
> Thanks for your explaination! So if I want to transfer a buffer of data
> from a single I/O port, will not DMA framework
> also be able ?
No.
> Have I to write aother driver?
Yes.
> Actually, I don't want write all because there are serveral DMA code at
> hand. I only want to use a framework instead of re-writing.
There is no framework for what you want to do. There is only one other
driver that does what you want (sound/soc/fsl/fsl_dma.c), and that is a
complicated driver that does many things besides transferring data to an
I/O port.
> And I afraid that I can not write code which assure sharing DMA channels.
Look at arch/powerpc/boot/dts/mpc8610_hpcd.dts. The DMA channels that
are needed by the 8610 audio driver have a different 'compatible'
property. This is how you prevent the generic DMA driver from using a
channel that you want.
I'm afraid that you're going to have to study the DMA programming model,
and my device driver, and write a brand new driver from scratch.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-04-24 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 12:38 MPC8349E's DMA controller like ISA controller but with more feature? lhthanh
2009-04-20 15:55 ` Scott Wood
2009-04-20 17:23 ` Timur Tabi
[not found] ` <49EFEA26.2010602@kobekara.com>
[not found] ` <20090423154311.GA19717@ld0162-tx32.am.freescale.net>
[not found] ` <49F08FBC.9010903@freescale.com>
2009-04-24 6:12 ` lhthanh
2009-04-24 14:40 ` Timur Tabi [this message]
2009-05-07 1:59 ` lhthanh
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=49F1CF7B.2080703@freescale.com \
--to=timur@freescale$(echo .)com \
--cc=lhthanh@kobekara$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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