From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/9] dmaengine: Create a generic dma_slave_caps callback
Date: Wed, 1 Oct 2014 10:21:57 +0200 [thread overview]
Message-ID: <20141001082157.GE6884@lukather> (raw)
In-Reply-To: <20140927092536.GZ5182@n2100.arm.linux.org.uk>
Hi Russell,
On Sat, Sep 27, 2014 at 10:25:36AM +0100, Russell King - ARM Linux wrote:
> On Sat, Sep 27, 2014 at 10:54:42AM +0200, Maxime Ripard wrote:
> > dma_slave_caps is very important to the generic layers that might interact with
> > dmaengine, such as ASoC. Unfortunately, it has been added as yet another
> > dma_device callback, and most of the existing drivers haven't implemented it,
> > reducing its reliability.
>
> Many haven't implemented it probably because either (a) they don't get used
> with ASoC, or (b) they aren't aware of the new interface, or (c) can't be
> bothered with the churn.
For a), I really see this as a chicken-egg issue. ASoC is the only
user of it because it's the only framework that has a generic layer on
top, and it's the only framework that has a generic layer because most
drivers don't implement it.
Now, there seems to be a trend to actually use a generic DMA layer in
other frameworks. SPI gained one recently, I think I saw something
about some discussions for IIO and I2C too. And in order for this to
work, we have to make it reliable, and as such, implemented on most
drivers.
> However, trying to return something introduces a bug:
>
> > static inline int dma_get_slave_caps(struct dma_chan *chan, struct dma_slave_caps *caps)
> > {
> > + struct dma_device *device;
> > +
> > if (!chan || !caps)
> > return -EINVAL;
> >
> > + device = chan->device;
> > +
> > /* check if the channel supports slave transactions */
> > - if (!test_bit(DMA_SLAVE, chan->device->cap_mask.bits))
> > + if (!test_bit(DMA_SLAVE, device->cap_mask.bits))
> > return -ENXIO;
> >
> > - if (chan->device->device_slave_caps)
> > - return chan->device->device_slave_caps(chan, caps);
> > + caps->cmd_pause = !!device->device_pause;
> > + caps->cmd_terminate = !!device->device_terminate_all;
> > +
> > + if (device->device_slave_caps)
> > + return device->device_slave_caps(chan, caps);
> >
> > - return -ENXIO;
> > + return 0;
>
> So this now returns success if the driver doesn't implement device_slave_caps(),
> but with most of the structure zero.
>
> Now, consider what effect this has with:
>
>
> ret = dma_get_slave_caps(chan, &dma_caps);
> if (ret == 0) {
> if (dma_caps.cmd_pause)
> hw.info |= SNDRV_PCM_INFO_PAUSE | SNDRV_PCM_INFO_RESUME;
> if (dma_caps.residue_granularity <= DMA_RESIDUE_GRANULARITY_SEGMENT)
> hw.info |= SNDRV_PCM_INFO_BATCH;
>
> if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
> addr_widths = dma_caps.dstn_addr_widths;
> else
> addr_widths = dma_caps.src_addr_widths;
> }
>
> addr_widths becomes zero, and we also get SNDRV_PCM_INFO_BATCH turned
> on for _all_ DMA engine drivers. The first renders ASoC useless with
> DMA engine.
>
> It may be a good way to get people to implement it, but this will cause
> regressions.
Hmmm, nasty indeed. Maybe we could add a test to see if any of the
field we're going to use are filled, and if not, return an error?
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20141001/262b71c3/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "Vinod Koul" <vinod.koul@intel.com>,
dmaengine@vger.kernel.org, lars@metafoo.de,
linux-kernel@vger.kernel.org,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
linux-arm-kernel@lists.infradead.org,
"Antoine Ténart" <antoine@free-electrons.com>
Subject: Re: [PATCH 6/9] dmaengine: Create a generic dma_slave_caps callback
Date: Wed, 1 Oct 2014 10:21:57 +0200 [thread overview]
Message-ID: <20141001082157.GE6884@lukather> (raw)
In-Reply-To: <20140927092536.GZ5182@n2100.arm.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 3341 bytes --]
Hi Russell,
On Sat, Sep 27, 2014 at 10:25:36AM +0100, Russell King - ARM Linux wrote:
> On Sat, Sep 27, 2014 at 10:54:42AM +0200, Maxime Ripard wrote:
> > dma_slave_caps is very important to the generic layers that might interact with
> > dmaengine, such as ASoC. Unfortunately, it has been added as yet another
> > dma_device callback, and most of the existing drivers haven't implemented it,
> > reducing its reliability.
>
> Many haven't implemented it probably because either (a) they don't get used
> with ASoC, or (b) they aren't aware of the new interface, or (c) can't be
> bothered with the churn.
For a), I really see this as a chicken-egg issue. ASoC is the only
user of it because it's the only framework that has a generic layer on
top, and it's the only framework that has a generic layer because most
drivers don't implement it.
Now, there seems to be a trend to actually use a generic DMA layer in
other frameworks. SPI gained one recently, I think I saw something
about some discussions for IIO and I2C too. And in order for this to
work, we have to make it reliable, and as such, implemented on most
drivers.
> However, trying to return something introduces a bug:
>
> > static inline int dma_get_slave_caps(struct dma_chan *chan, struct dma_slave_caps *caps)
> > {
> > + struct dma_device *device;
> > +
> > if (!chan || !caps)
> > return -EINVAL;
> >
> > + device = chan->device;
> > +
> > /* check if the channel supports slave transactions */
> > - if (!test_bit(DMA_SLAVE, chan->device->cap_mask.bits))
> > + if (!test_bit(DMA_SLAVE, device->cap_mask.bits))
> > return -ENXIO;
> >
> > - if (chan->device->device_slave_caps)
> > - return chan->device->device_slave_caps(chan, caps);
> > + caps->cmd_pause = !!device->device_pause;
> > + caps->cmd_terminate = !!device->device_terminate_all;
> > +
> > + if (device->device_slave_caps)
> > + return device->device_slave_caps(chan, caps);
> >
> > - return -ENXIO;
> > + return 0;
>
> So this now returns success if the driver doesn't implement device_slave_caps(),
> but with most of the structure zero.
>
> Now, consider what effect this has with:
>
>
> ret = dma_get_slave_caps(chan, &dma_caps);
> if (ret == 0) {
> if (dma_caps.cmd_pause)
> hw.info |= SNDRV_PCM_INFO_PAUSE | SNDRV_PCM_INFO_RESUME;
> if (dma_caps.residue_granularity <= DMA_RESIDUE_GRANULARITY_SEGMENT)
> hw.info |= SNDRV_PCM_INFO_BATCH;
>
> if (substream->stream == SNDRV_PCM_STREAM_PLAYBACK)
> addr_widths = dma_caps.dstn_addr_widths;
> else
> addr_widths = dma_caps.src_addr_widths;
> }
>
> addr_widths becomes zero, and we also get SNDRV_PCM_INFO_BATCH turned
> on for _all_ DMA engine drivers. The first renders ASoC useless with
> DMA engine.
>
> It may be a good way to get people to implement it, but this will cause
> regressions.
Hmmm, nasty indeed. Maybe we could add a test to see if any of the
field we're going to use are filled, and if not, return an error?
Thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-10-01 8:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 8:54 [PATCH 0/9] dmaengine: Implement generic slave capabilities retrieval Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 1/9] dmaengine: Make the destination abbreviation coherent Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 2/9] dmaengine: Make channel allocation callbacks optional Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-28 16:07 ` Vinod Koul
2014-09-28 16:07 ` Vinod Koul
2014-10-01 8:39 ` Maxime Ripard
2014-10-01 8:39 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 3/9] dmaengine: Introduce a device_config callback Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-28 16:13 ` Vinod Koul
2014-09-28 16:13 ` Vinod Koul
2014-09-28 16:14 ` Vinod Koul
2014-09-28 16:14 ` Vinod Koul
2014-09-27 8:54 ` [PATCH 4/9] dmaengine: split out pause/resume operations from device_control Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 5/9] dmaengine: Add device_terminate_all callback Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 6/9] dmaengine: Create a generic dma_slave_caps callback Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 9:25 ` Russell King - ARM Linux
2014-09-27 9:25 ` Russell King - ARM Linux
2014-10-01 8:21 ` Maxime Ripard [this message]
2014-10-01 8:21 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 7/9] dmaengine: Move slave caps to dma_device Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 9:28 ` Russell King - ARM Linux
2014-09-27 9:28 ` Russell King - ARM Linux
2014-10-01 8:27 ` Maxime Ripard
2014-10-01 8:27 ` Maxime Ripard
2014-10-01 8:55 ` Russell King - ARM Linux
2014-10-01 8:55 ` Russell King - ARM Linux
2014-09-27 8:54 ` [PATCH 8/9] dmaengine: Mark device_control as deprecated Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
2014-09-27 8:54 ` [PATCH 9/9] dmaengine: sun6i: Convert to generic slave_caps Maxime Ripard
2014-09-27 8:54 ` Maxime Ripard
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=20141001082157.GE6884@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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.