linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel 2.6.33: PXA270 Audio does not resume after resume from suspend state
Date: Thu, 22 Jul 2010 17:15:31 +0200	[thread overview]
Message-ID: <20100722151530.GI17833@buzzloop.caiaq.de> (raw)
In-Reply-To: <AANLkTiloYpM6LBNFHOfHGdvoHZ03cavW8vdmVZjHxSKC@mail.gmail.com>

On Tue, Jun 08, 2010 at 10:38:36AM -0400, Shane Volpe wrote:
> I have upgraded an embedded system (PXA270) to the 2.6.33 kernel (from
> 2.6.23).  Now when I run an audio program (ogg123) and put the system
> into standby then wake the system up the audio does not work (continue
> playing) after resume until I terminate ogg123 and start again.  After
> restarting ogg123 the audio works fine with out reseting the system or
> changing anything else on the system.
> 
> The system is using the UCB1400 AC97 codec and just as added
> information when the audio is locked up, after resume, the touchscreen
> on the system still works which is also controlled by the UCB1400
> audio codec.  I have also tried several other audio players and the
> results are the same.   Has anyone else seen this bug and does anyone
> have suggestions on further tests to perform to narrow down were the
> bug may reside?

I've had similar issues some time ago. However, we used I2S over SSP for
our system, not AC97, and suspend/resume works fine now.

You may have a look at commit 026384d614b ("ASoC: fix PXA SSP port
resume") and check whether something similar must be done for the AC97
controller part.

Daniel

      reply	other threads:[~2010-07-22 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 14:38 Kernel 2.6.33: PXA270 Audio does not resume after resume from suspend state Shane Volpe
2010-07-22 15:15 ` Daniel Mack [this message]

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=20100722151530.GI17833@buzzloop.caiaq.de \
    --to=daniel@caiaq.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).