From: Mark Brown Subject: Re: questions about asoc jack detection Date: Wed, 20 Apr 2011 15:53:58 +0100 Message-ID: <20110420145358.GB25571@sirena.org.uk> References: <20110420065212.GC21880@qtel.sh.intel.com> <20110420093102.GA4097@opensource.wolfsonmicro.com> <20110420140615.GK9074@qtel.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id 264501038B5 for ; Wed, 20 Apr 2011 16:54:02 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20110420140615.GK9074@qtel.sh.intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Lu Guanqun Cc: "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org 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.