From: Robin Murphy <robin.murphy@arm.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ARM_DMA350 should depend on ARM/ARM64
Date: Wed, 23 Apr 2025 11:59:30 +0100 [thread overview]
Message-ID: <b1f19b31-3535-4bb5-bcef-6f17ad2a0ee6@arm.com> (raw)
In-Reply-To: <50dbaf4ce962fa7ed0208150ca987e3083da39ec.1745345400.git.geert+renesas@glider.be>
On 2025-04-22 7:11 pm, Geert Uytterhoeven wrote:
> The Arm DMA-350 controller is only present on Arm-based SoCs.
Do you know that for sure? I certainly don't. This is a licensable,
self-contained DMA controller IP with no relationship whatsoever to any
particular CPU ISA - our other system IP products have turned up in the
wild paired with non-Arm CPUs, so I don't see any reason that DMA-350
wouldn't either.
Would you propose making all the DesignWare drivers depend on ARC
because those happen to come from the same company too? ;)
Thanks,
Robin.
> Hence add
> dependencies on ARM and ARM64, to prevent asking the user about this
> driver when configuring a kernel for a non-Arm architecture.
>
> Fixes: 5d099706449d54b4 ("dmaengine: Add Arm DMA-350 driver")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/dma/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> index 8109f73baf10fc3b..db87dd2a07f7606e 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -95,6 +95,7 @@ config APPLE_ADMAC
>
> config ARM_DMA350
> tristate "Arm DMA-350 support"
> + depends on ARM || ARM64 || COMPILE_TEST
> select DMA_ENGINE
> select DMA_VIRTUAL_CHANNELS
> help
next prev parent reply other threads:[~2025-04-23 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 18:11 [PATCH] dmaengine: ARM_DMA350 should depend on ARM/ARM64 Geert Uytterhoeven
2025-04-23 10:59 ` Robin Murphy [this message]
2025-04-23 11:11 ` Geert Uytterhoeven
2025-04-23 11:48 ` Vinod Koul
2025-04-23 12:13 ` Geert Uytterhoeven
2025-04-23 12:17 ` Vinod Koul
2025-04-23 13:29 ` Robin Murphy
2025-04-23 14:34 ` Geert Uytterhoeven
2025-04-24 11:38 ` Robin Murphy
2025-04-24 5:36 ` 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=b1f19b31-3535-4bb5-bcef-6f17ad2a0ee6@arm.com \
--to=robin.murphy@arm.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.