[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150122200252.GE18153@dtor-ws>
Date: Thu, 22 Jan 2015 12:02:52 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Henrik Rydberg <rydberg@...math.org>
Cc: Benjamin Tissoires <benjamin.tissoires@...hat.com>,
Peter Hutterer <peter.hutterer@...-t.net>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: MT - Add support for balanced slot assignment
On Thu, Jan 22, 2015 at 08:52:25PM +0100, Henrik Rydberg wrote:
> int input_mt_assign_slots(struct input_dev *dev, int *slots,
> - const struct input_mt_pos *pos, int num_pos)
> + const struct input_mt_pos *pos, int num_pos,
> + int dmax)
Should dmax be unsigned and do we really need to treat 0 specially or we
could use UNIT_MAX as "don't care" value?
> {
> struct input_mt *mt = dev->mt;
> + int mu = 2 * dmax * dmax;
For my education, what does "mu" stand for? Ideally, if someone could create a
write-up on the contact matching that would be most awesome.
Thanks.
--
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