From: Liam Girdwood <lrg@slimlogic.co.uk>
To: jassi brar <jassisinghbrar@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"jassi.brar@samsung.com" <jassi.brar@samsung.com>,
"graeme.gregory@wolfsonmicro.com"
<graeme.gregory@wolfsonmicro.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
SeungHyun Choi <sh428.choi@samsung.com>
Subject: Re: Reforming s3c2443 ac97 driver
Date: Thu, 21 Jan 2010 10:37:47 +0000 [thread overview]
Message-ID: <1264070267.2396.92.camel@odin> (raw)
In-Reply-To: <1b68c6791001202258p7ef0ebcdt444a3be2eeaaff36@mail.gmail.com>
On Thu, 2010-01-21 at 15:58 +0900, jassi brar wrote:
> The s3c2443-ac97.c is used by SMDK2443 and LN2440SBC machines. My new
> driver is at least as good as old one for SMDK2443(both detect
> controller fine but none produce any sound..
> might be some h/w issue on the only board I have got).
It does sound like the AC97 link is up and running. What codec is used
here ?
> I have no access to LN2440SBC but there is no reason for it to
> complain.
> Besides, the new AC97 controller driver(plus a machine driver for
> SMDKs with WM9713 attached to AC97 port) has been tested on all
> SoCs that I could get my hands on(6410, C100, C110 and V210).
>
It would be good if you could also confirm that AC97 warm reset, AC97
cold reset and VRA (rates other than 48kHz) all work with the new
driver. Fwiw, it does sound like AC97 warm reset works since the WM9713
probes (it's default state requires warm reset to wake up the link).
Liam
next prev parent reply other threads:[~2010-01-21 10:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 5:28 Reforming s3c2443 ac97 driver JASWINDERSINGH BRAR
2010-01-08 5:53 ` Ben Dooks
2010-01-08 9:48 ` Mark Brown
2010-01-21 6:58 ` jassi brar
2010-01-21 10:03 ` Mark Brown
2010-01-21 10:37 ` Liam Girdwood [this message]
2010-01-21 11:22 ` jassi brar
2010-01-21 11:30 ` Mark Brown
2010-01-21 11:34 ` jassi brar
[not found] <0KWM003YNI0X6D@ms11.samsung.com>
2010-01-22 1:03 ` jassi brar
2010-01-22 1:04 ` Ben Dooks
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=1264070267.2396.92.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=graeme.gregory@wolfsonmicro.com \
--cc=jassi.brar@samsung.com \
--cc=jassisinghbrar@gmail.com \
--cc=sh428.choi@samsung.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 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).