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: Thu, 18 Sep 2008 09:49:24 -0500 [thread overview]
Message-ID: <48D26A74.4030104@freescale.com> (raw)
In-Reply-To: <20080918164535.5e9f77a8@hskinnemo-gx745.norway.atmel.com>
Haavard Skinnemoen wrote:
> I guess so. What would be even more simple is to simply prevent other
> clients from taking a channel once someone has acked it, which would be
> perfect for my purposes, but perhaps not everyone else's...
I'm not clear on how your driver works, but doesn't it run continuous tests on
all channels all the time? If so, wouldn't your proposal prevent other drivers
from ever getting a DMA channel?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-18 14:49 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 [this message]
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
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=48D26A74.4030104@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox