On Tue, Mar 24, 2015 at 07:50:39AM +0100, David Henningsson wrote:
On 2015-03-23 17:41, Mark Brown wrote:
For headphone or headset, one hw switch only:
- "Headphone Jack"
- "Headset Mic Phantom Jack"
I'd have expected these to be the same thing, just with the second case always having the same state for both switches.
We need to distinguish the use cases: in case of independent switches, we can make the assumption that if the user plugged in a headset, the user wants to use the headset mic instead of the internal mic, so we switch to it.
In the other case, where we don't know if the user plugged in a headphone or a headset, we need to ask the user what (s)he plugged in, so we can determine whether to select headphone+internal mic or headphone+headset mic.
Hrm, I can see that. However it feels wrong to have no state change at all on the microphone part of the jack - I think I would have expected this case to be flagged as a separate mode, say "Tied", so that simpler applications have more chance to do the right thing. It's a bit of a separate issue though and it's a bit late now as we've already shipped the ABI for the kcontrols.