From: Vinod Koul <vkoul@kernel.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: dmaengine@vger.kernel.org, dan.j.williams@intel.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/2] dmaengine: ti: omap-dma: Improved polling support
Date: Mon, 29 Jul 2019 12:05:15 +0530 [thread overview]
Message-ID: <20190729063515.GE12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <20190716082459.1222-1-peter.ujfalusi@ti.com>
On 16-07-19, 11:24, Peter Ujfalusi wrote:
> 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.
Applied, thanks
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-29 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 8:24 [PATCH v2 0/2] dmaengine: ti: omap-dma: Improved polling support Peter Ujfalusi
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 ` Vinod Koul [this message]
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=20190729063515.GE12733@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--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=peter.ujfalusi@ti.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).