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:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
