public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Viresh Kumar <vireshk@kernel.org>,
	dmaengine@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2 1/7] dmaengine: dw: Add missed multi-block support for iDMA 32-bit
Date: Wed, 5 Dec 2018 23:42:02 +0530	[thread overview]
Message-ID: <20181205181202.GV2847@vkoul-mobl> (raw)
In-Reply-To: <20181205162818.45112-2-andriy.shevchenko@linux.intel.com>

On 05-12-18, 18:28, Andy Shevchenko wrote:
> Intel integrated DMA 32-bit support multi-block transfers.
> Add missed setting to the platform data.
> 
> Fixes: f7c799e950f9 ("dmaengine: dw: we do support Merrifield SoC in PCI mode")
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: stable@vger.kernel.org

How is this a stable material? It would improve performance by using multi
blocks but given the fact that this is used for slow peripherals, do you
really see a user impact?

> ---
>  drivers/dma/dw/pci.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/dma/dw/pci.c b/drivers/dma/dw/pci.c
> index 7778ed705a1a..313ba10c6224 100644
> --- a/drivers/dma/dw/pci.c
> +++ b/drivers/dma/dw/pci.c
> @@ -25,6 +25,7 @@ static struct dw_dma_platform_data mrfld_pdata = {
>  	.block_size = 131071,
>  	.nr_masters = 1,
>  	.data_width = {4},
> +	.multi_block = {1, 1, 1, 1, 1, 1, 1, 1},
>  };
>  
>  static int dw_pci_probe(struct pci_dev *pdev, const struct pci_device_id *pid)
> -- 
> 2.19.2

-- 
~Vinod

  reply	other threads:[~2018-12-05 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181205162818.45112-1-andriy.shevchenko@linux.intel.com>
2018-12-05 16:28 ` [PATCH v2 1/7] dmaengine: dw: Add missed multi-block support for iDMA 32-bit Andy Shevchenko
2018-12-05 18:12   ` Vinod Koul [this message]
2018-12-07 13:32     ` 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=20181205181202.GV2847@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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