All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@oss.nxp.com>
To: "Nuno Sá" <noname.nuno@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Nuno Sá" <nuno.sa@analog.com>, "Vinod Koul" <vkoul@kernel.org>,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org, linux-iio@vger.kernel.org,
	linux-sound@vger.kernel.org, linux-spi@vger.kernel.org,
	"Frank Li" <Frank.Li@kernel.org>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Eugeniy Paltsev" <Eugeniy.Paltsev@synopsys.com>,
	"Amélie Delaunay" <amelie.delaunay@foss.st.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Mark Brown" <broonie@kernel.org>
Subject: Re: [PATCH v4 01/10] dmaengine: Move enum dma_slave_buswidth to a new header
Date: Tue, 6 Oct 2026 02:59:16 -0500	[thread overview]
Message-ID: <asSqVEHe8EjkbcwW@SMW015318> (raw)
In-Reply-To: <6f5dd1c1622adbaf0174a949ca91cb11872087ff.camel@gmail.com>

On Tue, Oct 06, 2026 at 07:36:06AM +0100, Nuno Sá wrote:
> On Sat, 2026-10-03 at 19:59 -0500, Frank Li wrote:
...
> >
> > There are already include bitmap.h, and use
> >
> > typedef struct { DECLARE_BITMAP(bits, DMA_TX_TYPE_END); } dma_cap_mask_t;
> >
> > Suppose all DMA Engine consumer will use it to do some check. So I think
> > needn't split it as indivial version.
>
> Are we sure all consumers are making use of dma_cap_mask?

Some legacy user check it. Supposed needn't check it after get channel.
I am working new API to check it to avoid direct access it.

> In fact the only function
> depending on bitmap.h is the one clearing the cap_mask. But stepping a bit back,
> bitmap.h was the original proposal from Andy so the idea was to have the new
> widthmask (this one indeed heavily uses bitmaps) already as a split. And with it,
> came types.h given that the DMA enum needs to be used from both consumers and
> providers.

Supposed provider is super set, which can include consume part.

> And note that consumers might want the header without actually needing the
> bus width API so the separation kind of made sense to me.
> Then, as a follow up the idea was to also split the cap_mask API into it's own header
> with a backing include in the main consumer header.
>
> So if we all agree with the above, I guess the current series does not really has to
> change. I see 3 ways:
>
> * Just go back some versions before and have all of it in dmaengine.h
> * The current form
> * s/engine/consumer on the current proposal include/linux/dma/engine/*

I think we can put include/linux/dmaengine.h now. The split/move need more
work. I already sent some patches.

Frank

>
> - Nuno Sá
>
> >
> > Frank
> >
> > > where it's indeed required. Besides bitmap.h there are might be more headers
> > > that "include half of the world" which should be avoided in every header file.
> > >
> > > --
> > > With Best Regards,
> > > Andy Shevchenko
> > >
> > >

  reply	other threads:[~2026-10-06  7:59 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 17:25 [PATCH v4 00/10] dmaengine: Support bus widths of 32 bytes and above Nuno Sá
2026-09-11 17:25 ` [PATCH v4 01/10] dmaengine: Move enum dma_slave_buswidth to a new header Nuno Sá
2026-09-12  7:57   ` Andy Shevchenko
2026-09-14 14:18   ` Frank Li
2026-09-14 15:40     ` Nuno Sá
2026-09-15  7:29     ` Andy Shevchenko
2026-09-15 14:37       ` Frank Li
2026-09-15 14:53         ` Andy Shevchenko
2026-09-17 10:54           ` Nuno Sá
2026-09-17 12:29             ` Andy Shevchenko
2026-09-17 10:49         ` Nuno Sá
2026-09-17 14:38           ` Frank Li
2026-09-17 15:26             ` Nuno Sá
2026-09-18  8:25             ` Nuno Sá
2026-09-15 15:52       ` Vinod Koul
2026-09-15 16:20         ` Vinod Koul
2026-09-15 17:04           ` Frank Li
2026-09-17 18:09             ` Vinod Koul
2026-09-18  6:24               ` Andy Shevchenko
2026-09-18 18:01                 ` Vinod Koul
2026-09-18  8:39               ` Nuno Sá
2026-09-18 18:03                 ` Vinod Koul
2026-09-21  8:53                   ` Nuno Sá
2026-09-21 16:12                     ` Frank Li
2026-10-02 10:43                       ` Nuno Sá
2026-10-02 13:47                         ` Frank Li
2026-10-03 14:52                           ` Andy Shevchenko
2026-10-04  0:59                             ` Frank Li
2026-10-04  8:31                               ` Andy Shevchenko
2026-10-06  6:36                               ` Nuno Sá
2026-10-06  7:59                                 ` Frank Li [this message]
2026-10-06  9:47                                   ` Nuno Sá
2026-09-11 17:25 ` [PATCH v4 02/10] dmaengine: Support bus widths of 32 bytes and above Nuno Sá
2026-09-14  8:05   ` Andy Shevchenko
2026-09-11 17:25 ` [PATCH v4 03/10] dmaengine: dma-axi-dmac: Use bus width capability helpers Nuno Sá
2026-09-11 17:39   ` sashiko-bot
2026-09-11 17:25 ` [PATCH v4 04/10] dmaengine: dw-axi-dmac: " Nuno Sá
2026-09-11 17:40   ` sashiko-bot
2026-09-11 17:25 ` [PATCH v4 05/10] dmaengine: qcom: gpi: " Nuno Sá
2026-09-11 17:40   ` sashiko-bot
2026-09-11 17:25 ` [PATCH v4 06/10] dmaengine: stm32-dma3: " Nuno Sá
2026-09-11 17:25 ` [PATCH v4 07/10] iio: buffer-dmaengine: Use dma_slave_caps bus width accessors Nuno Sá
2026-09-14  8:06   ` Andy Shevchenko
2026-09-11 17:25 ` [PATCH v4 08/10] ALSA: pcm_dmaengine: Use dma_slave_caps bus width helpers Nuno Sá
2026-09-14  8:12   ` Andy Shevchenko
2026-09-14 15:39     ` Nuno Sá
2026-09-15  7:31       ` Andy Shevchenko
2026-09-15  8:13         ` Nuno Sá
2026-09-11 17:25 ` [PATCH v4 09/10] spi: dw: " Nuno Sá
2026-09-11 17:25 ` [PATCH v4 10/10] dmaengine: Drop legacy bus width fields from dma_slave_caps Nuno Sá

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=asSqVEHe8EjkbcwW@SMW015318 \
    --to=frank.li@oss.nxp.com \
    --cc=Eugeniy.Paltsev@synopsys.com \
    --cc=Frank.Li@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=amelie.delaunay@foss.st.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=broonie@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=noname.nuno@gmail.com \
    --cc=nuno.sa@analog.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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 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.