From: Takashi Iwai <tiwai@suse.de>
To: phoenix.diablo@gmail.com
Cc: Raymond Yau <superquad.vortex2@gmail.com>,
alsa-devel@alsa-project.org, alex.baldacchino.alsasub@gmail.com,
haraldwelte@viatech.com, lydiawang <lydiawang@viatech.com.cn>
Subject: Re: Major reworks on patch_via.c (TESTERS WANTED)
Date: Tue, 05 Jul 2011 07:25:32 +0200 [thread overview]
Message-ID: <s5h1uy5guyb.wl%tiwai@suse.de> (raw)
In-Reply-To: <201107042137.46835.phoenix.diablo@gmail.com>
At Mon, 4 Jul 2011 21:37:46 +0200,
Jan Binder wrote:
>
> Am Mittwoch, 22. Juni 2011, 16:28:36 schrieb Takashi Iwai:
> > At Mon, 20 Jun 2011 17:06:51 +0200,
> >
> > Takashi Iwai wrote:
> > > Hi,
> > >
> > > as there have many problems reported for VIA codecs, I started looking
> > > at the driver code, and decided to rework on it.
> > > [snip]
>
> After not being able to compile the kernel from git, I now compiled modules
> from today's snapshot (up to 7b5017f56c69ef88f92e6472ec2578708b892211).
>
> I will describe what worked for me and what did not, as I lack the experience
> to point to details in the code.
>
> * When enabling Dynamic Power-Control in alsamixer, I get no sound, except on
> the internal SPDIF output.
OK, this and the third item make me wonder whether the jack-detection
works on your machine at all. Could you check it via hda-verb or
whatever?
> * Independent HP worked, when I could turn it on in alsamixer and correctly
> produced sound with aplay -Dhw:0,2,0 . I could not always reliably enable
> Independent HP in alsamixer, sometimes it would not change status ans aplay
> claimed that hw:0,2,0 was busy.
This is intentional. The switching is racy, so it can't be changed
safely when the multi-channel PCM is opened/used.
> * Headphone automute (muting rear line out when headphones are plugged in, if
> I understand correctly) does not seem to work in any setting.
See above.
> * I can only get SPDIF output from the internal connector on the mainboard
> (pin 0x20 if I interpret hda-analyzer correctly) and not from the SPDIF socket
> on the rear panel.
> It looks like this might be pin 0x21, which looks like an SPDIF Input in hda-
> analyzer, but the mainboard manual says that this should be an output.
You can change the pin 0x21 in user_pin_config sysfs file, then
trigger reconfig sysfs file dynamically. See
Documentation/sound/alsa/HD-Audio.txt file.
> * Output of alsa-info.sh is attached.
Thanks, I'll check it later.
Takashi
next prev parent reply other threads:[~2011-07-05 5:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 15:06 Major reworks on patch_via.c (TESTERS WANTED) Takashi Iwai
2011-06-20 15:16 ` Takashi Iwai
2011-06-21 10:01 ` David Henningsson
2011-06-21 11:01 ` Takashi Iwai
2011-06-21 11:38 ` David Henningsson
2011-06-21 12:28 ` Takashi Iwai
2011-06-22 8:02 ` Jan Binder
2011-06-22 8:52 ` Takashi Iwai
2011-06-22 14:28 ` Takashi Iwai
2011-07-02 16:00 ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-04 12:55 ` Takashi Iwai
2011-07-04 14:02 ` Takashi Iwai
2011-07-06 0:55 ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-06 0:49 ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-04 19:37 ` Jan Binder
2011-07-05 5:25 ` Takashi Iwai [this message]
2011-07-05 9:20 ` Raymond Yau
2011-07-06 0:58 ` alex dot baldacchino dot alsasub at gmail dot com
2011-07-15 6:03 ` 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=s5h1uy5guyb.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alex.baldacchino.alsasub@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=haraldwelte@viatech.com \
--cc=lydiawang@viatech.com.cn \
--cc=phoenix.diablo@gmail.com \
--cc=superquad.vortex2@gmail.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