From: Takashi Iwai Subject: Re: Jack event API - decision needed Date: Wed, 29 Jun 2011 09:03:39 +0200 Message-ID: References: <4DFF4D15.6050809@canonical.com> <20110627120743.GA20707@sirena.org.uk> <4E0A00E3.5000102@canonical.com> <20110629025916.GA22472@opensource.wolfsonmicro.com> <20110629065940.GA25977@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 993C310385C for ; Wed, 29 Jun 2011 09:03:40 +0200 (CEST) In-Reply-To: <20110629065940.GA25977@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 23:59:41 -0700, Mark Brown wrote: > > > > 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. > > You're missing my point here. The point is not the switches, the point > is the buttons on the jacks - they need to go via the input API and not > the ALSA API. OK, buttons. How confusing terminologies are... thanks, Takashi