From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: "Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH 1/2] dw_dmac: set CAP_PRIVATE capability for DW DMA controller
Date: Wed, 1 Apr 2009 07:04:40 +0200 [thread overview]
Message-ID: <20090401070440.326f6e7f@hcegtvedt> (raw)
In-Reply-To: <129600E5E5FB004392DDC3FB599660D790F8C3EB@irsmsx504.ger.corp.intel.com>
On Tue, 31 Mar 2009 15:01:49 +0100
"Sosnowski, Maciej" <maciej.sosnowski@intel.com> wrote:
> Hans-Christian Egtvedt wrote:
> > This patch adds the private capability for the DW DMA controller.
> > This allows the DMA controller to do other DMA transfers than
> > memory-to-memory. For example when the DMA controller is used by
> > peripherals to transfer data between memory and peripheral.
> >
> > Signed-off-by: Hans-Christian Egtvedt
> > <hans-christian.egtvedt@atmel.com> ---
> > drivers/dma/dw_dmac.c | 1 +
> > 1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/dma/dw_dmac.c b/drivers/dma/dw_dmac.c
> > index a97c07e..1c5e31d 100644
> > --- a/drivers/dma/dw_dmac.c
> > +++ b/drivers/dma/dw_dmac.c
> > @@ -994,6 +994,7 @@ static int __init dw_probe(struct
> > platform_device *pdev) channel_clear_bit(dw, MASK.DST_TRAN,
> > dw->all_chan_mask); channel_clear_bit(dw, MASK.ERROR,
> > dw->all_chan_mask);
> >
> > + dma_cap_set(DMA_PRIVATE, dw->dma.cap_mask);
> > dma_cap_set(DMA_MEMCPY, dw->dma.cap_mask);
> > dma_cap_set(DMA_SLAVE, dw->dma.cap_mask);
> > dw->dma.dev = &pdev->dev;
>
> Hi Hans,
>
> Adding Dan...
>
> Please note that this way you permenently exclude the device from
> public use. If that's your intent that's fine.
>
No, my intention was to be able to use dma_request_channel in the ALSA
driver I was working on in parallel.
> Remember however that you can leave the device generally non-private
> and attempt as needed to allocate a channel for exclusive usage by
> dma_request_channel()
>
The weird part was that when testing this, the dma_request_channel()
would not return any channel before DMA_PRIVATE flag was set. I think I
did this some time ago, I can do a retest with the current 2.6.29 and
see how it behaves.
> - it would set DMA_PRIVATE flag if private channel candidate has been
> found.
>
Which I think was the reason I added the private flag.
--
Best regards,
Hans-Christian Egtvedt
next prev parent reply other threads:[~2009-04-01 5:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 11:35 Hans-Christian Egtvedt
2009-03-24 11:35 ` [PATCH 2/2] dw_dmac: add cyclic API to DW DMA driver Hans-Christian Egtvedt
2009-03-31 14:02 ` Sosnowski, Maciej
2009-03-31 14:03 ` Sosnowski, Maciej
2009-04-01 5:10 ` Hans-Christian Egtvedt
2009-04-01 8:28 ` Haavard Skinnemoen
2009-04-01 9:11 ` Hans-Christian Egtvedt
2009-04-01 13:28 ` [PATCH v2 1/1] " Hans-Christian Egtvedt
2009-04-01 13:39 ` Haavard Skinnemoen
2009-04-01 13:47 ` [PATCH v3 " Hans-Christian Egtvedt
2009-04-01 13:52 ` Haavard Skinnemoen
2009-04-01 22:46 ` Dan Williams
2009-04-01 15:08 ` Sosnowski, Maciej
2009-03-31 14:01 ` [PATCH 1/2] dw_dmac: set CAP_PRIVATE capability for DW DMA controller Sosnowski, Maciej
2009-04-01 5:04 ` Hans-Christian Egtvedt [this message]
2009-04-01 5:30 ` Dan Williams
2009-04-01 8:33 ` Hans-Christian Egtvedt
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=20090401070440.326f6e7f@hcegtvedt \
--to=hans-christian.egtvedt@atmel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.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
Powered by JetHome