From: Richard Purdie <rpurdie@rpsys.net>
To: Daniel Mack <daniel@caiaq.de>
Cc: linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Constantin Baranov <const@mimas.ru>
Subject: Re: [PATCH] leds-alix2: add support for button connected to J15
Date: Sun, 18 Oct 2009 11:56:52 +0100 [thread overview]
Message-ID: <1255863412.27878.136.camel@ted> (raw)
In-Reply-To: <20091016130315.GT28832@buzzloop.caiaq.de>
Hi,
On Fri, 2009-10-16 at 15:03 +0200, Daniel Mack wrote:
> for a project I was working on, we used the J15 connector of the ALIX.2D
> board (which is connected to a GPIO of the CS5536 Geode companion chip)
> for an external button switch.
>
> I thought it might be worth sharing this piece of code, so others can do
> the same.
>
> There is, however, a small hardware modification is necessary as the pin
> is also shared as buzzer output. I noted that in the Kconfig entry.
>
> The patch should go thru Richard's led-2.6.git as it depends on another
> one that has been queued there already.
How common is this modification? I'm just trying to get a feel for the
number of users out there of this feature...
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next prev parent reply other threads:[~2009-10-18 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 13:03 [PATCH] leds-alix2: add support for button connected to J15 Daniel Mack
2009-10-18 7:27 ` Dmitry Torokhov
2009-10-19 7:37 ` Daniel Mack
2009-10-20 1:38 ` Dmitry Torokhov
2009-10-20 10:13 ` Daniel Mack
2009-10-21 4:35 ` Dmitry Torokhov
2009-10-21 19:33 ` Daniel Mack
2009-10-21 20:21 ` Constantin Baranov
2009-10-21 20:41 ` Daniel Mack
2009-10-21 21:39 ` Constantin Baranov
2009-10-21 22:09 ` Constantin Baranov
2009-10-22 10:11 ` Daniel Mack
2009-10-18 10:56 ` Richard Purdie [this message]
2009-10-19 7:16 ` Daniel Mack
2009-10-22 10:29 ` Pavel Machek
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=1255863412.27878.136.camel@ted \
--to=rpurdie@rpsys.net \
--cc=const@mimas.ru \
--cc=daniel@caiaq.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).