From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: [alsa-devel] [0/2] Jack reporting Date: Wed, 16 Jul 2008 13:02:35 +0200 Message-ID: References: <20080703095026.GA652@sirena.org.uk> <20080714151058.GF25448@sirena.org.uk> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <20080714151058.GF25448@sirena.org.uk> Sender: linux-input-owner@vger.kernel.org To: Mark Brown Cc: alsa-devel@alsa-project.org, Dmitry Torokhov , linux-input@vger.kernel.org List-Id: alsa-devel@alsa-project.org At Mon, 14 Jul 2008 16:11:00 +0100, Mark Brown wrote: > > On Thu, Jul 03, 2008 at 10:50:27AM +0100, Mark Brown wrote: > > This is a repost of the the jack reporting API I posted recently. There > > are no chances since the last submission - as discussed in that thread > > the existing users and the need to support buttons implemented in jacks > > pushes me towards use of an input device to represent jacks. > > Takashi, do you have any comments on these patches? I have no strong opinion about this. Your implementation looks small enough. But, if Dmitry finds the input layer not suitable for such a purpose, this isn't a good way to go. I think the question is how general and how extensible these features should be. If it's just a jack reporting, there are bunch of other possible implementations. Even ALSA control API could provide a similar functionality. Takashi