From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>,
linux-spi@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v5 0/2] spi: pxa2xx: Adjust DMA burst size per platform
Date: Tue, 19 Mar 2019 17:48:41 +0200 [thread overview]
Message-ID: <20190319154843.74684-1-andriy.shevchenko@linux.intel.com> (raw)
On some platforms DMA burst size is not the same as hard coded default
Fix the driver to support them.
In v5:
- correct subject in cover letter
- correct the patches that have been sent
In v4:
- fix s/master/controller/g
In v3:
- drop threshold print since it's easy to calculate constant (Jarkko)
- split one more unrelated change to a separate patch,
but independent from this series (Jarkko)
In v2:
- drop unrelated changes (Jarkko, Robert)
- don't include Robert's tag due to changes in the patch
Andy Shevchenko (2):
spi: pxa2xx: Introduce DMA burst size support
spi: pxa2xx: Debug print DMA burst size
drivers/spi/spi-pxa2xx-dma.c | 4 +++-
drivers/spi/spi-pxa2xx-pci.c | 4 ++++
drivers/spi/spi-pxa2xx.c | 4 ++++
include/linux/spi/pxa2xx_spi.h | 1
4 files changed, 12 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-03-19 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 15:48 Andy Shevchenko [this message]
2019-03-19 15:48 ` [PATCH v5 1/2] spi: pxa2xx: Introduce DMA burst size support Andy Shevchenko
2019-03-20 7:19 ` Jarkko Nikula
2019-03-20 17:30 ` Applied "spi: pxa2xx: Introduce DMA burst size support" to the spi tree Mark Brown
2019-03-19 15:48 ` [PATCH v5 2/2] spi: pxa2xx: Debug print DMA burst size Andy Shevchenko
2019-03-20 7:19 ` Jarkko Nikula
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=20190319154843.74684-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robert.jarzmik@free.fr \
/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).