From: dbaryshkov@gmail.com (Dmitry Eremin-Solenikov)
To: linux-arm-kernel@lists.infradead.org
Subject: gpio_keys and how PXA27x sets gpio_set_wake() (was Re: sharp c-3000 aka spitz: fix warn_on introduced in 2.6.32-rc1)
Date: Tue, 26 Jan 2010 14:23:56 +0300 [thread overview]
Message-ID: <bc64b4641001260323y496bf7cdv507085644fadb0fe@mail.gmail.com> (raw)
In-Reply-To: <1264502668.4480.97.camel@utx.utx.cz>
Hello,
2010/1/26 Stanislav Brabec <utx@penguin.cz>:
> Eric Miao wrote:
>> > The problem affects gpio_keys: It is a driver implementing "one key per
>> > gpio". It now handles On/Off and lid switches on Zaurus. Lid switches
>> > are on "normal" GPIOs, On/Off switch is wired to PKWR capable GPIO.
>> Ain't On/Off switch one of the matrix key? And so SPITZ_GPIO_KEY_INT
>> could be used to handle that?
>
> No. On/Off is connected directly to GPIO 95. Other keys use strobe/sense
> matrix keypad.
>
> SPITZ_GPIO_KEY_INT is a bit unspecific. I think it means: Charger was
> inserted or key was pressed or On/Off was pressed.
This seems to be true. At least they used the same design on tosa and other
zaurii.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2010-01-26 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 7:10 sharp c-3000 aka spitz: fix warn_on introduced in 2.6.32-rc1 Pavel Machek
2010-01-06 7:17 ` Eric Miao
2010-01-07 6:52 ` Pavel Machek
2010-01-07 7:33 ` Eric Miao
2010-01-23 19:41 ` Stanislav Brabec
2010-01-23 22:43 ` gpio_keys and how PXA27x sets gpio_set_wake() (was Re: sharp c-3000 aka spitz: fix warn_on introduced in 2.6.32-rc1) Stanislav Brabec
2010-01-26 3:58 ` Eric Miao
2010-01-26 10:13 ` Stanislav Brabec
2010-01-26 10:20 ` Eric Miao
2010-01-26 10:44 ` Stanislav Brabec
2010-01-26 11:23 ` Dmitry Eremin-Solenikov [this message]
2010-01-26 11:39 ` Eric Miao
2010-01-26 12:50 ` Stanislav Brabec
2010-03-05 9:23 ` sharp c-3000 aka spitz: fix warn_on introduced in 2.6.32-rc1 Pavel Machek
2010-03-08 5:35 ` Eric Miao
2010-04-29 13:08 ` 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=bc64b4641001260323y496bf7cdv507085644fadb0fe@mail.gmail.com \
--to=dbaryshkov@gmail.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).