From: fisaksen@baylibre.com (Frode Isaksen)
To: linux-arm-kernel@lists.infradead.org
Subject: Enable DMA for daVinci SPI controller
Date: Fri, 10 Feb 2017 16:29:36 +0100 [thread overview]
Message-ID: <1486740584-17875-1-git-send-email-fisaksen@baylibre.com> (raw)
Enable DMA for the daVinci SPI using the SPI framework DMA mapping
function. Also, add some extra options to the spi-loopback-test
module to catch errors caused by many SG entries.
This has been tested using spidev_test, spi-loopback-test and
mounting and read/write UBIFS volume over SPI flash.
In-Reply-To:
next reply other threads:[~2017-02-10 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:29 Frode Isaksen [this message]
2017-02-10 15:29 ` [PATCH 1/8] spi: davinci: Use SPI framework to handle DMA mapping Frode Isaksen
2017-02-13 11:30 ` Mark Brown
2017-02-10 15:29 ` [PATCH 2/8] spi: davinci: enable DMA when channels are defined in DT Frode Isaksen
2017-02-13 11:32 ` Mark Brown
2017-02-10 15:29 ` [PATCH 3/8] spi: davinci: limit the transfer size if DMA enabled Frode Isaksen
2017-02-10 19:07 ` Kevin Hilman
2017-02-13 5:59 ` Sekhar Nori
2017-02-14 11:27 ` Frode Isaksen
2017-02-14 15:29 ` Sekhar Nori
2017-02-14 16:40 ` Frode Isaksen
2017-03-21 22:02 ` Peter Ujfalusi
2017-03-22 11:11 ` Frode Isaksen
2017-03-22 11:35 ` Sekhar Nori
2017-03-22 12:20 ` Peter Ujfalusi
2017-03-22 13:30 ` Frode Isaksen
2017-02-10 15:29 ` [PATCH 4/8] spi: davinci: flush caches when performing DMA Frode Isaksen
2017-02-10 15:29 ` [PATCH 5/8] spi: davinci: do not use DMA if transfer length is less than 16 Frode Isaksen
2017-02-10 15:29 ` [PATCH 6/8] spi: loopback-test: set HW loopback mode if loopback set Frode Isaksen
2017-02-10 15:29 ` [PATCH 7/8] spi: loopback-test: add option to use vmalloc'ed buffers Frode Isaksen
2017-02-10 15:29 ` [PATCH 8/8] spi: loopback-test: limit length to spi_max_transfer_size() Frode Isaksen
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=1486740584-17875-1-git-send-email-fisaksen@baylibre.com \
--to=fisaksen@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).