From: Jon Hunter <jonathanh@nvidia.com>
To: Peter Robinson <pbrobinson@gmail.com>,
linux-tegra@vger.kernel.org, Vinod Koul <vkoul@kernel.org>
Cc: Thierry Reding <treding@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH v2 2/2] dmaengine: tegra210-adma: Update dependency to ARCH_TEGRA
Date: Wed, 17 Jan 2024 14:56:38 +0000 [thread overview]
Message-ID: <9404e4e2-e7ad-47e0-be24-56982febf353@nvidia.com> (raw)
In-Reply-To: <20240112093310.329642-2-pbrobinson@gmail.com>
Adding Vinod ...
On 12/01/2024 09:32, Peter Robinson wrote:
> Update the architecture dependency to be the generic Tegra
> because the driver works on the four latest Tegra generations
> not just T210, if you build a kernel with a specific
> ARCH_TEGRA_xxx_SOC option that excludes 210 you don't get
> this driver.
>
> Fixes: 433de642a76c9 ("dmaengine: tegra210-adma: add support for Tegra186/Tegra194")
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> Cc: Jon Hunter <jonathanh@nvidia.com>
> Cc: Thierry Reding <treding@nvidia.com>
> Cc: Sameer Pujar <spujar@nvidia.com>
> Cc: Laxman Dewangan <ldewangan@nvidia.com>
> ---
>
> v2: fix spelling of option
>
> drivers/dma/Kconfig | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> index 70ba506dabab5..de6eb370d485d 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -629,16 +629,16 @@ config TEGRA20_APB_DMA
>
> config TEGRA210_ADMA
> tristate "NVIDIA Tegra210 ADMA support"
> - depends on (ARCH_TEGRA_210_SOC || COMPILE_TEST)
> + depends on (ARCH_TEGRA || COMPILE_TEST)
> select DMA_ENGINE
> select DMA_VIRTUAL_CHANNELS
> help
> - Support for the NVIDIA Tegra210 ADMA controller driver. The
> - DMA controller has multiple DMA channels and is used to service
> - various audio clients in the Tegra210 audio processing engine
> - (APE). This DMA controller transfers data from memory to
> - peripheral and vice versa. It does not support memory to
> - memory data transfer.
> + Support for the NVIDIA Tegra210/Tegra186/Tegra194/Tegra234 ADMA
> + controller driver. The DMA controller has multiple DMA channels
> + and is used to service various audio clients in the Tegra210
> + audio processing engine (APE). This DMA controller transfers
> + data from memory to peripheral and vice versa. It does not
> + support memory to memory data transfer.
>
> config TIMB_DMA
> tristate "Timberdale FPGA DMA support"
Thanks!
Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
Jon
--
nvpublic
next prev parent reply other threads:[~2024-01-17 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:32 [PATCH v2 1/2] bus: tegra-aconnect: Update dependency to ARCH_TEGRA Peter Robinson
2024-01-12 9:32 ` [PATCH v2 2/2] dmaengine: tegra210-adma: " Peter Robinson
2024-01-17 14:56 ` Jon Hunter [this message]
2024-01-19 15:37 ` Thierry Reding
2024-01-17 14:55 ` [PATCH v2 1/2] bus: tegra-aconnect: " Jon Hunter
2024-01-19 15:37 ` Thierry Reding
2024-01-22 7:59 ` Sameer Pujar
2024-01-22 16:25 ` (subset) " 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=9404e4e2-e7ad-47e0-be24-56982febf353@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=spujar@nvidia.com \
--cc=treding@nvidia.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