From: Sebastian Siewior <linuxppc-embedded@ml.breakpoint.cc>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Using the loop feature of the DMA controller on MPC8544 DS
Date: Wed, 12 Mar 2008 22:15:04 +0100 [thread overview]
Message-ID: <20080312211504.GC11426@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <47D841EE.2060806@freescale.com>
* Timur Tabi | 2008-03-12 15:49:50 [-0500]:
>Well, I need to solve this problem myself, but I wasn't planning on doing it for
>a while since I have a higher priority assignment at the moment. My 8610 sound
>driver does DMA all on its own and completely ignores Zhang's driver, so I need
>to fix that.
Ah okey. So you grab one DMA channel for yourself and you hope no one else
is going to use it?
Are you using lists descriptors or single transfers?
>Unfortunately, I'm not familiar with Zhang's driver at all (it's changed too
>much since I last looked at it), so I don't know what the *best* way is.
His driver uses DMA engine so you can't use the cool features / arch
specific settings.
>For my
>sound driver, I don't even know if I'll be able to leverage Zhang's driver at
>all, since I need to use a specific DMA channel, and I need to control each of
>the link descriptors. Zhang's driver abstracts DMA too much. So all I was
>going to do is come up with a way to reserve channels.
Welcome in my world :)
>Timur Tabi
>Linux kernel developer at Freescale
Sebastian
next prev parent reply other threads:[~2008-03-12 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 12:34 Using the loop feature of the DMA controller on MPC8544 DS Sebastian Siewior
2008-03-12 15:58 ` Timur Tabi
2008-03-12 17:20 ` Sebastian Siewior
2008-03-12 18:47 ` Timur Tabi
2008-03-12 20:44 ` Sebastian Siewior
2008-03-12 20:49 ` Timur Tabi
2008-03-12 21:15 ` Sebastian Siewior [this message]
2008-03-12 21:16 ` Timur Tabi
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=20080312211504.GC11426@Chamillionaire.breakpoint.cc \
--to=linuxppc-embedded@ml.breakpoint.cc \
--cc=linuxppc-embedded@ozlabs.org \
--cc=timur@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).