From: Vinod Koul <vkoul@kernel.org>
To: Amelie Delaunay <amelie.delaunay@foss.st.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-stm32@st-md-mailman.stormreply.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: add channel device name to channel registration
Date: Thu, 21 Dec 2023 22:48:27 +0530 [thread overview]
Message-ID: <ZYRzY3ul9UzD9d06@matsya> (raw)
In-Reply-To: <5e007fe4-d6cd-4ec3-b9c1-ef7841e29851@foss.st.com>
On 21-12-23, 18:11, Amelie Delaunay wrote:
> Hi Vinod,
>
> On 12/21/23 17:13, Vinod Koul wrote:
> > On 13-12-23, 18:40, Amelie Delaunay wrote:
> > > Channel device name is used for sysfs, but also by dmatest filter function.
> > >
> > > With dynamic channel registration, channels can be registered after dma
> > > controller registration. Users may want to have specific channel names.
> > >
> > > If name is NULL, the channel name relies on previous implementation,
> > > dma<controller_device_id>chan<channel_device_id>.
> >
> > lgtm, where is the user for this..?
> >
>
> I'll send beginning of next year a DMA controller driver for STM32MP25 SoC
> family. It relies on the dynamic channel registration. It will be a user of
> this dma_async_device_channel_register(struct dma_device *device, struct
> dma_chan *chan, const char *name).
Okay, I prefer to add a API with the user.
Thnx
--
~Vinod
prev parent reply other threads:[~2023-12-21 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 17:40 [PATCH] dmaengine: add channel device name to channel registration Amelie Delaunay
2023-12-21 16:13 ` Vinod Koul
2023-12-21 17:11 ` Amelie Delaunay
2023-12-21 17:18 ` Vinod Koul [this message]
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=ZYRzY3ul9UzD9d06@matsya \
--to=vkoul@kernel.org \
--cc=amelie.delaunay@foss.st.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.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