From: Lee Jones <lee.jones@linaro.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: alsa-devel@alsa-project.org,
Linus Walleij <linus.walleij@linaro.org>,
LKML <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case
Date: Wed, 4 Dec 2013 18:03:21 +0000 [thread overview]
Message-ID: <20131204180321.GE26581@lee--X1> (raw)
In-Reply-To: <CAGa+x85c3y5+VXFjHAZYpUM0+2Tfnra6QKad7-aeUdwjSwo+Vg@mail.gmail.com>
> Today's next (next-20131204) has a new boot failure[1] on
> ux500/snowball which bisected down to this commit. Full boot log
> attached.
Right.
Anyone not on CC (which I think you are Kevin) can follow the fun here:
http://www.spinics.net/lists/arm-kernel/msg291374.html
> It doesn't find the alsa device which in turn seems to prevent the
> emmc rootfs from being mounted. It boots fine to an initramfs.
<snip>
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80125000' missing or empty
> mmc1: new high speed MMC card at address 0001
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80125000' missing or empty
> mmcblk0: mmc1:0001 7.28 GiB
> mmcblk0boot0: mmc1:0001 partition 1 2.00 MiB
> mmcblk0boot1: mmc1:0001 partition 2 2.00 MiB
> mmcblk0rpmb: mmc1:0001 partition 3 128 KiB
> dma dma0chan22: [d40_config_memcpy] No memcpy
> dma dma0chan22: [d40_alloc_chan_resources] Failed to configure memcpy channel
> ux500-msp-i2s ux500-msp-i2s.1: Missing dma channel for stream: 0
> ux500-msp-i2s ux500-msp-i2s.1: ASoC: pcm constructor failed: -22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: can't create pcm ab8500_0 :-22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: failed to instantiate card -22
> snd-soc-mop500 snd-soc-mop500.0: Error: snd_soc_register_card failed (-22)!
> snd-soc-mop500: probe of snd-soc-mop500.0 failed with error -22
<snip>
> mmci-pl18x sdi4: error during DMA transfer!
> mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
> mmcblk0rpmb: retrying using single block read
It's interesting that the MSP failure has managed to fudge the entire
DMA Controller. I have absolutely no idea how that can even happen?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
WARNING: multiple messages have this Message-ID (diff)
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case
Date: Wed, 4 Dec 2013 18:03:21 +0000 [thread overview]
Message-ID: <20131204180321.GE26581@lee--X1> (raw)
In-Reply-To: <CAGa+x85c3y5+VXFjHAZYpUM0+2Tfnra6QKad7-aeUdwjSwo+Vg@mail.gmail.com>
> Today's next (next-20131204) has a new boot failure[1] on
> ux500/snowball which bisected down to this commit. Full boot log
> attached.
Right.
Anyone not on CC (which I think you are Kevin) can follow the fun here:
http://www.spinics.net/lists/arm-kernel/msg291374.html
> It doesn't find the alsa device which in turn seems to prevent the
> emmc rootfs from being mounted. It boots fine to an initramfs.
<snip>
> of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80125000' missing or empty
> mmc1: new high speed MMC card at address 0001
> of_dma_request_slave_channel: dma-names property of node '/soc/msp at 80125000' missing or empty
> mmcblk0: mmc1:0001 7.28 GiB
> mmcblk0boot0: mmc1:0001 partition 1 2.00 MiB
> mmcblk0boot1: mmc1:0001 partition 2 2.00 MiB
> mmcblk0rpmb: mmc1:0001 partition 3 128 KiB
> dma dma0chan22: [d40_config_memcpy] No memcpy
> dma dma0chan22: [d40_alloc_chan_resources] Failed to configure memcpy channel
> ux500-msp-i2s ux500-msp-i2s.1: Missing dma channel for stream: 0
> ux500-msp-i2s ux500-msp-i2s.1: ASoC: pcm constructor failed: -22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: can't create pcm ab8500_0 :-22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: failed to instantiate card -22
> snd-soc-mop500 snd-soc-mop500.0: Error: snd_soc_register_card failed (-22)!
> snd-soc-mop500: probe of snd-soc-mop500.0 failed with error -22
<snip>
> mmci-pl18x sdi4: error during DMA transfer!
> mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
> mmcblk0rpmb: retrying using single block read
It's interesting that the MSP failure has managed to fudge the entire
DMA Controller. I have absolutely no idea how that can even happen?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Kevin Hilman <khilman@linaro.org>
Cc: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case
Date: Wed, 4 Dec 2013 18:03:21 +0000 [thread overview]
Message-ID: <20131204180321.GE26581@lee--X1> (raw)
In-Reply-To: <CAGa+x85c3y5+VXFjHAZYpUM0+2Tfnra6QKad7-aeUdwjSwo+Vg@mail.gmail.com>
> Today's next (next-20131204) has a new boot failure[1] on
> ux500/snowball which bisected down to this commit. Full boot log
> attached.
Right.
Anyone not on CC (which I think you are Kevin) can follow the fun here:
http://www.spinics.net/lists/arm-kernel/msg291374.html
> It doesn't find the alsa device which in turn seems to prevent the
> emmc rootfs from being mounted. It boots fine to an initramfs.
<snip>
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80124000' missing or empty
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80125000' missing or empty
> mmc1: new high speed MMC card at address 0001
> of_dma_request_slave_channel: dma-names property of node '/soc/msp@80125000' missing or empty
> mmcblk0: mmc1:0001 7.28 GiB
> mmcblk0boot0: mmc1:0001 partition 1 2.00 MiB
> mmcblk0boot1: mmc1:0001 partition 2 2.00 MiB
> mmcblk0rpmb: mmc1:0001 partition 3 128 KiB
> dma dma0chan22: [d40_config_memcpy] No memcpy
> dma dma0chan22: [d40_alloc_chan_resources] Failed to configure memcpy channel
> ux500-msp-i2s ux500-msp-i2s.1: Missing dma channel for stream: 0
> ux500-msp-i2s ux500-msp-i2s.1: ASoC: pcm constructor failed: -22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: can't create pcm ab8500_0 :-22
> snd-soc-mop500 snd-soc-mop500.0: ASoC: failed to instantiate card -22
> snd-soc-mop500 snd-soc-mop500.0: Error: snd_soc_register_card failed (-22)!
> snd-soc-mop500: probe of snd-soc-mop500.0 failed with error -22
<snip>
> mmci-pl18x sdi4: error during DMA transfer!
> mmcblk0rpmb: error -110 transferring data, sector 0, nr 8, cmd response 0x900, card status 0x0
> mmcblk0rpmb: retrying using single block read
It's interesting that the MSP failure has managed to fudge the entire
DMA Controller. I have absolutely no idea how that can even happen?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-12-04 18:03 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 11:07 [PATCH 00/10] ASoC: dma: ARM: ux500: Obtain DMA data from Device Tree Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 11:07 ` [PATCH 01/10] dma: ste_dma40: Expand DT binding to accept 'high-priority channel' flag Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 21:02 ` Linus Walleij
2013-11-19 21:02 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 02/10] dma: ste_dma40: Parse flags property for new 'high priority channel' request Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 21:03 ` Linus Walleij
2013-11-19 21:03 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 03/10] ARM: ux500: Don't use enums for MSP IDs - for easy DT conversion Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 11:07 ` [PATCH 04/10] ARM: ux500: Add DMA config bindings for MSP devices Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 21:06 ` Linus Walleij
2013-11-19 21:06 ` Linus Walleij
2013-11-19 11:07 ` [PATCH 05/10] ASoC: Ux500: Match platform by device node when booting Device Tree Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:49 ` Mark Brown
2013-11-19 18:49 ` Mark Brown
2013-11-19 11:07 ` [PATCH 06/10] ASoC: ux500_pcm: Extend Device Tree support to deal with DMA data Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:50 ` Mark Brown
2013-11-19 18:50 ` Mark Brown
2013-11-19 11:07 ` [PATCH 07/10] ASoC: ux500: Store DMA data in the DAI differently in the pdata and DT case Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:51 ` Mark Brown
2013-11-19 18:51 ` Mark Brown
2013-12-02 7:35 ` [alsa-devel] " Olof Johansson
2013-12-02 7:35 ` Olof Johansson
2013-12-02 10:12 ` Lee Jones
2013-12-02 10:12 ` [alsa-devel] " Lee Jones
2013-12-02 10:12 ` Lee Jones
2013-12-02 13:54 ` Mark Brown
2013-12-02 13:54 ` Mark Brown
2013-12-02 14:03 ` Lee Jones
2013-12-02 14:03 ` [alsa-devel] " Lee Jones
2013-12-02 14:03 ` Lee Jones
2013-12-02 14:04 ` Mark Brown
2013-12-02 14:04 ` Mark Brown
2013-12-02 14:04 ` Mark Brown
2013-12-04 17:45 ` Kevin Hilman
2013-12-04 17:45 ` Kevin Hilman
2013-12-04 18:03 ` Lee Jones [this message]
2013-12-04 18:03 ` Lee Jones
2013-12-04 18:03 ` Lee Jones
2013-11-19 11:07 ` [PATCH 08/10] ASoC: ux500_pcm: Differentiate between pdata and DT initialisation Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:48 ` Mark Brown
2013-11-19 18:48 ` Mark Brown
2013-11-19 19:33 ` Lee Jones
2013-11-19 19:33 ` Lee Jones
2013-11-19 19:40 ` Lars-Peter Clausen
2013-11-19 19:40 ` Lars-Peter Clausen
2013-11-19 20:09 ` Mark Brown
2013-11-19 20:09 ` Mark Brown
2013-11-19 11:07 ` [PATCH 09/10] ASoC: ux500_pcm: Take out pointless dev_dbg() call Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:51 ` Mark Brown
2013-11-19 18:51 ` Mark Brown
2013-11-19 11:07 ` [PATCH 10/10] ASoC: ux500: Dynamically fill DAI driver data on probe Lee Jones
2013-11-19 11:07 ` Lee Jones
2013-11-19 18:53 ` [PATCH 00/10] ASoC: dma: ARM: ux500: Obtain DMA data from Device Tree Mark Brown
2013-11-19 18:53 ` Mark Brown
2013-11-29 16:03 ` Lee Jones
2013-11-29 16:03 ` Lee Jones
2013-11-29 16:42 ` Mark Brown
2013-11-29 16:42 ` Mark Brown
2013-11-29 17:37 ` Lee Jones
2013-11-29 17:37 ` Lee Jones
2013-11-29 18:21 ` Mark Brown
2013-11-29 18:21 ` Mark Brown
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=20131204180321.GE26581@lee--X1 \
--to=lee.jones@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=khilman@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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.