From: Franklin S Cooper Jr <fcooper@ti.com>
To: tony@atomide.com, robh+dt@kernel.org, broonie@kernel.org,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
andy.shevchenko@gmail.com, robert.jarzmik@free.fr,
nsekhar@ti.com
Cc: Franklin S Cooper Jr <fcooper@ti.com>
Subject: [RFC] [PATCH v3 0/4] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping
Date: Thu, 7 Jul 2016 12:17:47 -0500 [thread overview]
Message-ID: <1467911871-4508-1-git-send-email-fcooper@ti.com> (raw)
This patchset switches omap2-mcspi from handling DMA mapping internally to
using the mechanism built into the SPI framework.
However, this is slightly complex since some OMAP SoCs have a quirk that
needs to be handled. In the driver on certain OMAP SOCs if certain
conditions are met the DMA should transfer one or two less elements
when reading from the SPI. The remaining bytes are read in CPU mode.
Sg_split is used to implement this quirk without altering the original
sgl.
Note: The first patch looks to already have been accepted.
V2 changes:
Save page_link value if page_link doesn't point to chained sg_list
v3 changes:
Switch from using custom sg_table clone function to sg_split that already
exist within the kernel.
Franklin S Cooper Jr (4):
spi: omap2-mcspi: Add comments for RX only DMA buffer workaround
spi: spi-omap2-mcspi: Select SPI_SPLIT
spi: omap2-mcspi: Use the SPI framework to handle DMA mapping
ARM: dts: am335x-icev2: Add SPI based NOR
arch/arm/boot/dts/am335x-icev2.dts | 39 ++++++++++
drivers/spi/Kconfig | 1 +
drivers/spi/spi-omap2-mcspi.c | 145 ++++++++++++++++++-------------------
3 files changed, 109 insertions(+), 76 deletions(-)
--
2.7.0
next reply other threads:[~2016-07-07 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 17:17 Franklin S Cooper Jr [this message]
[not found] ` <1467911871-4508-1-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-07 17:17 ` [RFC] [PATCH v3 1/4] spi: omap2-mcspi: Add comments for RX only DMA buffer workaround Franklin S Cooper Jr
[not found] ` <1467911871-4508-2-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08 8:46 ` Mark Brown
2016-07-07 17:17 ` [RFC] [PATCH v3 3/4] spi: omap2-mcspi: Use the SPI framework to handle DMA mapping Franklin S Cooper Jr
[not found] ` <1467911871-4508-4-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08 8:49 ` Applied "spi: omap2-mcspi: Use the SPI framework to handle DMA mapping" to the spi tree Mark Brown
2016-07-07 17:17 ` [RFC] [PATCH v3 4/4] ARM: dts: am335x-icev2: Add SPI based NOR Franklin S Cooper Jr
2016-07-07 17:17 ` [RFC] [PATCH v3 2/4] spi: spi-omap2-mcspi: Select SPI_SPLIT Franklin S Cooper Jr
2016-07-07 17:33 ` Randy Dunlap
[not found] ` <1467911871-4508-3-git-send-email-fcooper-l0cyMroinI0@public.gmane.org>
2016-07-08 8:49 ` Applied "spi: omap2-mcspi: Select SPI_SPLIT" to the spi tree Mark Brown
2016-07-08 8:54 ` Sekhar Nori
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=1467911871-4508-1-git-send-email-fcooper@ti.com \
--to=fcooper@ti.com \
--cc=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robert.jarzmik@free.fr \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.com \
/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).