From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Aggarwal, Anuj" <anuj.aggarwal@ti.com>
Cc: 'Troy Kisky' <troy.kisky@boundarydevices.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Arun KS <arunks@mistralsolutions.com>
Subject: Re: [alsa-devel] [PATCH] ASoC: AM3517: Fix AIC23 suspend/resume hang
Date: Fri, 27 Nov 2009 11:42:46 +0000 [thread overview]
Message-ID: <20091127114245.GD29821@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB030AAC33B6@dbde02.ent.ti.com>
On Fri, Nov 27, 2009 at 01:37:54PM +0530, Aggarwal, Anuj wrote:
> [Aggarwal, Anuj] We were able to fine tune NFS and use arecord to capture
> large files. But some more problems cropped up when tried to suspend /
> resume. Basic playback is working fine wrt suspend/resume. But capture,
> either tried independently or with playback, is creating a system wide
> hang. I fixed that infinite-loop in resume path but I believe something
> else needs cleanup too.
> Any pointers?
Have you got CONFIG_DETECT_SOFTLOCKUP turned on? With any luck that
will at least pinpoint where the code has locked up. Otherwise it's
going to be a case of bisection via printk().
A contrast and compare of the hardware initialisation on initial boot
compared to coming out of suspend might identify the problem. If the
playback is working it's *probably* something missing in the CPU init
that's specific to capture.
next prev parent reply other threads:[~2009-11-27 11:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 13:10 [PATCH] ASoC: AM3517: Fix AIC23 suspend/resume hang Anuj Aggarwal
2009-11-25 13:33 ` Mark Brown
2009-11-25 19:19 ` Aggarwal, Anuj
2009-11-25 19:39 ` Mark Brown
2009-11-26 3:19 ` Aggarwal, Anuj
2009-11-25 20:22 ` Troy Kisky
2009-11-26 3:01 ` Aggarwal, Anuj
2009-11-26 10:22 ` [alsa-devel] " Mark Brown
2009-11-26 14:56 ` Aggarwal, Anuj
2009-11-26 15:11 ` Mark Brown
2009-11-26 15:22 ` Aggarwal, Anuj
2009-11-26 15:24 ` Aggarwal, Anuj
2009-11-26 15:29 ` Mark Brown
2009-11-27 8:07 ` Aggarwal, Anuj
2009-11-27 11:42 ` Mark Brown [this message]
2009-11-27 11:47 ` [alsa-devel] " Mark Brown
2009-11-26 15:42 ` Philby John
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=20091127114245.GD29821@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@ti.com \
--cc=arunks@mistralsolutions.com \
--cc=linux-omap@vger.kernel.org \
--cc=troy.kisky@boundarydevices.com \
/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.