From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Viresh Kumar <viresh.linux@gmail.com>,
Vinod Koul <vinod.koul@intel.com>,
linux-kernel@vger.kernel.org,
spear-devel <spear-devel@list.st.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v4 0/4] dw_dmac: return actual residue value
Date: Fri, 25 Jan 2013 11:47:59 +0200 [thread overview]
Message-ID: <1359107283-5274-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
The patch series is targeted for getting proper residue value.
Since v3:
- split dwc_get_residue() from dwc_tx_status and improve locking there
- patch 1/4 "dw_dmac: remove unnecessary tx_list field in dw_dma_chan" was
amended a bit to simplify patch 4/4
Since v2:
- get rid of dwc_update_residue(): for soft LLP mode we assign residue in
dwc_do_start() and decrease it at each interrupt. In the middle of transfer
we will return that result substracted by amount of sent bytes
Since v1:
- everything is rewritten to address Viresh's and Vinod's comments.
Andy Shevchenko (4):
dw_dmac: remove unnecessary tx_list field in dw_dma_chan
dw_dmac: introduce total_len field in struct dw_desc
dw_dmac: fill individual length of descriptor
dw_dmac: return proper residue value
drivers/dma/dw_dmac.c | 82 +++++++++++++++++++++++++++++++++++++-------
drivers/dma/dw_dmac_regs.h | 3 +-
2 files changed, 71 insertions(+), 14 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-01-25 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:47 Andy Shevchenko [this message]
2013-01-25 9:48 ` [PATCH v4 1/4] dw_dmac: remove unnecessary tx_list field in dw_dma_chan Andy Shevchenko
2013-01-25 9:48 ` [PATCH v4 2/4] dw_dmac: introduce total_len field in struct dw_desc Andy Shevchenko
2013-01-25 9:48 ` [PATCH v4 3/4] dw_dmac: fill individual length of descriptor Andy Shevchenko
2013-01-25 9:48 ` [PATCH v4 4/4] dw_dmac: return proper residue value Andy Shevchenko
2013-01-25 9:55 ` [PATCH v4 0/4] dw_dmac: return actual " Viresh Kumar
2013-01-28 12:06 ` 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=1359107283-5274-1-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=vinod.koul@intel.com \
--cc=viresh.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.