From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Henrik Rydberg <rydberg@euromail.se>,
Chris Bagwell <chris@cnpbagwell.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
Nikolai Kondrashov <spbnick@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation: Add evdev type and code definitions
Date: Fri, 7 Jan 2011 13:53:53 -0800 [thread overview]
Message-ID: <20110107215353.GF28875@core.coreip.homeip.net> (raw)
In-Reply-To: <1294435695-16750-1-git-send-email-chase.douglas@canonical.com>
Hi Chase,
On Fri, Jan 07, 2011 at 04:28:15PM -0500, Chase Douglas wrote:
> +
> +* KEY_SUSPEND, KEY_POWER:
> + - These codes are reserved for the EV_PWR type.
> +
This is not correct, KEY_SUSPEND and KEY_POWER are valid events for
EV_KEY type. We need to figure out what to do with drivers who like to do
EV_PWR/KEY_PWR though.
The whole EV_PWR business is iffy. IIRC/IIUC it was envisioned to semd
powwer events _to_ the devices to implement device-level PM. We'll have
to revisit it at some point.
> +EV_REL:
> +----------
> +EV_REL events describe relative changes in a property. For example, a mouse may
> +move to the left by a certain number of units, but its absolute position in
> +space is unknown. If the absolute position is known, EV_ABS codes should be used
> +instead of EV_REL codes.
> +
> +A few EV_REL codes have special meanings:
> +
> +* REL_WHEEL, REL_HWHEEL:
> + - These codes are used for vertical and horizontal scroll wheels,
> + respectively.
> +
> +EV_ABS:
> +----------
> +EV_ABS events describe absolute changes in a property. For example, a touchpad
> +may emit coordinates for a touch location.
> +
> +A few EV_ABS codes have special meanings:
> +
> +* ABS_DISTANCE:
> + - Used to describe the distance of a tool from an interaction surface. This
> + should only be used while the tool is hovering, meaning in close proximity
> + of the device. If the input device may be used freely in three dimensions,
> + consider ABS_Z instead.
> +
> +* ABS_MT_<name>:
> + - Used to describe multitouch input events. Please see
> + multi-touch-protocol.txt for details.
> +
> +EV_SW:
> +----------
> +EV_SW events describe stateful binary switches. For example, the SW_LID code is
> +used to denote when a laptop lid is closed.
Please add that drivers should refresh switch state upon binding to a
device and also upon resume.
> +
> +EV_MSC:
> +----------
> +EV_MSC events are used for input and output events that do not fall under other
> +categories.
> +
> +EV_LED:
> +----------
> +EV_LED events are used for input and output to set and query the state of
> +various LEDs on devices.
> +
> +EV_REP:
> +----------
> +EV_REP events are used for specifying autorepeating events.
> +
> +EV_SND:
> +----------
> +EV_SND events are used for sending sound commands to simple sound output
> +devices.
> +
> +EV_FF:
> +----------
> +EV_FF events are used to initialize a force feedback capable device and to cause
> +such device to feedback.
> +
> +EV_PWR:
> +----------
> +EV_PWR events are a special type of key event used specifically for monitoring
> +power buttons and switches. The two codes in use are:
> +
> +* KEY_POWER:
> + - Used to denote a power button event.
> +
> +* KEY_SUSPEND:
> + - Used to denote a suspend button event.
Just replace this with TBA for now.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-01-07 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 21:28 [PATCH v2] Documentation: Add evdev type and code definitions Chase Douglas
2011-01-07 21:53 ` Dmitry Torokhov [this message]
2011-01-07 22:03 ` Chase Douglas
2011-01-07 22:42 ` Dmitry Torokhov
2011-01-07 22:06 ` Nikolai Kondrashov
2011-01-07 22:15 ` Chase Douglas
2011-01-07 22:26 ` Nikolai Kondrashov
2011-01-07 22:36 ` Chase Douglas
2011-01-08 1:15 ` Chris Bagwell
2011-01-09 14:51 ` Henrik Rydberg
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=20110107215353.GF28875@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@euromail.se \
--cc=spbnick@gmail.com \
/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).