From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Takashi Iwai" <tiwai@suse.de>
Cc: "Daniel J Blueman" <daniel.blueman@gmail.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: ALC883 recording troubles...
Date: Thu, 12 Jun 2008 19:29:57 +0200 [thread overview]
Message-ID: <19f34abd0806121029j1f9cabf0nc852c6e1a0a98d4f@mail.gmail.com> (raw)
In-Reply-To: <19f34abd0806120955r4734bca8h44774bacc65aca37@mail.gmail.com>
On Thu, Jun 12, 2008 at 6:55 PM, Vegard Nossum <vegard.nossum@gmail.com> wrote:
> Now I consulted the HDA specification, and I find this surprising:
>
> Verb 3h (set Amplifier Gain/Mute) has the following payload bits:
>
> 15 Set Output Amp
> 14 Set Input Amp
>
> ...but the payloads that I logged (a01a and 901a) would correspond to
> bit 15 being set, which is the Output Amp!
I applied this as well, just to make sure, and I tested again:
@@ -906,6 +908,9 @@ int snd_hda_codec_amp_update(struct hda_codec
*codec, hda_nid_t nid, int ch,
{
struct hda_amp_info *info;
+ printk(KERN_ERR "snd_hda_codec_amp_update(): direction = %s\n",
+ direction == HDA_OUTPUT ? "output" : "input");
+
info = get_alloc_amp_hash(codec, HDA_HASH_KEY(nid, direction, idx));
if (!info)
return 0;
..and yes, changing the "Capture" level does indeed set the Output bit
when modifying this control. Maybe there's something wrong with the
set-up of mixer or pin controls that makes ALSA think this is an
output stream?
Is there something strange here:
Node 0x18 [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Pin Default 0x02a19840: [Jack] Mic at Ext Front
Node 0x19 [Pin Complex] wcaps 0x40008b: Stereo Amp-In
Pin Default 0x99a30941: [Fixed] Mic at Int ATAPI
Node 0x1a [Pin Complex] wcaps 0x40018f: Stereo Amp-In Amp-Out
Pin Default 0x0281304e: [Jack] Line In at Ext Front
..or it certainly seems that all the inputs claim to have output
capability too. Maybe this is what is confusing ALSA?
I will try to change the Gain/Mute levels manually using hda-verb
using the Input bit instead of Output and see how it goes.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-06-12 17:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 19:59 Daniel J Blueman
2008-06-10 5:59 ` Takashi Iwai
2008-06-11 19:00 ` Daniel J Blueman
2008-06-11 21:37 ` Daniel J Blueman
2008-06-12 10:45 ` Takashi Iwai
2008-06-12 10:49 ` Takashi Iwai
2008-06-12 13:03 ` Vegard Nossum
2008-06-12 13:12 ` Takashi Iwai
2008-06-12 13:48 ` Vegard Nossum
2008-06-12 13:52 ` Takashi Iwai
2008-06-12 13:55 ` Vegard Nossum
2008-06-12 14:01 ` Vegard Nossum
2008-06-12 14:13 ` Takashi Iwai
2008-06-12 14:02 ` Takashi Iwai
2008-06-12 14:18 ` Vegard Nossum
2008-06-12 14:23 ` Takashi Iwai
2008-06-12 14:58 ` Daniel J Blueman
2008-06-12 15:18 ` Takashi Iwai
2008-06-12 16:55 ` Vegard Nossum
2008-06-12 17:29 ` Vegard Nossum [this message]
2008-06-12 17:53 ` Takashi Iwai
2008-06-12 18:31 ` Vegard Nossum
2008-06-12 21:50 ` Daniel J Blueman
2008-06-13 10:38 ` Romano Giannetti
2008-06-28 0:05 ` Daniel J Blueman
[not found] ` <19f34abd0806280311s115062e6vc6d0f304cb744934@mail.gmail.com>
[not found] ` <6278d2220806280329j2f77c52dp8fbae78420c136c1@mail.gmail.com>
2008-06-28 12:29 ` Daniel J Blueman
2008-06-28 12:39 ` Vegard Nossum
2008-06-28 13:24 ` Daniel J Blueman
2008-06-28 13:46 ` Vegard Nossum
2008-06-29 17:29 ` Romano Giannetti
2008-06-29 21:33 ` Daniel J Blueman
2008-08-14 19:10 ` Daniel J Blueman
2008-08-15 14:42 ` Takashi Iwai
2008-08-15 22:01 ` Daniel J Blueman
2008-08-16 8:38 ` Takashi Iwai
2008-08-16 13:37 ` Daniel J Blueman
2008-08-16 17:00 ` Takashi Iwai
2008-08-16 17:33 ` Daniel J Blueman
2008-08-17 8:04 ` Takashi Iwai
2008-06-10 12:22 ` Romano Giannetti
2008-06-10 12:53 ` Vegard Nossum
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=19f34abd0806121029j1f9cabf0nc852c6e1a0a98d4f@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=daniel.blueman@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®