From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: Marc Pignat <marc.pignat@hevs.ch>
Cc: 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 13:45:53 +0100 [thread overview]
Message-ID: <20080123134553.144ca487@dhcp-252-066.norway.atmel.com> (raw)
In-Reply-To: <200801231330.32777.marc.pignat@hevs.ch>
On Wed, 23 Jan 2008 13:30:32 +0100
Marc Pignat <marc.pignat@hevs.ch> wrote:
> On Wednesday 23 January 2008, Haavard Skinnemoen wrote:
> > Right. Does that mean I shouldn't Cc it on patches?
> extract from the linux-arm-kernel 'Mailing List Etiquette':
> 10. Cross-posting between linux-arm* lists and other lists. [[40]rmk]
> Please do not do this. Subscribers on other lists may not be
> subscribed to the linux-arm lists, so when they try to reply to
> such a message, they will receive a bounce. This is deemed by
> others to be rude behaviour on the part of the person who
> originally cross-posted.
Ok, sorry about that.
> > Dunno. I suppose the PDC_BUFFER_SIZE and/or PDC_RX_TIMEOUT definitions
> > needs to be revisited? Chip?
> I just think there is no need to warn, even if definitions are sub-optimal.
I agree, so I replaced it with a comment.
> > I don't really understand why the buffer size depends on the cache line
> > size either. Why don't we just set it to something nice and large, like
> > 512 (actually 1024 since there are two buffers), and be done with it?
> Probably for dma safety/performance, The PDC buffer start should be aligned to
> cache line, and the size be a multiple of cache line size.
Ok, but then any power of two larger than the cache line size should be
fine, assuming kmalloc() returns a properly aligned buffer.
Other than that, I can't see any reason why a platform with 64 byte
cache lines should need larger buffers than one with 32 byte cache
lines.
> > And while we're at it, might as well move the SUPPORT_PDC definition
> > into Kconfig where it belongs...
> For me there is no need to disbable pdc support once working. PDC can be
> enabled/disabled in the board setup code. -> simply remove this definition.
There are still issues with the DMA code that the PIO code doesn't
have. So I think it should be selectable until we can sort out the
error/break handling.
Haavard
next prev parent reply other threads:[~2008-01-23 12: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 [this message]
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
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=20080123134553.144ca487@dhcp-252-066.norway.atmel.com \
--to=hskinnemoen@atmel.com \
--cc=coldwell@redhat.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;
as well as URLs for NNTP newsgroup(s).