From: Vignesh Raghavendra <vigneshr-l0cyMroinI0@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Vignesh Raghavendra <vigneshr-l0cyMroinI0@public.gmane.org>,
<linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH 0/2] spi: spi-omap2-mcspi: Add DMA support for AM65x
Date: Tue, 4 Feb 2020 18:18:14 +0530 [thread overview]
Message-ID: <20200204124816.16735-1-vigneshr@ti.com> (raw)
This patch series adds DMA support for McSPI on AM65x.
First patch addresses a limitationn on AM65x where transfers have to be
<4K per DMA request and second patch handles possible EPROBE_DEFER when
requesting DMA channels
Vignesh Raghavendra (2):
spi: spi-omap2-mcspi: Handle DMA size restriction on AM65x
spi: spi-omap2-mcspi: Support probe deferral for DMA channels
drivers/spi/spi-omap2-mcspi.c | 103 +++++++++++-------
include/linux/platform_data/spi-omap2-mcspi.h | 1 +
2 files changed, 65 insertions(+), 39 deletions(-)
--
2.25.0
next reply other threads:[~2020-02-04 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 12:48 Vignesh Raghavendra [this message]
2020-02-04 12:48 ` [PATCH 1/2] spi: spi-omap2-mcspi: Handle DMA size restriction on AM65x Vignesh Raghavendra
2020-02-06 15:54 ` Applied "spi: spi-omap2-mcspi: Handle DMA size restriction on AM65x" to the spi tree Mark Brown
[not found] ` <20200204124816.16735-1-vigneshr-l0cyMroinI0@public.gmane.org>
2020-02-04 12:48 ` [PATCH 2/2] spi: spi-omap2-mcspi: Support probe deferral for DMA channels Vignesh Raghavendra
[not found] ` <20200204124816.16735-3-vigneshr-l0cyMroinI0@public.gmane.org>
2020-02-06 15:54 ` Applied "spi: spi-omap2-mcspi: Support probe deferral for DMA channels" 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=20200204124816.16735-1-vigneshr@ti.com \
--to=vigneshr-l0cymroini0@public.gmane.org \
--cc=broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-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).