From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vkoul@kernel.org>
Cc: <dan.j.williams@intel.com>, <dmaengine@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>
Subject: [PATCH v2 0/2] dmaengine: ti: omap-dma: Improved polling support
Date: Tue, 16 Jul 2019 11:24:57 +0300 [thread overview]
Message-ID: <20190716082459.1222-1-peter.ujfalusi@ti.com> (raw)
Hi,
changes since v1:
- New preparation cleanup patch
- Simplified code for the main patch to be easier to read
This series fine-tunes the omap-dma polled memcpy support to be inline with how
the EDMA driver is handling it.
The polled completion can be tested by applying:
https://patchwork.kernel.org/patch/10966499/
and run the dmatest with polled = 1 on boards where sDMA is used.
Or boot up any dra7 family device with display enabled. The workaround for DMM
errata i878 uses polled DMA memcpy.
Regards,
Peter
---
Peter Ujfalusi (2):
dmaengine: ti: omap-dma: Readability cleanup in omap_dma_tx_status()
dmaengine: ti: omap-dma: Improved memcpy polling support
drivers/dma/ti/omap-dma.c | 52 +++++++++++++++++++++++++--------------
1 file changed, 33 insertions(+), 19 deletions(-)
--
Peter
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2019-07-16 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 8:24 Peter Ujfalusi [this message]
2019-07-16 8:24 ` [PATCH v2 1/2] dmaengine: ti: omap-dma: Readability cleanup in omap_dma_tx_status() Peter Ujfalusi
2019-07-16 8:24 ` [PATCH v2 2/2] dmaengine: ti: omap-dma: Improved memcpy polling support Peter Ujfalusi
2019-07-25 13:37 ` Vinod Koul
2019-07-25 14:07 ` Peter Ujfalusi
2019-07-29 6:16 ` Vinod Koul
2019-07-29 6:35 ` [PATCH v2 0/2] dmaengine: ti: omap-dma: Improved " Vinod Koul
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=20190716082459.1222-1-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).