public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Robin Gong <yibin.gong@nxp.com>
To: broonie@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	festevam@gmail.com, robin.murphy@arm.com,
	matthias.schiffer@ew.tq-group.com
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	kernel@pengutronix.de, linux-spi@vger.kernel.org
Subject: [PATCH v1 RFC 0/2] introduce fallback to pio in spi core
Date: Thu, 11 Jun 2020 20:58:28 +0800	[thread overview]
Message-ID: <1591880310-1813-1-git-send-email-yibin.gong@nxp.com> (raw)

Introudce fallback pio way at spi core level so that the tx/rx buffer
mapped by spi core for dma could be unmap and fallback pio again. Hence no
need the below patch where 'dma_sync_sg_for_devic' to sync fresh data back
into 'device' memory and sync to 'cpu' again in spi core.
https://www.spinics.net/lists/arm-kernel/msg812236.html

If you want to use this fallback feature, please set 'master->flags' with
SPI_MASTER_FALLBACK and add 'master->fallback' checking in your can_dma()
to ensure it can fallback to pio.

Robin Gong (2):
  spi: introduce fallback to pio
  spi: spi-imx: add fallback feature

 drivers/spi/spi-imx.c   | 23 +++++------------------
 drivers/spi/spi.c       | 11 +++++++++++
 include/linux/spi/spi.h |  4 ++++
 3 files changed, 20 insertions(+), 18 deletions(-)

-- 
2.7.4


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2020-06-11  4:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 12:58 Robin Gong [this message]
2020-06-11 12:58 ` [PATCH v1 RFC 1/2] spi: introduce fallback to pio Robin Gong
2020-06-11 13:40   ` Mark Brown
2020-06-12  2:18     ` Robin Gong
2020-06-12 10:13       ` Mark Brown
2020-06-12 13:48         ` Robin Gong
2020-06-12 14:16           ` Mark Brown
2020-06-14 13:04             ` Robin Gong
2020-06-15  7:19               ` Vinod Koul
2020-06-15  8:59                 ` Robin Gong
2020-06-15 11:25                   ` Vinod Koul
2020-06-16  3:05                     ` Robin Gong
2020-06-15 12:35               ` Mark Brown
2020-06-15 13:35                 ` Robin Gong
2020-06-15 13:39                   ` Mark Brown
2020-06-15 14:18                     ` Robin Gong
2020-06-15 14:36                       ` Mark Brown
2020-06-15 14:53                         ` Robin Gong
2020-06-15 14:55                           ` Mark Brown
2020-06-16  2:03                             ` Robin Gong
2020-06-16  9:59                               ` Mark Brown
2020-06-16 10:13                                 ` Robin Gong
2020-06-16 10:26                                   ` Mark Brown
2020-06-16 12:29                                     ` Robin Gong
2020-06-11 12:58 ` [PATCH v1 RFC 2/2] spi: spi-imx: add fallback feature Robin Gong

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=1591880310-1813-1-git-send-email-yibin.gong@nxp.com \
    --to=yibin.gong@nxp.com \
    --cc=broonie@kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=robin.murphy@arm.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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