[pulseaudio-discuss] [RFC] API for setting (default) port

Raymond Yau superquad.vortex2 at gmail.com
Wed May 13 19:08:36 PDT 2015

>> Since many years ago we have an API for setting default source/sink.
>>> Our default routing today is more port centric. So our UIs (at least the
>>> unity/gnome one) has developed ways around this, so that when a port is
>>> selected it first selects the right profile if needed.
>>> The problem is that in this world it's becoming more difficult to detect
>>> what the user actually wants, when the result is a chain of API calls. E
>>> g, if we first get a "set profile" call, we're not certain whether this
>>> is the user wanting to change the profile for the currently active port,
>>> or if this is the first part of a transition to a new port.
>> This problem description isn't really detailed enough for me to
>> understand what you're trying to solve.
> Ok. Assume you have 2.1 speakers, and headphones without full jack
> detection. (This is the case for some Dell laptops where the jack can be
> both used as headphone, headset and just mic, and the hardware cannot
> detect which one you plugged in.)
> Headphones are plugged in, and the user selects headphones manually.

Should the role of combo jack be defined by the driver when combo jack
support two or three roles ?

can user specify combo jack role as module parameter of snd-hda-intel when
the codec cannot  automatically differentiate headset and headphone ?

the driver use the combo jack parameter to set the role of the combo jack
1) headset - by remove hp mic pin and change headphone jack to headset jack
2) headphone - by remove hp mic pin and headset mic pin
3) mic  -- by set hp pin to mic pin and remove headset mic pin

driver can enable auto mic switch  when combo jack is set to single role
instead of asking the user whenever he plug the jack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20150514/607d75eb/attachment.html>

More information about the pulseaudio-discuss mailing list