From: Greg KH <greg@kroah.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: 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,
Russell King <rmk+kernel@arm.linux.org.uk>,
Peter Ujfalusi <peter.ujfalusi@ti.com>
Subject: Re: [PATCH] dma: omap-dma: add support for pause of non-cyclic transfers
Date: Fri, 7 Aug 2015 10:55:02 -0700 [thread overview]
Message-ID: <20150807175502.GA10282@kroah.com> (raw)
In-Reply-To: <1438936917-7254-1-git-send-email-bigeasy@linutronix.de>
On Fri, Aug 07, 2015 at 10:41:57AM +0200, Sebastian Andrzej Siewior wrote:
> 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.
>
> Cc: <stable@vger.kernel.org>
You don't get a "add support" patch into the stable tree unless it's a
trivial device id or quirk table addition, please go re-read
Documentation/stable_kernel_rules.txt
thanks,
greg k-h
prev parent reply other threads:[~2015-08-07 17:55 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
2015-08-07 17:55 ` Greg KH [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=20150807175502.GA10282@kroah.com \
--to=greg@kroah.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=nsekhar@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=rmk+kernel@arm.linux.org.uk \
--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