[alsa-devel] Jack detection on HDA vs SoC

Dylan Reid dgreid at chromium.org
Mon Feb 6 08:56:40 CET 2012

On Sat, Feb 4, 2012 at 5:20 AM, Mark Brown
<broonie at opensource.wolfsonmicro.com> wrote:
> On Fri, Feb 03, 2012 at 06:01:41PM -0800, Dylan Reid wrote:
> You're more likely to get responses to mails if you CC maintainers.
>> Is there a plan for the soc code to use the control-based method?
> Not exactly.  I'm expecting that the new interface will be integrated
> into the generic ALSA jack support rather than done as a custom thing in
> the HDA drivers which will mean that anything supporting accessory
> detect will get support, including ASoC.  This stuff should really be
> handled in the core rather than in individual drivers, there's also
> extcon which we'll need to integrate with.
>> Is there a consensus on whether new drivers should auto-switch or not?
> For embedded systems they definitely should not, it's frequently
> inappropriate (the most common case is things like ringtones which many
> userspaces think should always play to speaker so people can hear them
> even if they have removed their headphones).  I think the consensus was
> to move the PC audio to supporting runtime switching between the two
> modes so that if PulseAudio or whatever userspace sound manager is there
> wants to it can take control and do the switching for cases like the
> above.

Thanks for the responses Mark. A control that can disable auto switching
sounds like a good solution to me.  Certainly better than checking for x86 or
arm.  I see a couple of drivers already doing this, so I can follow their lead.

More information about the Alsa-devel mailing list