[alsa-devel] questions about asoc jack detection

[Tobin Davis]

On Wed, 2011-04-20 at 23:00 +0800, Lu Guanqun wrote:
> On Wed, Apr 20, 2011 at 10:53:58PM +0800, Mark Brown wrote:
> > On Wed, Apr 20, 2011 at 10:06:15PM +0800, Lu Guanqun wrote:
> > 
> > > Yes, it's related to policy. But I see some inconsistencies in handling
> > > this stuff. In this above example, you suggest we should play out of
> > > both outputs. However in HDA code, the common way when headphone is
> > > inserted is to mute the speaker and enable the headphone. Is there some
> > > differences between the HDA code and the ASoC code? Or this is just due
> > > to legacy code?
> > 
> > HDA code does this differently.  I'd argue that they've taken the wrong
> > implementation decision and that this should be a userspace issue but
> > the use cases for PCs are a bit more basic.
> 
> I agree with you that this kind of policy should be put into userspace
> instead of hardcoding it in kernel.
> 
> Good to hear the points from you. Thanks!
> 
IIRC, the HDA jack detection code is pretty much legacy.  It has been
around longer than udev and other prior userspace hw detection systems.

That That doesn't mean it can't change.

-- 
Tobin Davis 

The Angels want to wear my red shoes.
		-- E. Costello