* DMA screams on MSP
@ 2014-02-04 11:56 Linus Walleij
2014-02-04 13:36 ` Lee Jones
0 siblings, 1 reply; 4+ messages in thread
From: Linus Walleij @ 2014-02-04 11:56 UTC (permalink / raw)
To: Lee Jones; +Cc: alsa-devel@alsa-project.org, Mark Brown
Hi Lee,
I get this in my bootlog nowadays (v3.14-rc1):
[ 2.713897] dma dma0chan29: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.725158] dma dma0chan30: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.737457] dma dma0chan31: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.750793] dma dma0chan32: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.762145] dma dma0chan33: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.773376] dma dma0chan34: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.784606] dma dma0chan35: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.795837] dma dma0chan36: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.807067] dma dma0chan37: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.818298] dma dma0chan38: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.829528] dma dma0chan39: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.840728] dma dma0chan40: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.851959] dma dma0chan41: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
[ 2.863189] dma dma0chan42: [d40_validate_conf] Invalid device type
(14) physical channel exeeds available physical channels
(...)
[ 5.315887] dma dma0chan252: [d40_validate_conf] Invalid device
type (14) physical channel exeeds available physical channels
[ 5.327209] dma dma0chan253: [d40_validate_conf] Invalid device
type (14) physical channel exeeds available physical channels
[ 5.338531] dma dma0chan254: [d40_validate_conf] Invalid device
type (14) physical channel exeeds available physical channels
[ 5.349853] dma dma0chan255: [d40_validate_conf] Invalid device
type (14) physical channel exeeds available physical channels
(I patched dma40 to state the exact cause instead of just
"invalid device type".)
Like something (I guess ALSA SoC?) is trying real hard to get physical
channel 14, but I can't seem to figure out what is going on.
I will try to see if this also appears on the Snowball but I guess
so?
Any hints appreciated...
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DMA screams on MSP
2014-02-04 11:56 DMA screams on MSP Linus Walleij
@ 2014-02-04 13:36 ` Lee Jones
2014-02-04 20:01 ` Linus Walleij
0 siblings, 1 reply; 4+ messages in thread
From: Lee Jones @ 2014-02-04 13:36 UTC (permalink / raw)
To: Linus Walleij; +Cc: alsa-devel@alsa-project.org, Mark Brown
> I get this in my bootlog nowadays (v3.14-rc1):
>
> [ 2.713897] dma dma0chan29: [d40_validate_conf] Invalid device type
> (14) physical channel exeeds available physical channels
<snip>
> (I patched dma40 to state the exact cause instead of just
> "invalid device type".)
>
> Like something (I guess ALSA SoC?) is trying real hard to get physical
> channel 14, but I can't seem to figure out what is going on.
>
> I will try to see if this also appears on the Snowball but I guess
> so?
>
> Any hints appreciated...
It looks like you're attempting to initialise MSP2 (HDMI). Why are you
doing that? Can you `git grep msp2` and provide me with the output
please?
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DMA screams on MSP
2014-02-04 13:36 ` Lee Jones
@ 2014-02-04 20:01 ` Linus Walleij
2014-02-04 20:38 ` Lee Jones
0 siblings, 1 reply; 4+ messages in thread
From: Linus Walleij @ 2014-02-04 20:01 UTC (permalink / raw)
To: Lee Jones; +Cc: alsa-devel@alsa-project.org, Mark Brown
On Tue, Feb 4, 2014 at 2:36 PM, Lee Jones <lee.jones@linaro.org> wrote:
>> I get this in my bootlog nowadays (v3.14-rc1):
>>
>> [ 2.713897] dma dma0chan29: [d40_validate_conf] Invalid device type
>> (14) physical channel exeeds available physical channels
>
> <snip>
>
>> (I patched dma40 to state the exact cause instead of just
>> "invalid device type".)
>>
>> Like something (I guess ALSA SoC?) is trying real hard to get physical
>> channel 14, but I can't seem to figure out what is going on.
>>
>> I will try to see if this also appears on the Snowball but I guess
>> so?
>>
>> Any hints appreciated...
>
> It looks like you're attempting to initialise MSP2 (HDMI). Why are you
> doing that? Can you `git grep msp2` and provide me with the output
> please?
This is just plain mainline, there is nothing special about my
git tree...
Yeah it appears I went in and marked msp2 "okay" in
commit 70b41abc151f9 so that is causing it, I'll make a
quick fix to get rid of that.
But no matter whether it gets activated or not: should it not just
work anyway? This message seems to suggest the DMA
channel assignment is invalid.
Yours,
Linus Walleij
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: DMA screams on MSP
2014-02-04 20:01 ` Linus Walleij
@ 2014-02-04 20:38 ` Lee Jones
0 siblings, 0 replies; 4+ messages in thread
From: Lee Jones @ 2014-02-04 20:38 UTC (permalink / raw)
To: Linus Walleij; +Cc: alsa-devel@alsa-project.org, Mark Brown
> >> I get this in my bootlog nowadays (v3.14-rc1):
> >>
> >> [ 2.713897] dma dma0chan29: [d40_validate_conf] Invalid device type
> >> (14) physical channel exeeds available physical channels
> >
> > <snip>
> >
> >> (I patched dma40 to state the exact cause instead of just
> >> "invalid device type".)
> >>
> >> Like something (I guess ALSA SoC?) is trying real hard to get physical
> >> channel 14, but I can't seem to figure out what is going on.
> >>
> >> I will try to see if this also appears on the Snowball but I guess
> >> so?
> >>
> >> Any hints appreciated...
> >
> > It looks like you're attempting to initialise MSP2 (HDMI). Why are you
> > doing that? Can you `git grep msp2` and provide me with the output
> > please?
>
> This is just plain mainline, there is nothing special about my
> git tree...
>
> Yeah it appears I went in and marked msp2 "okay" in
> commit 70b41abc151f9 so that is causing it, I'll make a
> quick fix to get rid of that.
>
> But no matter whether it gets activated or not: should it not just
> work anyway? This message seems to suggest the DMA
> channel assignment is invalid.
I haven't tested/debugged any of the physical channels, so I don't
know what could be the particular issue. It should work in theroy, I
can't think what might have changed. The channel is the same, as are
the markers to use fixed physical channel. Do you have a copy of the
old Igloo or the internal ST-E Kernel? I'm pretty sure HDMI sound
worked in those.
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-02-04 20:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-04 11:56 DMA screams on MSP Linus Walleij
2014-02-04 13:36 ` Lee Jones
2014-02-04 20:01 ` Linus Walleij
2014-02-04 20:38 ` Lee Jones
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.