From: Daniel Drake <dsd@laptop.org>
To: alsa-devel@alsa-project.org
Subject: Conexant CX20582 HDA codec support
Date: Mon, 29 Jun 2009 13:10:53 +0100 [thread overview]
Message-ID: <1246277454.2182.6.camel@polyethylene> (raw)
Hi,
I'm working on some sound issues with the new OLPC XO-1.5 alpha board.
This laptop is now based on a VIA VX855 chipset and our board includes a
CX20582-10Q HDA codec. We are running kernel v2.6.30.
We have a few issues, which are:
1. Volume range is ridiculous, you can go all the way down to -74dB
gain. Beyond -42dB you can barely hear anything from the speakers, and
I note that all my other systems only go down as far as -46.5dB.
2. No microphone automute. The internal microphone continues recording
sound while there is an external one plugged in.
3. No speaker automute. The internal speakers continue playing sound
while there are headphones plugged in.
4. Mixer arrangement is odd. There are 3 microphones: Mic, Mic 1, and
Mic 2. Mic (the default) records nothing. Mic 1 and Mic 2 both seem to
behave the same, and record from both internal and external microphones.
I looked into adding some quirks into patch_conexant.c to hopefully
solve some of the above. However I note that there is no support for the
CX20582, hence the generic HDA parser is being used. How has support for
the other CX chips been developed -- are datasheets always required?
(I'll try and get hold of one anyway)
Here is some more info.
codec dump
http://dev.laptop.org/~dsd/20090629/codec0.txt
codec graph
http://dev.laptop.org/~dsd/20090629/codecgraph.svg
lspci entry
http://dev.laptop.org/~dsd/20090629/lspci-entry.txt
verbose dmesg from probing
http://dev.laptop.org/~dsd/20090629/dmesg-probe.txt
Any thoughts/input appreciated!
Thanks,
Daniel
next reply other threads:[~2009-06-29 12:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 12:10 Daniel Drake [this message]
2009-06-29 12:26 ` Conexant CX20582 HDA codec support Mark Brown
2009-06-29 12:48 ` Takashi Iwai
2009-07-03 20:05 ` Daniel Drake
2009-07-03 20:45 ` Takashi Iwai
2009-06-29 12:50 ` Takashi Iwai
2009-06-30 18:48 ` Daniel Drake
2009-06-30 19:23 ` Tony Vroon
2009-06-30 19:27 ` Daniel Drake
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=1246277454.2182.6.camel@polyethylene \
--to=dsd@laptop.org \
--cc=alsa-devel@alsa-project.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 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.