From: Andrew Morton <akpm@linux-foundation.org>
To: Anders Larsen <al@alarsen.net>
Cc: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>,
Ian McDonnell <ian@brightstareng.com>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
Nicolas Pitre <nico@fluxnic.net>,
linux-kernel@vger.kernel.org,
Iwo Mergler <iwo@call-direct.com.au>,
linux-mtd@lists.infradead.org,
Matthias Kaehlcke <matthias@kaehlcke.net>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] Fix Oops with Atmel SPI
Date: Fri, 21 May 2010 12:01:06 -0700 [thread overview]
Message-ID: <20100521120106.d955c78b.akpm@linux-foundation.org> (raw)
In-Reply-To: <1274267100l.1747l.1l@i-dmzi_al.realan.de>
On Wed, 19 May 2010 13:05:00 +0200
Anders Larsen <al@alarsen.net> wrote:
> On 2010-04-22 00:24:10, Andrew Morton wrote:
> > Finally.. Wouldn't it be better to just fix the atmel SPI driver so
> > that it doesn't barf when handed vmalloc'ed memory? Who do we ridicule
> > about that? <checks, adds cc>
>
> You mean something like this instead?
That looks simple enough. How do we get it tested, changelogged and
merged up? Haavard, can you please take a look?
> diff --git a/drivers/spi/atmel_spi.c b/drivers/spi/atmel_spi.c
> index c4e0442..a9ad5e8 100644
> --- a/drivers/spi/atmel_spi.c
> +++ b/drivers/spi/atmel_spi.c
> @@ -352,16 +352,30 @@ atmel_spi_dma_map_xfer(struct atmel_spi *as, struct spi_transfer *xfer)
>
> xfer->tx_dma = xfer->rx_dma = INVALID_DMA_ADDRESS;
> if (xfer->tx_buf) {
> - xfer->tx_dma = dma_map_single(dev,
> - (void *) xfer->tx_buf, xfer->len,
> - DMA_TO_DEVICE);
> + if (is_vmalloc_addr(xfer->tx_buf))
> + xfer->tx_dma = dma_map_page(dev,
> + vmalloc_to_page(xfer->tx_buf),
> + (unsigned long)xfer->tx_buf & (PAGE_SIZE-1),
> + xfer->len,
> + DMA_TO_DEVICE);
> + else
> + xfer->tx_dma = dma_map_single(dev,
> + (void *) xfer->tx_buf, xfer->len,
> + DMA_TO_DEVICE);
> if (dma_mapping_error(dev, xfer->tx_dma))
> return -ENOMEM;
> }
> if (xfer->rx_buf) {
> - xfer->rx_dma = dma_map_single(dev,
> - xfer->rx_buf, xfer->len,
> - DMA_FROM_DEVICE);
> + if (is_vmalloc_addr(xfer->rx_buf))
> + xfer->rx_dma = dma_map_page(dev,
> + vmalloc_to_page(xfer->rx_buf),
> + (unsigned long)xfer->rx_buf & (PAGE_SIZE-1),
> + xfer->len,
> + DMA_FROM_DEVICE);
> + else
> + xfer->rx_dma = dma_map_single(dev,
> + xfer->rx_buf, xfer->len,
> + DMA_FROM_DEVICE);
> if (dma_mapping_error(dev, xfer->rx_dma)) {
> if (xfer->tx_buf)
> dma_unmap_single(dev,
>
next prev parent reply other threads:[~2010-05-21 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 11:31 [PATCH] Fix Oops with Atmel SPI Anders Larsen
2010-04-14 7:30 ` Iwo Mergler
2010-04-14 7:57 ` Anders Larsen
2010-04-14 18:13 ` Kevin Cernekee
2010-04-15 7:32 ` Iwo Mergler
2010-04-21 22:24 ` Andrew Morton
2010-05-19 11:05 ` Anders Larsen
2010-05-21 19:01 ` Andrew Morton [this message]
2010-05-24 15:09 ` Ian McDonnell
2010-05-28 9:27 ` Haavard Skinnemoen
2010-04-27 12:57 ` Artem Bityutskiy
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=20100521120106.d955c78b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Artem.Bityutskiy@nokia.com \
--cc=al@alarsen.net \
--cc=dwmw2@infradead.org \
--cc=hskinnemoen@atmel.com \
--cc=ian@brightstareng.com \
--cc=iwo@call-direct.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias@kaehlcke.net \
--cc=nico@fluxnic.net \
/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).