From: viresh.kumar@st.com (viresh kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 7/7] dmaengine/dw_dmac: implement pause and resume in dwc_control
Date: Tue, 19 Apr 2011 14:40:07 +0530 [thread overview]
Message-ID: <4DAD516F.50901@st.com> (raw)
In-Reply-To: <20110419085514.GG2820@pulham.picochip.com>
On 04/19/2011 02:25 PM, Jamie Iles wrote:
>From the Synopsys datasheet it looks to me like pausing by clearing the
> channel enable bit could cause data to be lost. I think you need to set
> the CH_SUSP bit and wait for the FIFO_EMPTY flag to go high then disable
> the channel.
Yes, Previously i looked at some other doc of dwc and couldn't find this info.
But now found it in datasheet. Will correct and resend it.
--
viresh
next prev parent reply other threads:[~2011-04-19 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 8:32 [PATCH V2 0/7] dmaengine/dw_dmac updates Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 1/7] dmaengine/dw_dmac: Replace spin_lock_bh with irqsave variants Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 2/7] dmaengine/dw_dmac: Enable resubmission from callback routine Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 3/7] dmaengine/dw_dmac: call dwc_descriptor_complete from dwc_control with lock held Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 4/7] dmaengine/dw_dmac: don't call callback routine in case dmaengine_terminate_all() is called Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 5/7] dmaengine/dw_dmac: set residue as total len in dwc_tx_status if status is !DMA_SUCCESS Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 6/7] dmaengine/dw_dmac: Divide one sg to many desc, if sg len is greater than DWC_MAX_COUNT Viresh Kumar
2011-04-19 8:32 ` [PATCH V2 7/7] dmaengine/dw_dmac: implement pause and resume in dwc_control Viresh Kumar
2011-04-19 8:55 ` Jamie Iles
2011-04-19 9:10 ` viresh kumar [this message]
2011-04-19 10:12 ` [PATCH V2 7/7 resend] " Viresh Kumar
2011-04-26 3:46 ` [PATCH V2 0/7] dmaengine/dw_dmac updates Koul, Vinod
2011-04-26 5:36 ` viresh kumar
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=4DAD516F.50901@st.com \
--to=viresh.kumar@st.com \
--cc=linux-arm-kernel@lists.infradead.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).