linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Eugeniy.Paltsev@synopsys.com (Eugeniy Paltsev)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH v10 03/11] dmaengine: dw: override LLP support if asked in platform data
Date: Tue, 16 Aug 2016 13:21:06 +0000	[thread overview]
Message-ID: <1471353666.1562.3.camel@synopsys.com> (raw)
In-Reply-To: <1471017716-44893-4-git-send-email-andriy.shevchenko@linux.intel.com>

On Fri, 2016-08-12@19:01 +0300, Andy Shevchenko wrote:
> There are at least two known devices, e.g. DMA controller found on
> ARC AXS101
> SDP board, that have LLP register and no multi block transfer support
> at the
> same time.
> 
> Override autodetection by user provided data.
> 
> Reported-by: Eugeniy Paltsev <Eugeniy.Paltsev at synopsys.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko at linux.intel.com>
> ---
> ?drivers/dma/dw/core.c????????????????| 6 +-----
> ?include/linux/platform_data/dma-dw.h | 2 ++
> ?2 files changed, 3 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/dma/dw/core.c b/drivers/dma/dw/core.c
> index 80e7421..da18b18 100644
> --- a/drivers/dma/dw/core.c
> +++ b/drivers/dma/dw/core.c
> @@ -1571,11 +1571,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;
> -
> -			/* Check if channel supports multi block
> transfer */
> -			channel_writel(dwc, LLP,
> DWC_LLP_LOC(0xffffffff));
> -			dwc->nollp = DWC_LLP_LOC(channel_readl(dwc,
> LLP)) == 0;
> -			channel_writel(dwc, LLP, 0);
> +			dwc->nollp = pdata->is_nollp;
> ?		}
> ?	}
> ?
> diff --git a/include/linux/platform_data/dma-dw.h
> b/include/linux/platform_data/dma-dw.h
> index 4636c93..5f0e11e 100644
> --- a/include/linux/platform_data/dma-dw.h
> +++ b/include/linux/platform_data/dma-dw.h
> @@ -40,6 +40,7 @@ struct dw_dma_slave {
> ? * @is_private: The device channels should be marked as private and
> not for
> ? *	by the general purpose DMA channel allocator.
> ? * @is_memcpy: The device channels do support memory-to-memory
> transfers.
> + * @is_nollp: The device channels does not support multi block
> transfers.
> ? * @chan_allocation_order: Allocate channels starting from 0 or 7
> ? * @chan_priority: Set channel priority increasing from 0 to 7 or 7
> to 0.
> ? * @block_size: Maximum block size supported by the controller
> @@ -51,6 +52,7 @@ struct dw_dma_platform_data {
> ?	unsigned int	nr_channels;
> ?	bool		is_private;
> ?	bool		is_memcpy;
> +	bool		is_nollp;
> ?#define CHAN_ALLOCATION_ASCENDING	0	/* zero to seven
> */
> ?#define CHAN_ALLOCATION_DESCENDING	1	/* seven to zero
> */
> ?	unsigned char	chan_allocation_order;

Looks good to me.
Reviewed-by: Eugeniy Platsev <Eugeniy.Paltsev at synopsys.com>

           reply	other threads:[~2016-08-16 13:21 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1471017716-44893-4-git-send-email-andriy.shevchenko@linux.intel.com>]

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=1471353666.1562.3.camel@synopsys.com \
    --to=eugeniy.paltsev@synopsys.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;
as well as URLs for NNTP newsgroup(s).