From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: devicetree@vger.kernel.org
Cc: robh+dt@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, andriy.shevchenko@linux.intel.com,
vinod.koul@intel.com, dmaengine@vger.kernel.org,
linux-snps-arc@lists.infradead.org,
Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Subject: [PATCH v2 0/2] DW DMAC: update device tree
Date: Fri, 18 Nov 2016 19:53:07 +0300 [thread overview]
Message-ID: <1479487989-24543-1-git-send-email-Eugeniy.Paltsev@synopsys.com> (raw)
It wasn't possible to enable some features like
memory-to-memory transfers or multi block transfers via DT.
It is fixed by these patches.
Changes for v2:
* I thought about is_memcpy DT property: all known devices, which
use DT for configuration, support memory-to-memory transfers.
So we don't need to read it from DT. So enable it by default,
if we read configuration from DT.
* Use "multi-block" instead of "hw-llp" name to be more clear.
* Move adding DT property and adding documentation for this
property to one patch.
Eugeniy Paltsev (2):
DW DMAC: enable memory-to-memory transfers support
DW DMAC: add multi-block property to device tree
Documentation/devicetree/bindings/dma/snps-dma.txt | 2 ++
drivers/dma/dw/core.c | 2 +-
drivers/dma/dw/platform.c | 11 +++++++++++
include/linux/platform_data/dma-dw.h | 4 ++--
4 files changed, 16 insertions(+), 3 deletions(-)
--
2.5.5
next reply other threads:[~2016-11-18 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 16:53 Eugeniy Paltsev [this message]
2016-11-18 16:53 ` [PATCH v2 1/2] DW DMAC: enable memory-to-memory transfers support Eugeniy Paltsev
2016-11-18 17:46 ` Andy Shevchenko
2016-11-18 16:53 ` [PATCH v2 2/2] DW DMAC: add multi-block property to device tree Eugeniy Paltsev
2016-11-18 17:43 ` Andy Shevchenko
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=1479487989-24543-1-git-send-email-Eugeniy.Paltsev@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).