Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753443AbbFLMuK (ORCPT ); Fri, 12 Jun 2015 08:50:10 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:41778 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750753AbbFLMuH (ORCPT ); Fri, 12 Jun 2015 08:50:07 -0400 Date: Fri, 12 Jun 2015 13:50:05 +0100 From: Charles Keepax To: Zidan Wang Cc: broonie@kernel.org, lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.de, lars@metafoo.de, patches@opensource.wolfsonmicro.com, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: [alsa-devel][PATCH 2/4] ASoC: wm8960: support configure headphone jack detect pin and polarity from device tree Message-ID: <20150612125005.GI32730@opensource.wolfsonmicro.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 26 On Thu, Jun 11, 2015 at 07:14:34PM +0800, Zidan Wang wrote: > The ADCLRC/GPIO1, LINPUT3/JD2 and RINPUT3/JD3 pins can be selected as > headphone jack detect inputs to automatically disable the speaker output > and enable the headphone. > > Signed-off-by: Zidan Wang > --- This feels like this is missing some iteraction with DAPM, there are DAPM widgets that represent both the Speaker and the Headphone, in the case this feature is in use the power state DAPM shows may no longer accurately reflects the actual power state of the device. That said I have no idea if the registers update on the chip to reflect this change (my guess is that they don't). I am not really sure what the correct way to handle this sort of hardware output switching would be in DAPM. Thanks, Charles -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/