From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Audio issue on Kirkwood t5325: no sound
Date: Thu, 18 Jul 2013 16:42:06 +0100 [thread overview]
Message-ID: <20130718154206.GY24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130718173727.2cfa38d3@skate>
On Thu, Jul 18, 2013 at 05:37:27PM +0200, Thomas Petazzoni wrote:
> # for i in /sys/kernel/debug/asoc/t5325/dapm/* ; do echo $i ; cat "$i" ; done
> /sys/kernel/debug/asoc/t5325/dapm/Headphone Jack
> Headphone Jack: Off in 2 out 1
> in "static" "HPR"
> in "static" "HPL"
> /sys/kernel/debug/asoc/t5325/dapm/Mic Jack
> Mic Jack: Off in 1 out 0
> out "static" "MIC2"
> out "static" "MIC1"
> /sys/kernel/debug/asoc/t5325/dapm/Speaker
> Speaker: Off in 2 out 1
> in "static" "SPKOUTN"
> in "static" "SPKOUT"
> /sys/kernel/debug/asoc/t5325/dapm/bias_level
> Off
>
> I don't see anything that looks unreasonable in there, but I've never
> played with DAPM and related things, so it is very possible that my
> reasonable-guesser might be wrong on this.
The last one. I've seen that with the UDA134x driver too, where the bias
level stays in a low power state, resulting in no audio output. I fixed
it by adding DAPM to the UDA134x and my SA11x0 driver. Mark mentioned
something about virtual DAPM support must not be working correctly.
This needs an understanding of the DAPM code, which I'm told is just a
graph walk. However, trying to work out where stuff starts and how to
follow the code through the stages of state changes in soc-dapm.c has
proved to be quite an onerous task. I think there's only one or maybe
two people on this planet who understands that chunk of code.
At this point, you need Mark or Liam to sort this out.
next prev parent reply other threads:[~2013-07-18 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 11:43 Audio issue on Kirkwood t5325: no sound Thomas Petazzoni
2013-07-18 14:20 ` Russell King - ARM Linux
2013-07-18 15:37 ` Thomas Petazzoni
2013-07-18 15:42 ` Russell King - ARM Linux [this message]
2013-07-18 21:06 ` Mark Brown
2013-07-18 21:15 ` Mark Brown
2013-07-18 21:23 ` Russell King - ARM Linux
2013-07-18 21:52 ` 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=20130718154206.GY24642@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).