From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Marc Pignat <marc.pignat@hevs.ch>,
Andrew Victor <linux@maxim.org.za>,
kernel@avr32linux.org, linux-kernel@vger.kernel.org,
Remy Bohmer <linux@bohmer.net>,
Chip Coldwell <coldwell@redhat.com>
Subject: Re: [PATCH 6/6] atmel_serial: Add DMA support
Date: Wed, 23 Jan 2008 16:41:50 +0000 [thread overview]
Message-ID: <20080123164150.4b162826@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20080123161425.203a0159@dhcp-252-066.norway.atmel.com>
On Wed, 23 Jan 2008 16:14:25 +0100
Haavard Skinnemoen <hskinnemoen@atmel.com> wrote:
> On Wed, 23 Jan 2008 15:04:36 +0000
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> > > No, I think GFP_DMA is for legacy ISA DMA and other DMA controllers
> > > with addressing limitations. The PDC is capable of accessing the full
> > > 32-bit physical address space on both AT91 and AVR32, so no special DMA
> > > flags are needed.
> >
> > For kernel coherent DMA buffers use the dma_ API to allocate the memory.
>
> Yes, but since we're managing DMA coherency using the streaming DMA
> API, we don't really need coherent buffers, right?
Right.
Alan
prev parent reply other threads:[~2008-01-23 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 14:50 [PATCH v3 0/6] atmel_serial: Cleanups, irq handler splitup & DMA Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 1/6] atmel_serial: Clean up the code Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 2/6] atmel_serial: Use cpu_relax() when busy-waiting Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 3/6] atmel_serial: Use existing console options only if BRG is running Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 4/6] atmel_serial: Fix bugs in probe() error path and remove() Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 5/6] atmel_serial: Split the interrupt handler Haavard Skinnemoen
2008-01-22 14:50 ` [PATCH 6/6] atmel_serial: Add DMA support Haavard Skinnemoen
2008-01-22 16:52 ` Marc Pignat
2008-01-23 11:53 ` Haavard Skinnemoen
2008-01-23 12:30 ` Marc Pignat
2008-01-23 12:45 ` Haavard Skinnemoen
2008-01-23 13:18 ` Marc Pignat
2008-01-23 13:35 ` Haavard Skinnemoen
2008-01-23 13:52 ` Marc Pignat
2008-01-23 14:05 ` Haavard Skinnemoen
2008-01-23 15:04 ` Alan Cox
2008-01-23 15:14 ` Haavard Skinnemoen
2008-01-23 16:41 ` Alan Cox [this message]
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=20080123164150.4b162826@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=coldwell@redhat.com \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=linux@maxim.org.za \
--cc=marc.pignat@hevs.ch \
/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
all inboxes | Powered by JetHome®