From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, "Andrius Štikonas" <stikonas@gmail.com>
Subject: Re: Problems with Intel HDA driver
Date: Mon, 14 Sep 2009 16:15:02 +0300 [thread overview]
Message-ID: <4AAE41D6.1020600@pardus.org.tr> (raw)
In-Reply-To: <s5h3a6pln35.wl%tiwai@suse.de>
Takashi Iwai wrote On 14-09-2009 15:36:
>
> Yeah, I think we can add EAPD handling as default for IDT92HD71xx
> codecs. I've never seen machines that can't live with GPIO0 bit up.
>
enable_msi doesn't seem to affect the auto-muting problem. I played with
every single node in hda-analyzer but can't get auto-mute work. I can
manually mute the HP output and the internal speakers by
checking/unchecking OUT checkboxes on relevant NIDs. There's a 8xn
matrix for GPIO settings, I played with them as well to set unsol but nope.
I want to remember that dell-m4-1 makes automute work but breaks the
mixer channels:
http://www.spinics.net/lists/alsa-devel/msg26714.html
Err, I know that I didn't answer the last question in the thread as I'm
a little bit lost in the NID pool and didn't have time to investigate
further.
next prev parent reply other threads:[~2009-09-14 13:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 11:33 Problems with Intel HDA driver Andrius Štikonas
2009-09-14 12:25 ` Takashi Iwai
2009-09-14 12:36 ` Ozan Çağlayan
2009-09-14 12:36 ` Takashi Iwai
2009-09-14 13:15 ` Ozan Çağlayan [this message]
2009-09-14 13:15 ` Takashi Iwai
2009-09-14 13:23 ` Takashi Iwai
2009-09-14 13:41 ` Ozan Çağlayan
2009-09-14 13:46 ` Takashi Iwai
2009-09-15 9:04 ` Ozan Çağlayan
2009-09-15 12:58 ` Takashi Iwai
2009-09-27 20:23 ` Munzir Taha (منذر طه)
-- strict thread matches above, loose matches on Subject: below --
2009-09-27 20:27 Munzir Taha (منذر طه)
2009-09-27 20:44 ` Daniel Chen
2009-09-27 21:01 ` Munzir Taha (منذر طه)
2009-09-27 21:03 ` Daniel Chen
2009-09-27 21:31 ` Munzir Taha (منذر طه)
2009-09-27 21:53 ` Daniel Chen
2009-09-27 21:58 ` Munzir Taha (منذر طه)
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=4AAE41D6.1020600@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=alsa-devel@alsa-project.org \
--cc=stikonas@gmail.com \
--cc=tiwai@suse.de \
/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