From: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
To: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"vireshk@kernel.org" <vireshk@kernel.org>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: [PATCH v3 0/3] dmaengine: DW DMAC: split pdata to hardware properties
Date: Wed, 2 Nov 2016 11:55:08 +0000 [thread overview]
Message-ID: <1478087707.2603.7.camel@synopsys.com> (raw)
In-Reply-To: <1477670402-23943-1-git-send-email-Eugeniy.Paltsev@synopsys.com>
Hi Andy,
Could you possibly tell me your ideas about these changes?
Thanks.
On Fri, 2016-10-28 at 18:59 +0300, Eugeniy Paltsev wrote:
> This series is to address a proposal by Andy in these threads:
> http://www.spinics.net/lists/dmaengine/msg11506.html
> http://www.spinics.net/lists/dmaengine/msg11541.html
> Split platform data to actual hardware properties, and platform
> quirks.
> Now we able to use quirks and hardware properties separately from
> different sources (pdata, device tree or autoconfig registers)
>
> Changes for v3:
> - Split changes to separate patches.
> - Add "DW_DMA_IS_LLP_SUPPORTED" flag and get rid of "dwc->nollp"
> as separate variable.
> - Make "dw_dma_slave" documentation comments more clear about
> quirks.
> "is_memcpy" and "is_private" are quirks, "is_nollp" is regular
> pdata property.
>
> Eugeniy Paltsev (3):
> dmaengine: DW DMAC: split pdata to hardware properties and platform
> quirks
> dmaengine: DW DMAC: convert to unified device property API
> dmaengine: DW DMAC: move "nollp" to "dwc->flags"
>
> drivers/dma/dw/core.c | 34 +++++++++++++----------
> drivers/dma/dw/platform.c | 53 +++++++++++++++++++-------
> ----------
> drivers/dma/dw/regs.h | 2 +-
> include/linux/platform_data/dma-dw.h | 5 ++++
> 4 files changed, 54 insertions(+), 40 deletions(-)
>
--
Paltsev Eugeniy
next prev parent reply other threads:[~2016-11-02 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 15:59 [PATCH v3 0/3] dmaengine: DW DMAC: split pdata to hardware properties Eugeniy Paltsev
2016-10-28 16:00 ` [PATCH v3 1/3] dmaengine: DW DMAC: split pdata to hardware properties and platform quirks Eugeniy Paltsev
2016-10-28 16:00 ` [PATCH v3 2/3] dmaengine: DW DMAC: convert to unified device property API Eugeniy Paltsev
2016-10-28 16:00 ` [PATCH v3 3/3] dmaengine: DW DMAC: move "nollp" to "dwc->flags" Eugeniy Paltsev
2016-10-28 16:15 ` [PATCH v3 0/3] dmaengine: DW DMAC: split pdata to hardware properties Andy Shevchenko
2016-11-02 11:55 ` Eugeniy Paltsev [this message]
2016-11-07 13:55 ` Andy Shevchenko
2016-11-08 12:22 ` Eugeniy Paltsev
2016-11-08 13:36 ` Andy Shevchenko
2016-11-10 16:28 ` Eugeniy Paltsev
2016-11-11 11:05 ` 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=1478087707.2603.7.camel@synopsys.com \
--to=eugeniy.paltsev@synopsys.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=vinod.koul@intel.com \
--cc=vireshk@kernel.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).