From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org, eric miao <eric.y.miao@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: SoC pxa2xx-ac97 + wm9705 + touchscreen suspend/resume
Date: Thu, 2 Apr 2009 15:40:17 +0100 [thread overview]
Message-ID: <20090402144017.GI9522@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20090402141200.GH4527@sirena.org.uk>
On Thu, Apr 02, 2009 at 03:12:01PM +0100, Mark Brown wrote:
> Before doing that could you please try the patch below to wm9705.c
> implementing suspend and resume operations? It's completely
> speculative, I don't have a WM9705 test system to hand but I'm
> moderately confident
No real change - since I got rid of the debug printk's I scattered in
last time around, I don't know if this patch has changed anything.
It's actually worse though - using my devmem2 hack no longer restores
things to a functional state. devmem2 says the control register is
now set as:
Value at address 0x4050000C: 0xC0002
but I'm still seeing lots of:
pxa2xx_ac97_write: write error (ac97_reg=118 GSR=0x0)
pxa2xx_ac97_read: read error (ac97_reg=118 GSR=0x0)
pxa2xx_ac97_read: read error (ac97_reg=118 GSR=0x0)
pxa2xx_ac97_read: read error (ac97_reg=118 GSR=0x0)
...
messages. Before, setting the control register to '2' (thereby
releasing the cold reset) caused things to start working again.
next prev parent reply other threads:[~2009-04-02 14:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 22:37 SoC pxa2xx-ac97 + wm9705 + touchscreen suspend/resume Russell King - ARM Linux
2009-03-31 10:30 ` Mark Brown
2009-03-31 18:37 ` Russell King - ARM Linux
2009-03-31 19:15 ` Mark Brown
2009-04-02 11:55 ` Russell King - ARM Linux
2009-04-02 12:33 ` Mark Brown
2009-04-01 19:27 ` Mark Brown
2009-04-02 12:13 ` Russell King - ARM Linux
2009-04-02 12:18 ` Mark Brown
2009-04-02 12:38 ` Russell King - ARM Linux
2009-04-02 13:31 ` Russell King - ARM Linux
2009-04-02 14:12 ` Mark Brown
2009-04-02 14:40 ` Russell King - ARM Linux [this message]
2009-04-02 14:53 ` Mark Brown
2009-04-02 15:09 ` Russell King - ARM Linux
2009-04-02 15:22 ` Mark Brown
2009-04-18 9:11 ` Russell King - ARM Linux
2009-04-18 9:47 ` Mark Brown
2009-04-02 16:13 ` Ian Molton
2009-03-31 15:51 ` Liam Girdwood
2009-03-31 20:58 ` Ian Molton
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=20090402144017.GI9522@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=lrg@slimlogic.co.uk \
/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