From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, linux-input@vger.kernel.org
Subject: Re: [alsa-devel] [0/2] Jack reporting
Date: Thu, 17 Jul 2008 11:31:12 +0100 [thread overview]
Message-ID: <20080717103111.GB15333@sirena.org.uk> (raw)
In-Reply-To: <20080716112939.ZZRA012@mailhub.coreip.homeip.net>
On Wed, Jul 16, 2008 at 12:36:06PM -0400, Dmitry Torokhov wrote:
> On Wed, Jul 16, 2008 at 01:50:53PM +0100, Mark Brown wrote:
> > As well as detecting the presence of a connected device typical jack
> > detection implementations also support the implementation of at least
> > one button which would require an input device for at least some jacks
> It really depends on what you can do with this button. If it is just a
> simple circuit breaker then it is not really an input device. However
> is you can remap it for different purposes or map a regular key on a
> keybaord to perform this function then I will agree with you. For example
As far as the hardware is concerned it's just a button - if it's visible
to software then there's no fixed function for it and any action taken
will be application/system specific. There will normally be a side
effect in hardware muting the microphone but that's not intended to be
the main effect.
next prev parent reply other threads:[~2008-07-17 10:31 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 ` [alsa-devel] " Takashi Iwai
2008-07-16 12:50 ` Mark Brown
2008-07-16 16:36 ` [alsa-devel] " Dmitry Torokhov
2008-07-17 10:31 ` Mark Brown [this message]
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=20080717103111.GB15333@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=tiwai@suse.de \
/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