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: [PATCH 0/3] Few Tegra210 ADMA fixes
Date: Mon, 30 Aug 2021 15:06:58 +0530 [thread overview]
Message-ID: <1630316221-9728-1-git-send-email-spujar@nvidia.com> (raw)
Following are the fixes in the series:
- Couple of minor fixes (non functional fixes)
- ADMA FIFO size fix: The slave ADMAIF channels have different default
FIFO sizes (ADMAIF FIFO is actually a ring buffer and it is divided
amongst all available channels). As per HW recommendation the sizes
should match with the corresponding ADMA channels to which ADMAIF
channel is mapped to at runtime. Thus program ADMA channel FIFO sizes
accordingly. Otherwise FIFO corruption is observed.
Sameer Pujar (3):
dmaengine: tegra210-adma: Re-order 'has_outstanding_reqs' member
dmaengine: tegra210-adma: Add description for 'adma_get_burst_config'
dmaengine: tegra210-adma: Override ADMA FIFO size
drivers/dma/tegra210-adma.c | 55 +++++++++++++++++++++++++++++++--------------
1 file changed, 38 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2021-08-30 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 9:36 Sameer Pujar [this message]
2021-08-30 9:36 ` [PATCH 1/3] dmaengine: tegra210-adma: Re-order 'has_outstanding_reqs' member Sameer Pujar
2021-08-30 9:37 ` [PATCH 2/3] dmaengine: tegra210-adma: Add description for 'adma_get_burst_config' Sameer Pujar
2021-08-30 9:37 ` [PATCH 3/3] dmaengine: tegra210-adma: Override ADMA FIFO size Sameer Pujar
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=1630316221-9728-1-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).