All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: dmaengine.c: question about device_alloc_chan_resources
Date: Fri, 19 Sep 2008 09:34:40 -0500	[thread overview]
Message-ID: <48D3B880.3070607@freescale.com> (raw)
In-Reply-To: <20080919132544.533ab7d0@hskinnemo-gx745.norway.atmel.com>

Haavard Skinnemoen wrote:

> Yes, or maybe provide an interface for simply requesting a channel
> without having to register any callbacks. 

I could use this feature.  The sound drivers for our MPC8610 processor use DMA,
but the drivers need to control the DMA hardware directly, so I can't use
dmaengine.  I would like to be able to just reserve the channels and program
them as I see fit.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2008-09-19 14:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-16 21:30 dmaengine.c: question about device_alloc_chan_resources Timur Tabi
2008-09-17 22:36 ` Dan Williams
2008-09-18 14:13   ` Timur Tabi
2008-09-18 14:28     ` Haavard Skinnemoen
2008-09-18 14:31       ` Timur Tabi
2008-09-18 14:45         ` Haavard Skinnemoen
2008-09-18 14:49           ` Timur Tabi
2008-09-18 15:00             ` Haavard Skinnemoen
2008-09-19  4:20           ` Dan Williams
2008-09-19 11:25             ` Haavard Skinnemoen
2008-09-19 14:34               ` Timur Tabi [this message]
2008-09-19 14:50                 ` linux-os (Dick Johnson)
2008-09-19 15:01                   ` Timur Tabi
2008-09-19 15:28                   ` Alan Cox
2008-09-20 23:00                 ` Dan Williams
2008-09-21  9:26                   ` Haavard Skinnemoen
2008-09-21 19:50                     ` Guennadi Liakhovetski
2008-09-22  7:44                       ` Haavard Skinnemoen

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=48D3B880.3070607@freescale.com \
    --to=timur@freescale.com \
    --cc=dan.j.williams@intel.com \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.