From: Peter Hurley <peter@hurleysoftware.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
nsekhar@ti.com, linux-omap@vger.kernel.org,
linux-serial@vger.kernel.org, john.ogness@linutronix.de,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH] dma: omap-dma: add support for pause of non-cyclic transfers
Date: Fri, 07 Aug 2015 10:46:06 -0400 [thread overview]
Message-ID: <55C4C4AE.9080004@hurleysoftware.com> (raw)
In-Reply-To: <20150807132551.GO7576@n2100.arm.linux.org.uk>
On 08/07/2015 09:25 AM, Russell King - ARM Linux wrote:
> On Fri, Aug 07, 2015 at 03:22:56PM +0200, Sebastian Andrzej Siewior wrote:
>> For TX-transfers, I would need to update the start-address so the
>> transfers begins where it stopped. However based on your concern I
>> can't really assume that the position reported by the HW is the correct
>> one.
>
> Exactly - I don't believe that existing OMAP DMA hardware can ever support
> pausing a mem-to-device transfer without data loss as you have no idea
> how many bytes have been prefetched by the DMA, and therefore you have
> no idea how many bytes to unwind the hardware position. It gets worse
> than that when you have to cross into the previous descriptor. It's
> really not nice.
>
> So, disallowing pause for mem-to-device is entirely reasonable given the
> data loss implications.
Thanks for adding your hard-won knowledge to this discussion, Russell.
This saves us a bunch of wasted effort trying to fix x_char with DMA
(and TCSANOW termios changes and throttling).
Regards,
Peter Hurley
next prev parent reply other threads:[~2015-08-07 14:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 8:41 [PATCH] dma: omap-dma: add support for pause of non-cyclic transfers Sebastian Andrzej Siewior
2015-08-07 9:44 ` Peter Ujfalusi
2015-08-07 10:36 ` Sebastian Andrzej Siewior
2015-08-07 11:44 ` Peter Ujfalusi
2015-08-07 12:47 ` Sebastian Andrzej Siewior
2015-08-07 13:22 ` Russell King - ARM Linux
2015-08-07 13:42 ` Sebastian Andrzej Siewior
2015-08-07 13:57 ` Russell King - ARM Linux
2015-08-07 15:08 ` Peter Hurley
2015-08-07 15:29 ` Russell King - ARM Linux
2015-08-07 15:44 ` Sebastian Andrzej Siewior
2015-08-07 16:39 ` Russell King - ARM Linux
2015-08-07 17:23 ` Peter Hurley
2015-08-07 17:42 ` Russell King - ARM Linux
2015-08-07 16:07 ` Peter Hurley
2015-08-07 16:20 ` Sebastian Andrzej Siewior
2015-08-07 16:35 ` Russell King - ARM Linux
2015-08-07 16:33 ` Russell King - ARM Linux
2015-08-07 18:21 ` Peter Hurley
2015-08-07 18:32 ` Russell King - ARM Linux
2015-08-08 1:41 ` Peter Hurley
2015-08-08 9:07 ` Russell King - ARM Linux
2015-08-07 10:55 ` Russell King - ARM Linux
2015-08-07 12:35 ` Sebastian Andrzej Siewior
2015-08-07 13:17 ` Russell King - ARM Linux
2015-08-07 13:22 ` Sebastian Andrzej Siewior
2015-08-07 13:25 ` Russell King - ARM Linux
2015-08-07 14:46 ` Peter Hurley [this message]
2015-08-07 17:55 ` Greg KH
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=55C4C4AE.9080004@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=bigeasy@linutronix.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=vinod.koul@intel.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).