[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48D3BEB2.3060902@freescale.com>
Date: Fri, 19 Sep 2008 10:01:06 -0500
From: Timur Tabi <timur@...escale.com>
To: "linux-os (Dick Johnson)" <linux-os@...logic.com>
CC: Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
Dan Williams <dan.j.williams@...el.com>,
lkml <linux-kernel@...r.kernel.org>
Subject: Re: dmaengine.c: question about device_alloc_chan_resources
linux-os (Dick Johnson) wrote:
> On Fri, 19 Sep 2008, Timur Tabi wrote:
>
>> 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
>
> The hardware on the PC/AT machines won't allow you to
> reserve a specific channel and program it as you see fit,
> because there are two devices, one for the low DMA
> channels and another for the high ones.
True, but that restriction doesn't apply to all processors. So we could still
provide the capability of reserving channels for those systems where it makes
sense. This is the case for the DMA controller I'm working with.
My solution for now is to permanently reserve the channels I need. This is safe
and probably okay, because there are 6 other channels still available. However,
if there was a mechanism where I could dynamically reserve channels, I would use it.
> The information transmitted in this message is confidential and may be privileged.
Really?
--
Timur Tabi
Linux kernel developer at Freescale
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists