From: Mark Brown <broonie@sirena.org.uk>
To: Russell King - ARM Linux <linux@arm.linux.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 13:33:37 +0100 [thread overview]
Message-ID: <20090402123337.GF4527@sirena.org.uk> (raw)
In-Reply-To: <20090402115541.GB9522@n2100.arm.linux.org.uk>
On Thu, Apr 02, 2009 at 12:55:41PM +0100, Russell King - ARM Linux wrote:
> On Tue, Mar 31, 2009 at 08:15:40PM +0100, Mark Brown wrote:
> > With a normal ASoC codec
> > driver the AC97 codec is not visible as a separate device in the device
> > tree - if you could point me to your machine driver that'd be helpful.
> Not true - the codec appears as /sys/devices/0-0:WM9705 rather than a
> sub-device of the AC97 controller. Below this there are two sub-devices:
Ah, I see what you mean - as you say that's actually the device for the
touch functionalty of the device rather than for the codec part which is
handled in soc-audio.
> /sys/devices/0-0:WM9705/wm97xx-battery
> /sys/devices/0-0:WM9705/wm97xx-touch
> The wm97xx-ts touchscreen driver binds to the 0-0:WM9705 device, so
> clearly unless 0-0:WM9705 is a child of the AC97 controller, things
> aren't going to be guaranteed to be resumed in the right order.
Right, the second patch I sent yesterday parents the device properly so
the ordering should now be OK there. Did you try using the generic AC97
driver? The code for handling the controller hardware is now shared
between the ASoC and that - if it fails with both that'd point at the
controller support.
next prev parent reply other threads:[~2009-04-02 12:33 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 [this message]
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
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=20090402123337.GF4527@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@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