From: Sameer Pujar <spujar@nvidia.com>
To: <vkoul@kernel.org>, <jonathanh@nvidia.com>,
<ldewangan@nvidia.com>, <thierry.reding@gmail.com>
Cc: <dmaengine@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Sameer Pujar <spujar@nvidia.com>
Subject: [RESEND PATCH 2/3] dmaengine: tegra210-adma: Add description for 'adma_get_burst_config'
Date: Wed, 15 Sep 2021 21:37:04 +0530 [thread overview]
Message-ID: <1631722025-19873-3-git-send-email-spujar@nvidia.com> (raw)
In-Reply-To: <1631722025-19873-1-git-send-email-spujar@nvidia.com>
Trivial change to add description for 'adma_get_burst_config' in chip
data structure.
Fixes: 433de642a76c ("dmaengine: tegra210-adma: add support for Tegra186/Tegra194")
Signed-off-by: Sameer Pujar <spujar@nvidia.com>
---
drivers/dma/tegra210-adma.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/dma/tegra210-adma.c b/drivers/dma/tegra210-adma.c
index caf200e..03f9776 100644
--- a/drivers/dma/tegra210-adma.c
+++ b/drivers/dma/tegra210-adma.c
@@ -73,6 +73,7 @@ struct tegra_adma;
/*
* struct tegra_adma_chip_data - Tegra chip specific data
+ * @adma_get_burst_config: Function callback used to set DMA burst size.
* @global_reg_offset: Register offset of DMA global register.
* @global_int_clear: Register offset of DMA global interrupt clear.
* @ch_req_tx_shift: Register offset for AHUB transmit channel select.
--
2.7.4
next prev parent reply other threads:[~2021-09-15 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 16:07 [RESEND PATCH 0/3] Few Tegra210 ADMA fixes Sameer Pujar
2021-09-15 16:07 ` [RESEND PATCH 1/3] dmaengine: tegra210-adma: Re-order 'has_outstanding_reqs' member Sameer Pujar
2021-09-17 9:47 ` Jon Hunter
2021-09-15 16:07 ` Sameer Pujar [this message]
2021-09-17 9:47 ` [RESEND PATCH 2/3] dmaengine: tegra210-adma: Add description for 'adma_get_burst_config' Jon Hunter
2021-09-15 16:07 ` [RESEND PATCH 3/3] dmaengine: tegra210-adma: Override ADMA FIFO size Sameer Pujar
2021-09-17 9:45 ` Jon Hunter
2021-09-27 6:20 ` [RESEND PATCH 0/3] Few Tegra210 ADMA fixes Sameer Pujar
2021-10-04 15:49 ` Sameer Pujar
2021-10-05 6:33 ` Vinod Koul
2021-10-18 4:03 ` 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=1631722025-19873-3-git-send-email-spujar@nvidia.com \
--to=spujar@nvidia.com \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).