From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
To: alsa-devel@alsa-project.org,
Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Han Lu <han.lu@intel.com>, Arun Raghavan <arun@accosted.net>
Subject: Separate input and output jacks for one UCM device?
Date: Wed, 18 Mar 2015 21:41:08 +0200 [thread overview]
Message-ID: <5509D4D4.6030000@linux.intel.com> (raw)
Hi Liam and alsa-devel,
My understanding is that a UCM device can represent a thing that has
both input and output (I don't particularly like that, but it's too late
to complain). How likely do you think that there are or there will be
some drivers that expose separate input and output jack kcontrols for a
headset jack, to differentiate between headphones/headset/microphone? My
understanding is that jack kcontrols store only booleans, so there's no
way to distinguish between headphones and a headset with just one kcontrol.
The current UCM "spec" doesn't support specifying multiple kcontrols,
since there's only one "JackControl" value. (Perhaps the "JackDev" value
suffers from this problem too, but I don't know if jack input devices
already support reporting the state separately for input and output.)
--
Tanu
next reply other threads:[~2015-03-18 19:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 19:41 Tanu Kaskinen [this message]
2015-03-19 9:15 ` Separate input and output jacks for one UCM device? Liam Girdwood
2015-03-19 14:09 ` Takashi Iwai
2015-03-19 14:19 ` Mark Brown
2015-03-19 14:22 ` Jie, Yang
2015-03-19 14:34 ` Takashi Iwai
2015-03-19 14:31 ` Jie, Yang
2015-03-19 14:37 ` Takashi Iwai
2015-03-19 14:42 ` Mark Brown
2015-03-19 14:51 ` Takashi Iwai
2015-03-19 15:18 ` Mark Brown
2015-03-19 15:28 ` Takashi Iwai
2015-03-19 15:45 ` Mark Brown
2015-03-20 4:03 ` Raymond Yau
2015-03-31 16:49 ` Tanu Kaskinen
2015-04-01 12:27 ` Liam Girdwood
2015-04-01 16:56 ` Tanu Kaskinen
2015-04-01 23:24 ` Raymond Yau
2015-04-02 6:39 ` Liam Girdwood
2015-04-02 15:28 ` Dylan Reid
2015-04-04 5:39 ` Raymond Yau
2015-04-06 9:26 ` Liam Girdwood
2015-04-07 3:00 ` Raymond Yau
2015-04-08 1:29 ` Raymond Yau
2015-04-07 20:37 ` Tanu Kaskinen
2015-04-15 15:39 ` Tanu Kaskinen
2015-04-15 16:10 ` Dylan Reid
2015-04-16 8:31 ` Tanu Kaskinen
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=5509D4D4.6030000@linux.intel.com \
--to=tanu.kaskinen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun@accosted.net \
--cc=han.lu@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
/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.