From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: spitz: add gpio button support (AK_INT and remote control description)
Date: Wed, 7 Oct 2009 13:06:44 +0100 [thread overview]
Message-ID: <20091007120643.GA17069@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1254914991.4213.80.camel@hammer.suse.cz>
On Wed, Oct 07, 2009 at 01:29:51PM +0200, Stanislav Brabec wrote:
> SW_REMOTE_INSERT should be recognized by the Jack abstraction layer
> (sound/core/jack.c).
It's the other way around - the jack layer reports jacks for ALSA cards.
Also, for spitz you'd probably want to be using the ASoC wrapper layer.
> Well, I am thinking about defining extra values for resistors, that can
> make stuff even more useful at cost of need of non-standard wiring on
> fourth ring of the audio jack. It can generate SW_MICROPHONE_INSERT,
> SW_LINEOUT_INSERT, and not yet defined SW_HEADESET_INSERT and
> SW_LINEIN_INSERT (which would require hardware mod inside Zaurus for
> stereo line-in).
Headset should be represented by reporting headphone plus microphone on
one jack simultaneously.
next prev parent reply other threads:[~2009-10-07 12:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 7:46 spitz: add gpio button support Pavel Machek
2009-10-06 11:48 ` spitz: add gpio button support (AK_INT and remote control description) Stanislav Brabec
2009-10-07 8:58 ` Pavel Machek
2009-10-07 11:29 ` Stanislav Brabec
2009-10-07 12:06 ` Mark Brown [this message]
2009-10-07 14:27 ` Eric Miao
2009-10-06 20:09 ` spitz: add gpio button support (fixes regression) Pavel Machek
2009-10-15 21:16 ` Stanislav Brabec
2009-10-15 21:20 ` Pavel Machek
2009-10-15 21:47 ` Stanislav Brabec
2009-10-15 21:52 ` Pavel Machek
2009-10-16 3:01 ` Eric Miao
2009-10-16 9:28 ` Stanislav Brabec
2009-10-16 9:39 ` Pavel Machek
2009-10-16 18:50 ` [PATCH] " Stanislav Brabec
2009-10-16 19:05 ` Russell King - ARM Linux
2009-10-16 22:22 ` Stanislav Brabec
2009-10-17 4:42 ` Eric Miao
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=20091007120643.GA17069@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).