From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Dmitry Torokhov <dtor@insightbb.com>,
linux-input@vger.kernel.org
Subject: Re: [alsa-devel] [0/2] Jack reporting
Date: Wed, 16 Jul 2008 13:02:35 +0200 [thread overview]
Message-ID: <s5hlk02148k.wl%tiwai@suse.de> (raw)
In-Reply-To: <20080714151058.GF25448@sirena.org.uk>
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
next prev parent reply other threads:[~2008-07-16 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 9:50 [0/2] Jack reporting Mark Brown
2008-07-03 9:52 ` [PATCH 1/2] Add jack reporting API for ALSA Mark Brown
2008-07-03 9:52 ` [PATCH 2/2] Add microphone and headset reporting Mark Brown
2008-07-14 15:11 ` [0/2] Jack reporting Mark Brown
2008-07-16 11:02 ` Takashi Iwai [this message]
2008-07-16 12:50 ` Mark Brown
2008-07-16 16:36 ` [alsa-devel] " Dmitry Torokhov
2008-07-17 10:31 ` Mark Brown
2008-07-20 5:23 ` Dmitry Torokhov
2008-07-20 12:17 ` Mark Brown
2008-07-20 15:23 ` Takashi Iwai
2008-07-20 19:30 ` Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hlk02148k.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dtor@insightbb.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox