From: Vinod Koul <vinod.koul@intel.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org, dmaengine@vger.kernel.org,
gnurou@gmail.com, thierry.reding@gmail.com,
swarren@wwwdotorg.org, ldewangan@nvidia.com
Subject: Re: [PATCH] dmaengine: tegra210-adma: Add memcpy support
Date: Fri, 2 Sep 2016 16:55:32 +0530 [thread overview]
Message-ID: <20160902112532.GG9355@localhost> (raw)
In-Reply-To: <1472769797-31650-1-git-send-email-nicoleotsuka@gmail.com>
On Thu, Sep 01, 2016 at 03:43:16PM -0700, Nicolin Chen wrote:
> +#define ADMA_CH_CTRL_MODE_ONCE (1 << 8)
BIT(8)? You should change the existing ones too :)
> #define ADMA_CH_CTRL_MODE_CONTINUOUS (2 << 8)
> +#define ADMA_CH_CTRL_MODE_LINKED_LIST (4 << 8)
> #define ADMA_CH_CTRL_FLOWCTRL_EN BIT(1)
>
> #define ADMA_CH_CONFIG 0x28
> @@ -111,6 +115,7 @@ struct tegra_adma_desc {
> size_t buf_len;
> size_t period_len;
> size_t num_periods;
> + bool cyclic;
Okay, i think this should be a separate preparatory patch
> case DMA_DEV_TO_MEM:
> adma_dir = ADMA_CH_CTRL_DIR_AHUB2MEM;
> burst_size = fls(tdc->sconfig.src_maxburst);
> - ch_regs->config = ADMA_CH_CONFIG_TRG_BUF(desc->num_periods - 1);
> - ch_regs->ctrl = ADMA_CH_CTRL_RX_REQ(tdc->sreq_index);
> + ch_regs->config = ADMA_CH_CONFIG_TRG_BUF(num_periods - 1);
> + ch_regs->ctrl = ADMA_CH_CTRL_RX_REQ(tdc->sreq_index) |
> + ADMA_CH_CTRL_MODE_CONTINUOUS |
> + ADMA_CH_CTRL_FLOWCTRL_EN;
why is this changing?
> +static struct dma_async_tx_descriptor *tegra_adma_prep_dma_memcpy(
> + struct dma_chan *dc, dma_addr_t dest, dma_addr_t src,
> + size_t buf_len, unsigned long flags)
> +{
> + struct tegra_adma_chan *tdc = to_tegra_adma_chan(dc);
> + struct device *dev = dc->device->dev;
> + struct tegra_adma_desc *desc = NULL;
> +
> + dev_dbg(dev, "%s channel: %d src=0x%llx dst=0x%llx len=%zu\n",
> + __func__, dc->chan_id, (unsigned long long)src,
> + (unsigned long long)dest, buf_len);
> +
> + if (unlikely(!tdc || !buf_len))
> + return NULL;
> +
> + desc = kzalloc(sizeof(*desc), GFP_NOWAIT);
> + if (!desc)
> + return NULL;
> +
> + desc->num_periods = 1;
> + desc->buf_len = buf_len;
> + desc->period_len = buf_len;
should we perhaps rename this to length rather than period?
--
~Vinod
next prev parent reply other threads:[~2016-09-02 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 22:43 [PATCH] dmaengine: tegra210-adma: Add memcpy support Nicolin Chen
2016-09-01 22:43 ` [PATCH] dmaengine: tegra210-adma: Add some necessary dev_err() before error out Nicolin Chen
2016-09-02 11:25 ` Vinod Koul [this message]
2016-09-02 18:34 ` [PATCH] dmaengine: tegra210-adma: Add memcpy support Nicolin Chen
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=20160902112532.GG9355@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).