From: Tony Vroon <tony@linx.net>
To: alsa-devel@alsa-project.org
Subject: Recalcitrant input pin on ALC262
Date: Sun, 01 Feb 2009 20:56:40 +0000 [thread overview]
Message-ID: <1233521800.3811.4.camel@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 956 bytes --]
Good evening,
Currently I am implementing full support for the Tyan Thunder n6650W and
have noticed a pin complex that advertises input, but can't seem to be
set to it:
Node 0x1c [Pin Complex] wcaps 0x400001: Stereo
Pincap 0x00000020: IN
Pin Default 0x411111f0: [N/A] Speaker at Ext Rear
Conn = 1/8, Color = Black
DefAssociation = 0xf, Sequence = 0x0
Misc = NO_PRESENCE
Pin-ctls: 0x00:
As you can see the pin capabilities reflect input. However, even after
issuing this in the model-specific verbs:
{0x1c, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_IN},
the pin-ctls firmly remains 0x00. Even the python-based hda-analyzer
appears unable to flip the pin-ctls over to 0x20 and reports no error
messages in the GUI or in the terminal.
What am I missing please?
Slightly related, is it considered acceptable to modify pin defaults if
they are blatantly wrong? (Reported colour, N/A vs Fixed, etc)
Regards,
Tony V.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2009-02-01 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 20:56 Tony Vroon [this message]
2009-02-02 6:50 ` Recalcitrant input pin on ALC262 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=1233521800.3811.4.camel@localhost \
--to=tony@linx.net \
--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.