public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: vkoul@kernel.org (Vinod)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 3/4] dmaengine: imx-sdma: support dmatest
Date: Tue, 10 Jul 2018 21:03:26 +0530	[thread overview]
Message-ID: <20180710153326.GG3219@vkoul-mobl> (raw)
In-Reply-To: <1531239793-11781-4-git-send-email-yibin.gong@nxp.com>

On 11-07-18, 00:23, Robin Gong wrote:
> dmatest(memcpy) will never call dmaengine_slave_config before prep,

and that should have been a hint to you that you should not expect that

> so jobs in dmaengine_slave_config need to be moved into somewhere
> before device_prep_dma_memcpy. Besides, dmatest never setup chan
> ->private as other common case like uart/audio/spi will always setup
> chan->private. Here check it to judge if it's dmatest case and do
> jobs in slave_config.

and you should not do anything for dmatest. Supporting it means memcpy
implementation is not correct :)

> 
> Signed-off-by: Robin Gong <yibin.gong@nxp.com>
> ---
>  drivers/dma/imx-sdma.c | 37 ++++++++++++++++++++++++++++---------
>  1 file changed, 28 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
> index ed2267d..48f3749 100644
> --- a/drivers/dma/imx-sdma.c
> +++ b/drivers/dma/imx-sdma.c
> @@ -1222,10 +1222,36 @@ static int sdma_alloc_chan_resources(struct dma_chan *chan)
>  {
>  	struct sdma_channel *sdmac = to_sdma_chan(chan);
>  	struct imx_dma_data *data = chan->private;
> +	struct imx_dma_data default_data;
>  	int prio, ret;
>  
> -	if (!data)
> -		return -EINVAL;
> +	ret = clk_enable(sdmac->sdma->clk_ipg);
> +	if (ret)
> +		return ret;
> +	ret = clk_enable(sdmac->sdma->clk_ahb);
> +	if (ret)
> +		goto disable_clk_ipg;
> +	/*
> +	 * dmatest(memcpy) will never call dmaengine_slave_config before prep,
> +	 * so jobs in dmaengine_slave_config need to be moved into somewhere
> +	 * before device_prep_dma_memcpy. Besides, dmatest never setup chan
> +	 * ->private as other common cases like uart/audio/spi will setup
> +	 * chan->private always. Here check it to judge if it's dmatest case
> +	 * and do jobs in slave_config.
> +	 */
> +	if (!data) {
> +		dev_warn(sdmac->sdma->dev, "dmatest is running?\n");

why is that a warning!

> +		sdmac->word_size  =  sdmac->sdma->dma_device.copy_align;
> +		default_data.priority = 2;
> +		default_data.peripheral_type = IMX_DMATYPE_MEMORY;
> +		default_data.dma_request = 0;
> +		default_data.dma_request2 = 0;
> +		data = &default_data;
> +
> +		sdma_config_ownership(sdmac, false, true, false);
> +		sdma_get_pc(sdmac, IMX_DMATYPE_MEMORY);
> +		sdma_load_context(sdmac);
> +	}

this needs to be default for memcpy

-- 
~Vinod

  reply	other threads:[~2018-07-10 15:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10 16:23 [PATCH v1 0/4] add memcpy support for sdma Robin Gong
2018-07-10 16:23 ` [PATCH v1 1/4] dmaengine: imx-sdma: add memcpy interface Robin Gong
2018-07-10 15:29   ` Vinod
2018-07-11  5:34     ` Robin Gong
2018-07-11  7:12       ` Vinod
2018-07-11  6:24   ` Sascha Hauer
2018-07-11  6:56     ` Robin Gong
2018-07-11  7:01       ` Sascha Hauer
2018-07-11  7:05         ` Robin Gong
2018-07-11  7:08           ` Sascha Hauer
2018-07-10 16:23 ` [PATCH v1 2/4] dmaengine: imx-sdma: add check_bd_buswidth() to kill the dulicated code Robin Gong
2018-07-10 15:31   ` Vinod
2018-07-11  5:36     ` Robin Gong
2018-07-11  6:32   ` Sascha Hauer
2018-07-10 16:23 ` [PATCH v1 3/4] dmaengine: imx-sdma: support dmatest Robin Gong
2018-07-10 15:33   ` Vinod [this message]
2018-07-11  6:37     ` Robin Gong
2018-07-11  6:53       ` s.hauer at pengutronix.de
2018-07-11  7:14         ` Robin Gong
2018-07-11  7:19         ` Vinod
2018-07-11  8:16           ` Robin Gong
2018-07-11  8:58             ` Vinod
2018-07-10 16:23 ` [PATCH v1 4/4] ARM: configs: imx_v6_v7_defconfig: add DMATEST support Robin Gong

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=20180710153326.GG3219@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=linux-arm-kernel@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