From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>,
ldewangan@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
Subject: Re: [PATCH v2 3/3] dmaengine: tegra: Add support for dma-channel-mask
Date: Fri, 23 Sep 2022 11:08:55 +0100 [thread overview]
Message-ID: <8d15c575-a490-e1ed-7e97-5a5cdea0925f@nvidia.com> (raw)
In-Reply-To: <20220919112559.58195-4-akhilrajeev@nvidia.com>
On 19/09/2022 12:25, Akhil R wrote:
> Add support for dma-channel-mask so that only the specified channels
> are used. This helps to reserve some channels for the firmware.
>
> This was initially achieved by limiting the channel number to 31 in
> the driver and adjusting the register address to skip channel0 which
> was reserved for a firmware. Now, with this change, the driver can
> align more to the actual hardware which has 32 channels.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> ---
> drivers/dma/tegra186-gpc-dma.c | 37 +++++++++++++++++++++++++++-------
> 1 file changed, 30 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/dma/tegra186-gpc-dma.c b/drivers/dma/tegra186-gpc-dma.c
> index fa9bda4a2bc6..1d1180db6d4e 100644
> --- a/drivers/dma/tegra186-gpc-dma.c
> +++ b/drivers/dma/tegra186-gpc-dma.c
> @@ -161,7 +161,10 @@
> #define TEGRA_GPCDMA_BURST_COMPLETION_TIMEOUT 5000 /* 5 msec */
>
> /* Channel base address offset from GPCDMA base address */
> -#define TEGRA_GPCDMA_CHANNEL_BASE_ADD_OFFSET 0x20000
> +#define TEGRA_GPCDMA_CHANNEL_BASE_ADDR_OFFSET 0x10000
Why did this value change? There is no mention in the commit message. If
this was incorrect before, then this needs to be a separate patch and
tagged with the appropriate fixes tag so that this can be picked up for
stable.
Thanks
Jon
--
nvpublic
next prev parent reply other threads:[~2022-09-23 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 11:25 [PATCH v2 0/3] Tegra GCPDMA: Add dma-channel-mask support Akhil R
2022-09-19 11:25 ` [PATCH v2 1/3] dt-bindings: dmaengine: Add dma-channel-mask to Tegra GPCDMA Akhil R
2022-09-23 10:06 ` Jon Hunter
2022-09-19 11:25 ` [PATCH v2 2/3] arm64: tegra: Add dma-channel-mask in GPCDMA node Akhil R
2022-09-23 10:06 ` Jon Hunter
2022-09-19 11:25 ` [PATCH v2 3/3] dmaengine: tegra: Add support for dma-channel-mask Akhil R
2022-09-23 10:08 ` Jon Hunter [this message]
2022-09-23 10:17 ` Akhil R
2022-09-23 10:50 ` Jon Hunter
2022-09-23 11:09 ` Akhil R
2022-09-23 11:45 ` Jon Hunter
2022-09-23 16:22 ` Akhil R
2022-09-23 10:50 ` Jon Hunter
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=8d15c575-a490-e1ed-7e97-5a5cdea0925f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=dmaengine@vger.kernel.org \
--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