From: Tony Vroon <tony@linx.net>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>
Subject: [ALC262 patch_realtek.c] Fujitsu Lifebook PC speaker signal
Date: Thu, 10 Apr 2008 12:10:41 +0100 [thread overview]
Message-ID: <1207825841.5651.20.camel@localhost> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 421 bytes --]
Good afternoon,
Could you please consider the following patch for the 2.6.26 merge window.
The legacy PC speaker signal was not routed to outputs. The codec is not
prevented from powering down in this patch, although I suppose one could
argue that perhaps it should be. Let me know if anyone feels strongly one
way or the other.
Signed-Off-By: Tony Vroon <tony@linx.net>
Regards,
Tony V.
LINX sysadmin
[-- Attachment #1.1.2: alc262-fujitsu-pcspk.patch --]
[-- Type: text/x-patch, Size: 617 bytes --]
--- sound/pci/hda/patch_realtek.c.OLD 2008-04-10 11:52:23.000000000 +0100
+++ sound/pci/hda/patch_realtek.c 2008-04-10 11:50:29.000000000 +0100
@@ -8065,6 +8065,8 @@
},
HDA_CODEC_VOLUME("CD Playback Volume", 0x0b, 0x04, HDA_INPUT),
HDA_CODEC_MUTE("CD Playback Switch", 0x0b, 0x04, HDA_INPUT),
+ HDA_CODEC_VOLUME("PC Speaker Volume", 0x0b, 0x05, HDA_INPUT),
+ HDA_CODEC_MUTE("PC Speaker Switch", 0x0b, 0x05, HDA_INPUT),
HDA_CODEC_VOLUME("Mic Boost", 0x18, 0, HDA_INPUT),
HDA_CODEC_VOLUME("Mic Playback Volume", 0x0b, 0x0, HDA_INPUT),
HDA_CODEC_MUTE("Mic Playback Switch", 0x0b, 0x0, HDA_INPUT),
[-- 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:[~2008-04-10 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 11:10 Tony Vroon [this message]
2008-04-14 10:34 ` [ALC262 patch_realtek.c] Fujitsu Lifebook PC speaker signal 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=1207825841.5651.20.camel@localhost \
--to=tony@linx.net \
--cc=alsa-devel@alsa-project.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 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.