From: Tanu Kaskinen <tanuk@iki.fi>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Headphone and headset jack control naming
Date: Tue, 15 Aug 2017 10:26:19 +0300 [thread overview]
Message-ID: <1502781979.2602.4.camel@iki.fi> (raw)
A user reported various audio problems with the Alienware 14 laptop in
the PulseAudio bugzilla. One of the problems is that the jack control
names that alsa reports are incorrect. However, I'm not sure what the
correct names would be, so I'd like to get that clarified (I will then
file a proper bug report in the kernel bugzilla).
The laptop has three physical jacks: headphone, headset and microphone.
In general, headset jacks have been so far represented by two jack
controls: "Headphone" + "Headset Mic" (or is "Headphone" + "Mic" more
common? I think I've seen both being used). However, in this case
there's also a headphone-only jack. Should we invent a new name for
headset outputs, so that the headphone and headset outputs can be
distinguished, or should there be two "Headphone" controls, or should
one of the controls (which one?) use the "Headphone2" name that is
already used by some hardware?
FWIW, currently the output jack control names on Alienware 14 are
"Headphone Front" for the headset jack and "Headphone Surround" for the
headphone jack, which I assume we all agree is incorrect. Furthermore,
there's no "Headset Mic" jack control, or any other control
corresponding to the headset mic. "Mic" control exists, but it
corresponds to the separate microphone jack.
--
Tanu
https://www.patreon.com/tanuk
reply other threads:[~2017-08-15 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1502781979.2602.4.camel@iki.fi \
--to=tanuk@iki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox