From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] input: mt: introduce MT event slots
Date: Thu, 15 Apr 2010 16:25:25 -0700 [thread overview]
Message-ID: <20100415232523.GA18263@core.coreip.homeip.net> (raw)
In-Reply-To: <1270685590-2204-1-git-send-email-rydberg@euromail.se>
Hi Henrik,
On Thu, Apr 08, 2010 at 02:13:10AM +0200, Henrik Rydberg wrote:
> With the rapidly increasing number of intelligent multi-contact and
> multi-user devices, the need to send digested, filtered information
> from a set of different sources within the same device is imminent.
> This patch adds the concept of slots to the MT protocol. The slots
> enumerate a set of identified sources, such that all MT events
> can be passed independently and selectively per identified source.
>
> The protocol works like this: Instead of sending a SYN_MT_REPORT
> event immediately after the contact data, one sends a SYN_MT_SLOT
> event immediately before the contact data. The input core will only
> emit events for the slots corresponding to the contacts that have
> changed. It is assumed that the same slot is used for the duration
> of an initiated contact.
>
I see the reason for doing this however I would like to hold off
applying it till we get a couple of users and prove that the scheme
works well for them.
> Signed-off-by: Henrik Rydberg <rydberg@euromail.se>
> ---
> drivers/input/input.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/input.h | 26 ++++++++++++++++++++
> 2 files changed, 88 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/input/input.c b/drivers/input/input.c
> index afd4e2b..217e976 100644
> --- a/drivers/input/input.c
> +++ b/drivers/input/input.c
> @@ -181,6 +181,22 @@ static void input_stop_autorepeat(struct input_dev *dev)
> #define INPUT_PASS_TO_DEVICE 2
> #define INPUT_PASS_TO_ALL (INPUT_PASS_TO_HANDLERS | INPUT_PASS_TO_DEVICE)
>
> +static void input_handle_mt_event(struct input_dev *dev,
> + unsigned int code, int value)
> +{
> + int oldval = dev->mt[dev->slot].abs[code];
A temp for dev->mt[dev->slot] might be nice.
>
> +/**
> + * struct input_mt_slot - represents the state of an MT input slot
> + * @abs: current values from absolute axes for this slot
> + */
> +struct input_mt_slot {
> + int abs[ABS_MAX + 1];
> +};
It would be nice to use abs[ABS_MT_MAX - ABS_MT_TOUCH_MAJOR] to save
some memory.
--
Dmitry
next prev parent reply other threads:[~2010-04-15 23:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 0:13 [PATCH] input: mt: introduce MT event slots Henrik Rydberg
2010-04-08 3:07 ` Michael Poole
2010-04-08 9:43 ` Henrik Rydberg
2010-04-08 11:40 ` Michael Poole
2010-04-08 13:01 ` Henrik Rydberg
2010-04-16 7:40 ` Hennerich, Michael
2010-04-16 14:29 ` Henrik Rydberg
2010-04-08 19:15 ` Rafi Rubin
2010-04-08 20:25 ` Henrik Rydberg
2010-04-08 21:23 ` Rafi Rubin
2010-04-08 22:12 ` Henrik Rydberg
2010-04-15 23:25 ` Dmitry Torokhov [this message]
2010-04-16 15:09 ` Henrik Rydberg
2010-05-04 7:57 ` Henrik Rydberg
2010-05-04 17:29 ` Dmitry Torokhov
2010-05-04 21:41 ` 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=20100415232523.GA18263@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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).