From: Frank Mori Hess <fmh6jj@gmail.com>
To: Vinod Koul <vinod.koul@linaro.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
r.baldyga@hackerion.com, Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Linux Samsung SOC <linux-samsung-soc@vger.kernel.org>
Subject: Re: Revert "dmaengine: pl330: add DMA_PAUSE feature"
Date: Mon, 21 May 2018 20:56:20 -0400 [thread overview]
Message-ID: <CAJz5OpdW7ZgX_K-+6H_mkHhzRf1_km8Usf306_HrnD7qCztdpw@mail.gmail.com> (raw)
In-Reply-To: <20180521091626.GB14654@vkoul-mobl>
On Mon, May 21, 2018 at 5:16 AM, Vinod Koul <vinod.koul@linaro.org> wrote:
>>
>> I understand the residue can't be read after terminate, that's why
>> reading the residue is step 2 in pause/residue/terminate. My question
>> was whether the entire sequence pause/residue/terminate taken as a
>> whole can or cannot lose data. Saying that individual steps can or
>> can't lose data is not enough, context is required. The key point is
>> whether pause flushes in-flight data to its destination or not. If it
>> does, and our residue is accurate, the terminate cannot cause data
>> loss. If pause doesn't flush, an additional step of flush_sync as
>> Lars suggested is required. So pause/flush_sync/residue/terminate
>> would be the safe sequence that cannot lose data.
>
> I wouldn't use cannot, shouldn't would be better here as it depends on HW and
> where all data has been buffered and if it can be flushed or not.
>
> Have you checked if pl330 supports such flushing?
It does not, at least in the context of pausing. The dma-330 DMAEND
instruction flushes in-flight data to its destination, and there are
read/write barrier instructions also, but none of them can be injected
on the fly into a running dma thread. DMAKILL can be, but it discards
in-flight data. Currently, if an 8250 serial driver uses the pl330
for rx dma, the result is possible data loss/corruption. If there was
a stronger pause capability, call it "cmd_sync_pause" which guaranteed
flushing of in-flight data to its destination and accurate residue
reading when paused, then the 8250 serial driver could check for
"cmd_sync_pause" and reject dma drivers that do not have that
capability. pl330.c would not advertise cmd_sync_pause. I don't know
if other dmaengine hardware would be able to support cmd_sync_pause or
not, I'm mostly just familiar with the pl330. The ep93xx_dma.c driver
for example has a m2p_hw_synchronize function which seems to do a
flush.
--
Frank
next prev parent reply other threads:[~2018-05-22 0:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 21:50 [PATCH] Revert "dmaengine: pl330: add DMA_PAUSE feature" Frank Mori Hess
2018-05-02 4:32 ` Vinod Koul
2018-05-02 14:37 ` Frank Mori Hess
2018-05-03 9:01 ` Vinod Koul
2018-05-03 16:35 ` Vinod Koul
[not found] ` <CGME20180508090407eucas1p13713284c2d3f5aa5c66f8d136be683c1@eucas1p1.samsung.com>
2018-05-08 9:04 ` Marek Szyprowski
2018-05-08 14:36 ` Frank Mori Hess
2018-05-09 6:59 ` Vinod Koul
2018-05-09 13:19 ` Marek Szyprowski
2018-05-09 17:48 ` Frank Mori Hess
2018-05-10 8:31 ` Marek Szyprowski
2018-05-10 16:04 ` Frank Mori Hess
2018-05-11 12:57 ` Marek Szyprowski
2018-05-11 15:57 ` Frank Mori Hess
2018-05-15 6:21 ` Vinod
2018-05-15 12:24 ` Marek Szyprowski
2018-05-15 13:45 ` Vinod
2018-05-15 15:50 ` Frank Mori Hess
2018-05-17 4:19 ` Vinod Koul
2018-05-17 16:20 ` Frank Mori Hess
2018-05-17 17:22 ` Lars-Peter Clausen
2018-05-18 19:01 ` Frank Mori Hess
2018-05-18 4:03 ` Vinod
2018-05-18 6:28 ` Marek Szyprowski
2018-05-18 7:21 ` Vinod
2018-05-29 5:17 ` Marek Szyprowski
2018-05-29 7:09 ` Vinod
2018-05-18 18:56 ` Frank Mori Hess
2018-05-21 9:16 ` Vinod Koul
2018-05-22 0:56 ` Frank Mori Hess [this message]
2018-05-22 3:37 ` Vinod Koul
2018-05-22 14:27 ` Frank Mori Hess
2018-05-23 5:39 ` Vinod
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=CAJz5OpdW7ZgX_K-+6H_mkHhzRf1_km8Usf306_HrnD7qCztdpw@mail.gmail.com \
--to=fmh6jj@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=r.baldyga@hackerion.com \
--cc=vinod.koul@linaro.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).