linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 14/15] ARM: pxa: change SSP devices allocation
Date: Thu, 5 Apr 2018 09:29:30 +0200	[thread overview]
Message-ID: <CAK8P3a0xJnVfXfUtP+JXGNgc2-LuHUmZCMq-SnEQw3wu3azemA@mail.gmail.com> (raw)
In-Reply-To: <87zi2i2ljy.fsf@belgarion.home>

On Thu, Apr 5, 2018 at 8:51 AM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> Arnd Bergmann <arnd@arndb.de> writes:
>
>> I'm still unable to follow through that code, but I understand now that
>> the device you pass to dma_request_slave_channel() is not the one
>> we'd like it to be here.
>>
>> Where exactly does that call to dma_request_chan() happen? Is this
>> the one in dmaengine_pcm_new()? Could we perhaps put a
>> pointer to the SSP device into snd_dmaengine_dai_dma_data?
> This is a sample stack I captured with an added WARN_ON(1), triggered by a
> userland "aplay Sultans_Of_Swing.wav" :)
>
> [  299.216743] [<c0012e80>] (unwind_backtrace) from [<c000f55c>] (show_stack+0x20/0x24)
> [  299.223986] [<c000f55c>] (show_stack) from [<c0529d68>] (dump_stack+0x20/0x28)
> [  299.231321] [<c0529d68>] (dump_stack) from [<c001de34>] (__warn+0xf0/0x11c)
> [  299.238183] [<c001de34>] (__warn) from [<c001df94>] (warn_slowpath_null+0x4c/0x58)
> [  299.245234] [<c001df94>] (warn_slowpath_null) from [<c02a2d38>] (dma_request_chan+0x40/0x228)
> [  299.252550] [<c02a2d38>] (dma_request_chan) from [<c02a2f38>] (dma_request_slave_channel+0x18/0x24)
> [  299.259855] [<c02a2f38>] (dma_request_slave_channel) from [<c03f76f0>] (__pxa2xx_pcm_open+0xf4/0x110)
> [  299.266789] [<c03f76f0>] (__pxa2xx_pcm_open) from [<c0409ed0>] (soc_pcm_open+0xf8/0x9c8)
> [  299.273932] [<c0409ed0>] (soc_pcm_open) from [<c03db9d4>] (snd_pcm_open_substream+0x9c/0x134)

Ok, so it seems we currently have a special case here that is only used by
pxa/mmp and omap, and you can simply open-code that by calling
dma_request_chan() from the pxa-specific __pxa2xx_pcm_open()
with any device pointer you like, it doesn't have to be the main audio
device.

I don't know exactly how the probing works, but I'd assume that we have
the correct device pointers in pxa2xx_ac97_dev_probe() and
asoc_ssp_probe(), or maybe in pxa2xx_ac97_*_startup() and
pxa_ssp_startup().

      Arnd

  reply	other threads:[~2018-04-05  7:29 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 14:26 [PATCH 00/15] ARM: pxa: switch to DMA slave maps Robert Jarzmik
2018-04-02 14:26 ` [PATCH 01/15] dmaengine: pxa: use a dma slave map Robert Jarzmik
2018-04-21 19:23   ` Robert Jarzmik
2018-04-22  6:13     ` Vinod Koul
2018-04-02 14:26 ` [PATCH 02/15] ARM: pxa: add " Robert Jarzmik
2018-04-03  6:51   ` Arnd Bergmann
2018-04-03 15:18     ` Robert Jarzmik
2018-04-03 15:39       ` Arnd Bergmann
2018-04-03 20:19         ` Robert Jarzmik
2018-04-04 10:18           ` Arnd Bergmann
2018-04-04 19:21             ` Robert Jarzmik
2018-04-02 14:26 ` [PATCH 03/15] mmc: pxamci: remove the dmaengine compat need Robert Jarzmik
2018-04-02 14:26 ` [PATCH 04/15] media: pxa_camera: " Robert Jarzmik
2018-04-21 19:27   ` Robert Jarzmik
2018-04-22 11:06     ` Hans Verkuil
2018-04-22 11:06   ` Hans Verkuil
2018-05-04 19:29     ` Mauro Carvalho Chehab
2018-04-02 14:26 ` [PATCH 05/15] mtd: nand: pxa3xx: " Robert Jarzmik
2018-05-18 21:31   ` Daniel Mack
2018-05-23 21:54     ` Daniel Mack
2018-04-02 14:26 ` [PATCH 06/15] net: smc911x: " Robert Jarzmik
2018-04-02 14:26 ` [PATCH 07/15] net: smc91x: " Robert Jarzmik
2018-04-02 14:26 ` [PATCH 08/15] ASoC: pxa: " Robert Jarzmik
2018-04-12 15:26   ` Mark Brown
2018-04-12 16:55     ` Robert Jarzmik
2018-04-02 14:26 ` [PATCH 09/15] net: irda: pxaficp_ir: " Robert Jarzmik
2018-04-21 19:30   ` Robert Jarzmik
2018-04-23  8:37   ` Greg Kroah-Hartman
2018-04-02 14:26 ` [PATCH 10/15] ata: pata_pxa: " Robert Jarzmik
2018-04-21 19:32   ` Robert Jarzmik
2018-04-24 11:04     ` Bartlomiej Zolnierkiewicz
2018-04-02 14:26 ` [PATCH 11/15] dmaengine: pxa: document pxad_param Robert Jarzmik
2018-04-02 14:26 ` [PATCH 12/15] dmaengine: pxa: make the filter function internal Robert Jarzmik
2018-04-02 16:25   ` kbuild test robot
2018-04-02 16:35   ` kbuild test robot
2018-04-03  7:13     ` Arnd Bergmann
2018-04-02 14:26 ` [PATCH 13/15] ARM: pxa: remove the DMA IO resources Robert Jarzmik
2018-04-02 14:26 ` [PATCH 14/15] ARM: pxa: change SSP devices allocation Robert Jarzmik
2018-04-03  7:06   ` Arnd Bergmann
2018-04-03 15:32     ` Robert Jarzmik
2018-04-03 15:53       ` Arnd Bergmann
2018-04-05  6:51         ` Robert Jarzmik
2018-04-05  7:29           ` Arnd Bergmann [this message]
2018-04-08 12:16             ` Robert Jarzmik
2018-04-02 14:26 ` [PATCH 15/15] ARM: pxa: change SSP DMA channels allocation Robert Jarzmik
2018-04-02 18:46   ` kbuild test robot
2018-04-03  7:15 ` [PATCH 00/15] ARM: pxa: switch to DMA slave maps Arnd Bergmann
2018-04-03 15:08 ` Ulf Hansson
2018-04-04 19:49   ` Robert Jarzmik
2018-04-04 19:56     ` Boris Brezillon
2018-04-05  6:29       ` Ulf Hansson
2018-04-05  6:50         ` Arnd Bergmann

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=CAK8P3a0xJnVfXfUtP+JXGNgc2-LuHUmZCMq-SnEQw3wu3azemA@mail.gmail.com \
    --to=arnd@arndb.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).