linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 22:23:50 +0100	[thread overview]
Message-ID: <20130718212350.GC24642@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130718211521.GX22506@sirena.org.uk>

On Thu, Jul 18, 2013 at 10:15:21PM +0100, Mark Brown wrote:
> On Thu, Jul 18, 2013 at 10:06:37PM +0100, Mark Brown wrote:
> 
> > All those "Off" things mean that things are powered off which tends not
> > to involve them making any noise...  Russell mentioned that he thought
> > this was a lack of DAPM stuff however looking here it seems there are
> > some DAPM widgets on your board?
> 
> And now I think about it further the fix here is essentially that we
> require DAPM on any device that wants power management these days - DAIs
> are now widget based so it's going to be much more sensible to just go
> through and add the relevant output pins to relevant legacy drivers.
> 
> This means that for uda134x (which I think is what you're using here, I

No, this report is against ALC5623, which does appear to have widgets.
I was remarking that this looks like the same kind of issue I had with
UDA134x.

Note that the report indicates that the bias setting remains off while
playing, and ALC5623 does this:

        case SND_SOC_BIAS_OFF:
                /* everything off, dac mute, inactive */
                snd_soc_write(codec, ALC5623_PWR_MANAG_ADD2, 0);
                snd_soc_write(codec, ALC5623_PWR_MANAG_ADD3, 0);
                snd_soc_write(codec, ALC5623_PWR_MANAG_ADD1, 0);

So if everything on the codec is powered down, it's not surprising that
there is no audio output.

  reply	other threads:[~2013-07-18 21:23 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
2013-07-18 21:06     ` Mark Brown
2013-07-18 21:15       ` Mark Brown
2013-07-18 21:23         ` Russell King - ARM Linux [this message]
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=20130718212350.GC24642@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).