[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc64b4641001260323y496bf7cdv507085644fadb0fe@mail.gmail.com>
Date: Tue, 26 Jan 2010 14:23:56 +0300
From: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
To: Stanislav Brabec <utx@...guin.cz>
Cc: Eric Miao <eric.y.miao@...il.com>, Andrew Morton <akpm@...l.org>,
thommycheck <thommycheck@...il.com>, dtor <dtor@...l.ru>,
arminlitzel <arminlitzel@....de>,
linux-input <linux-input@...r.kernel.org>,
kernel list <linux-kernel@...r.kernel.org>,
Dirk <Dirk@...er-online.de>, "Rafael J. Wysocki" <rjw@...k.pl>,
lenz <lenz@...wisc.edu>, rpurdie <rpurdie@...ys.net>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Pavel Machek <pavel@....cz>, Cyril Hrubis <metan@....cz>,
zaurus-devel <zaurus-devel@...ts.linuxtogo.org>,
omegamoon <omegamoon@...il.com>, Vojtech Pavlik <vojtech@...e.cz>
Subject: Re: 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)
Hello,
2010/1/26 Stanislav Brabec <utx@...guin.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists