From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Vignesh R <vigneshr@ti.com>, Vinod Koul <vinod.koul@intel.com>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH RESEND v3] dma: omap-dma: add support for pause of non-cyclic transfers
Date: Thu, 13 Oct 2016 13:07:53 +0300 [thread overview]
Message-ID: <d1eb15e4-7d8f-e2c0-0e27-580d3e41ac4e@ti.com> (raw)
In-Reply-To: <46582bda-321f-47a6-d7d5-a27cbdd7f363@ti.com>
On 10/10/16 17:12, Peter Ujfalusi wrote:
> On 10/10/16 15:07, Vignesh R wrote:
>> From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>>
>> This DMA driver is used by 8250-omap on DRA7-evm. There is one
>> requirement that is to pause a transfer. This is currently used on the RX
>> side. It is possible that the UART HW aborted the RX (UART's RX-timeout)
>> but the DMA controller starts the transfer shortly after.
>> Before we can manually purge the FIFO we need to pause the transfer,
>> check how many bytes it already received and terminate the transfer
>> without it making any progress.
>>
>> From testing on the TX side it seems that it is possible that we invoke
>> pause once the transfer has completed which is indicated by the missing
>> CCR_ENABLE bit but before the interrupt has been noticed. In that case the
>> interrupt will come even after disabling it.
>>
>> The AM572x manual says that we have to wait for the CCR_RD_ACTIVE &
>> CCR_WR_ACTIVE bits to be gone before programming it again here is the
>> drain loop. Also it looks like without the drain the TX-transfer makes
>> sometimes progress.
>>
>> One note: The pause + resume combo is broken because after resume the
>> the complete transfer will be programmed again. That means the already
>> transferred bytes (until the pause event) will be sent again. This is
>> currently not important for my UART user because it does only pause +
>> terminate.
>
> Acked-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Can you resend the patch with corrected subject line?
dmaengine: omap-dma: ....
--
Péter
next prev parent reply other threads:[~2016-10-13 10:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 12:07 Vignesh R
2016-10-10 14:12 ` Peter Ujfalusi
2016-10-13 10:07 ` Peter Ujfalusi [this message]
2016-10-14 5:01 ` Vignesh R
2016-10-14 5:00 ` [PATCH v4] dmaengine: " Vignesh R
2016-10-18 14:52 ` 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=d1eb15e4-7d8f-e2c0-0e27-580d3e41ac4e@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=vigneshr@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
Powered by JetHome