From: Akhil R <akhilrajeev@nvidia.com>
To: <ldewangan@nvidia.com>, <jonathanh@nvidia.com>,
<vkoul@kernel.org>, <thierry.reding@gmail.com>,
<p.zabel@pengutronix.de>, <dmaengine@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH 0/3] Tegra GCPDMA: Add dma-channel-mask support
Date: Tue, 13 Sep 2022 21:22:48 +0530 [thread overview]
Message-ID: <20220913155251.59375-1-akhilrajeev@nvidia.com> (raw)
Read dma-channel-mask from device tree and register only the
specified channels. This is useful to reserve some channels for the
firmware.
Also update the channel number and interrupts to include all 32
channels. The current driver was using only 31 channels as one
channel was reserved for firmware. Now with this change, the driver
can align more to the actual hardware.
Akhil R (3):
dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA
arm64: tegra: Add dma-channel-mask in GPCDMA node
dmaengine: tegra: Add support for dma-channel-mask
.../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 7 +++-
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 4 ++-
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 4 ++-
arch/arm64/boot/dts/nvidia/tegra234.dtsi | 4 ++-
drivers/dma/tegra186-gpc-dma.c | 35 +++++++++++++++----
5 files changed, 44 insertions(+), 10 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-13 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 15:52 Akhil R [this message]
2022-09-13 15:52 ` [PATCH 1/3] dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA Akhil R
2022-09-14 14:20 ` Thierry Reding
2022-09-13 15:52 ` [PATCH 2/3] arm64: tegra: Add dma-channel-mask in GPCDMA node Akhil R
2022-09-13 15:52 ` [PATCH 3/3] dmaengine: tegra: Add support for dma-channel-mask Akhil R
2022-09-14 1:25 ` kernel test robot
2022-09-14 14:23 ` Thierry Reding
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=20220913155251.59375-1-akhilrajeev@nvidia.com \
--to=akhilrajeev@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=p.zabel@pengutronix.de \
--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