From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: Jack insertion Date: Tue, 18 Nov 2008 11:03:43 +0000 Message-ID: <20081118110341.GA23217@sirena.org.uk> References: 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 077A224512 for ; Tue, 18 Nov 2008 12:03:45 +0100 (CET) Content-Disposition: inline In-Reply-To: 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: naveen krishna ch Cc: alsa-devel@alsa-project.org, linux-omap@vger.kernel.org, linux-omap-open-source@linux.omap.com List-Id: alsa-devel@alsa-project.org On Tue, Nov 18, 2008 at 12:16:18PM +0530, naveen krishna ch wrote: > Now my issue is is there any work regarding the Headset JACK > insertion/detection. > Earlier there was a proposal for a jack insertion layer. > Can anyone suggest me in this regard. The generic ALSA part of the API has been merged already - see include/sound/jack.h. For ASoC drivers you need to implement the actual detection in your machine driver. Normally this would just hook into a GPIO. You can then update the DAPM widget for the jack to mark it as in use or not in use (some existing drivers do this) and also hook into the generic userspace API (that's not been implemented by anyone yet). Plan is to get something more generic into 2.6.30.