From: Vinod Koul <vkoul@kernel.org>
To: Robin Gong <yibin.gong@nxp.com>
Cc: dan.j.williams@intel.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, fabio.estevam@nxp.com,
linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
kernel@pengutronix.de, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: [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)
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
next reply other threads:[~2018-07-10 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 15:33 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 16:23 [v1,3/4] dmaengine: imx-sdma: support dmatest Robin Gong
2018-07-11 6:37 Robin Gong
2018-07-11 6:53 Sascha Hauer
2018-07-11 7:14 Robin Gong
2018-07-11 7:19 Vinod Koul
2018-07-11 8:16 Robin Gong
2018-07-11 8:58 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=20180710153326.GG3219@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=yibin.gong@nxp.com \
/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