linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>,
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	<alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>,
	<cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>,
	<geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>,
	Nicolas Ferre
	<nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
Subject: [PATCH 0/5] spi: atmel: enhance the DMA handling
Date: Thu, 24 Nov 2016 12:24:56 +0100	[thread overview]
Message-ID: <cover.1479985886.git.nicolas.ferre@atmel.com> (raw)

Use the dummy buffer handling and DMA mapping core infrastructure to simplify
spi-atmel driver.
By using these frameworks we also fix the use of any kind of memory with
dmaengine. This work was triggered by issues encountered while using UBI/UBIFS
on a serial flash.

Some good ideas of this series have been inspired by spi-rspi.c and commits by
Geert Uytterhoeven.

I have a side question still: is the is_dma_mapped tag still used and considered into
the core spi routines or is it always the driver itself that have to deal with
it (so how to do with the can_dma() routine)?

Cyrille Pitchen (1):
  spi: atmel: Use SPI core DMA mapping framework

Nicolas Ferre (4):
  spi: atmel: trivial: move info banner to latest probe action
  spi: atmel: Use core SPI_MASTER_MUST_[RT]X handling
  spi: atmel: trivial: remove unused fields in DMA structure
  spi: atmel: remove the use of private channel fields

 drivers/spi/spi-atmel.c | 268 ++++++++++++++++++------------------------------
 1 file changed, 98 insertions(+), 170 deletions(-)

-- 
2.9.0

--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2016-11-24 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 11:24 Nicolas Ferre [this message]
2016-11-24 11:24 ` [PATCH 1/5] spi: atmel: trivial: move info banner to latest probe action Nicolas Ferre
     [not found]   ` <e259bb1c87e32c67295747f868f8684c1e929d68.1479985886.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2016-11-25 13:05     ` Mark Brown
2016-11-25 13:10     ` Applied "spi: atmel: trivial: move info banner to latest probe action" to the spi tree Mark Brown
2016-11-24 11:24 ` [PATCH 2/5] spi: atmel: Use core SPI_MASTER_MUST_[RT]X handling Nicolas Ferre
     [not found]   ` <86f613a36c2e7db07c3ec7d0b8a650cdb9222b32.1479985886.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2016-11-25 13:10     ` Applied "spi: atmel: Use core SPI_MASTER_MUST_[RT]X handling" to the spi tree Mark Brown
2016-11-24 11:24 ` [PATCH 3/5] spi: atmel: Use SPI core DMA mapping framework Nicolas Ferre
2016-11-25 13:10   ` Applied "spi: atmel: Use SPI core DMA mapping framework" to the spi tree Mark Brown
     [not found] ` <cover.1479985886.git.nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2016-11-24 11:25   ` [PATCH 4/5] spi: atmel: trivial: remove unused fields in DMA structure Nicolas Ferre
2016-11-25 13:10     ` Applied "spi: atmel: trivial: remove unused fields in DMA structure" to the spi tree Mark Brown
2016-11-24 11:25 ` [PATCH 5/5] spi: atmel: remove the use of private channel fields Nicolas Ferre
2016-11-25 13:10   ` Applied "spi: atmel: remove the use of private channel fields" to the spi tree Mark Brown

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=cover.1479985886.git.nicolas.ferre@atmel.com \
    --to=nicolas.ferre-aife0yeh4naavxtiumwx3w@public.gmane.org \
    --cc=alexandre.belloni-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org \
    --cc=geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).