From: Takashi Iwai Subject: Re: Jack event API - decision needed Date: Wed, 29 Jun 2011 07:34:11 +0200 Message-ID: References: <4DFF4D15.6050809@canonical.com> <20110627120743.GA20707@sirena.org.uk> <4E0A00E3.5000102@canonical.com> <20110629025916.GA22472@opensource.wolfsonmicro.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id F2DE724697 for ; Wed, 29 Jun 2011 07:34:14 +0200 (CEST) In-Reply-To: <20110629025916.GA22472@opensource.wolfsonmicro.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: Mark Brown Cc: ALSA Development Mailing List , Kay Sievers , Lennart Poettering , David Henningsson List-Id: alsa-devel@alsa-project.org At Tue, 28 Jun 2011 19:59:18 -0700, Mark Brown wrote: > > On Tue, Jun 28, 2011 at 06:35:33PM +0200, Takashi Iwai wrote: > > > If only the same functionality is required as currently done in the > > input-jack layer, re-implementing the jack-detection elements in ALSA > > control API is pretty easy. It means that the control element would > > have some jack name with a location prefix or such, reports the > > current jack status, and notifies the jack change. That's all. > > Optionally, it can have a TLV data giving the HD-audio jack > > attribute, too. > > It needs a subset of the current information - it should report only > audio events, so pretty much only headphone, microphone or line out > presence. Is that really all for PA, for now, and even for future? That's my primary question. Was this clarified in the thread...? > Anything else needs to be reported via a different API and > figured out by userspace, and the input device should stay there for > button press events. The first and the second part are independent, IMO. That is, whether using the input-jack device in future is an open question. It might be better to re-implement in a new API in a unified way, for example. Of course, keeping the old API is mandatory, so we'll still keep the input-jack code in future, though. thanks, Takashi