From: andriy.shevchenko@linux.intel.com (Andy Shevchenko)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v3 2/2] DW DMAC: add multi-block property to device tree
Date: Fri, 18 Nov 2016 21:33:13 +0200 [thread overview]
Message-ID: <1479497593.22212.45.camel@linux.intel.com> (raw)
In-Reply-To: <1479496356-27834-3-git-send-email-Eugeniy.Paltsev@synopsys.com>
On Fri, 2016-11-18@22:12 +0300, Eugeniy Paltsev wrote:
> Several versions of DW DMAC have multi block transfers hardware
> support. Hardware support of multi block transfers is disabled
> by default if we use DT to configure DMAC and software emulation
> of multi block transfers used instead.
> Add multi-block property, so it is possible to enable hardware
> multi block transfers (if present) via DT.
>
> Switch from per device is_nollp variable to multi_block array
> to be able enable/disable multi block transfers separately per
> channel.
>
> Update DT documentation.
>
> Update existing platform data.
Kinda useless for commit message, but might go after --- delimiter.
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev at synopsys.com>
> ---
> ?Documentation/devicetree/bindings/dma/snps-dma.txt | 2 ++
> ?drivers/dma/dw/core.c??????????????????????????????| 2 +-
> ?drivers/dma/dw/platform.c??????????????????????????| 5 +++++
> ?drivers/tty/serial/8250/8250_lpss.c????????????????| 2 +-
> ?include/linux/platform_data/dma-dw.h???????????????| 4 ++--
> ?5 files changed, 11 insertions(+), 4 deletions(-)
> --- a/Documentation/devicetree/bindings/dma/snps-dma.txt
> +++ b/Documentation/devicetree/bindings/dma/snps-dma.txt
> @@ -27,6 +27,8 @@ Optional properties:
> ???that services interrupts for this device
> ?- is_private: The device channels should be marked as private and not
> for by the
> ???general purpose DMA channel allocator. False if not passed.
> +- multi-block: Multi block transfers supported by hardware per AHB
> master.
> +??0 (default): not supported, 1: supported.
> ?
> ?Example:
> ?
> diff --git a/drivers/dma/dw/core.c b/drivers/dma/dw/core.c
> index c2c0a61..f2a3d06 100644
> --- a/drivers/dma/dw/core.c
> +++ b/drivers/dma/dw/core.c
> @@ -1569,7 +1569,7 @@ int dw_dma_probe(struct dw_dma_chip *chip)
> ? (dwc_params >> DWC_PARAMS_MBLK_EN &
> 0x1) == 0;
> ? } else {
> ? dwc->block_size = pdata->block_size;
> - dwc->nollp = pdata->is_nollp;
> + dwc->nollp = pdata->multi_block[i];
You missed the point. You assign positive value to negative variable.
It's a bug. Have you tested this? How?
In case of positive property you have to update DTS. By the way, I'm
pretty sure that spare13xx boards has auto configuration enabled, though
it has to be checked with vendor (I assume you may have fast response
from them).
> ? }
> ? }
> ?
--
Andy Shevchenko <andriy.shevchenko at linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-11-18 19:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 19:12 [PATCH v3 0/2] DW DMAC: update device tree Eugeniy Paltsev
2016-11-18 19:12 ` [PATCH v3 1/2] DW DMAC: enable memory-to-memory transfers support Eugeniy Paltsev
2016-11-18 19:27 ` Andy Shevchenko
2016-11-18 19:12 ` [PATCH v3 2/2] DW DMAC: add multi-block property to device tree Eugeniy Paltsev
2016-11-18 19:33 ` Andy Shevchenko [this message]
2016-11-23 4:15 ` Vinod Koul
2016-11-21 13:53 ` Arnd Bergmann
2016-11-18 19:26 ` [PATCH v3 0/2] DW DMAC: update " Andy Shevchenko
2016-11-21 10:02 ` Alexey Brodkin
2016-11-21 10:37 ` Andy Shevchenko
2016-11-23 4: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=1479497593.22212.45.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-snps-arc@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