From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: [Survey] headphone <-> master volume swap -- which codec chip?
Date: Fri, 24 Jan 2003 12:27:46 +0100 [thread overview]
Message-ID: <s5hn0lqyeh9.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301241213200.1448-100000@pnote.perex-int.cz>
At Fri, 24 Jan 2003 12:16:00 +0100 (CET),
Jaroslav wrote:
>
> On Fri, 24 Jan 2003, Takashi Iwai wrote:
>
> > Hi all,
> >
> > there have been bug-reports regarding to the swapping of headphone
> > and master volumes.
> > i'd like to ask you to check which AC97 codec chip is used on which
> > board (or laptop) if you have such a problem. if this happens only on
> > a certain chip model, we can add a quirk for that.
>
> Takashi, this quirk can be done only by detection of subvendor and
> subsystem from the PCI ID space.
yeah, the lspci output is on the query list.
> It's absolutely irrelevant which AC97
> chip is used.
really? i believe this happens only on certain ac97 chips.
for example, ALC202 spec says that ALC202A uses the headphone volume
as the "true line out" volume. so, apparently, some ac97 chips
"recommend" this behavior. let's see...
> Vendor might wire codec in any way. Also, some codecs may
> swap line-out / headphone out via registers.
this is a different case, imo.
the problem is that we have no chance to detect/switch them, either
manually or automatically.
a general solution would be to add an ac97 control switch to swap
them. then the accssed registers are exchanged internally according
to this control.
but it isn't bad to know which chips and which machines have this
problem, so that we can add quirks to turn on this switch
automatically.
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next prev parent reply other threads:[~2003-01-24 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 10:06 [Survey] headphone <-> master volume swap -- which codec chip? Takashi Iwai
[not found] ` <3E311B10.6070901@esat.kuleuven.ac.be>
2003-01-24 11:00 ` Takashi Iwai
[not found] ` <3E312127.6020500@esat.kuleuven.ac.be>
2003-01-27 11:15 ` Takashi Iwai
2003-01-24 11:16 ` Jaroslav Kysela
2003-01-24 11:27 ` Takashi Iwai [this message]
2003-01-24 12:41 ` Pieter Palmers
2003-01-24 14:41 ` Takashi Iwai
2003-01-24 15:48 ` Takashi Iwai
2003-01-24 17:09 ` Takashi Iwai
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=s5hn0lqyeh9.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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.