From: Vinod Koul <vkoul@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
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 17:18:19 +0530 [thread overview]
Message-ID: <aAjTg8dgvxqLQOwQ@vaman> (raw)
In-Reply-To: <CAMuHMdVJKA8zYETKJTRAwg6=+EuTq4YqbFO32K4+py9YNsD1Gw@mail.gmail.com>
On 23-04-25, 13:11, Geert Uytterhoeven wrote:
> Hi Robin,
>
> On Wed, 23 Apr 2025 at 12:59, Robin Murphy <robin.murphy@arm.com> wrote:
> > 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.
>
> The dependency can always be relaxed later, when the need arises.
> Note that currently there are no users at all...
True, but do we have any warnings generated as a result, if there are no
dependency should we still limit a driver to an arch?
--
~Vinod
next prev parent reply other threads:[~2025-04-23 11:48 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
2025-04-23 11:11 ` Geert Uytterhoeven
2025-04-23 11:48 ` Vinod Koul [this message]
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=aAjTg8dgvxqLQOwQ@vaman \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
/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