Peter,
It may be a long time ago now, but we had very vocal discussions regarding the
MT protocol back then, and I am quite sure all the subtleties are well
understood. In order to fully appreciate the simplicity of the protocol, one
only needs to stop misintepreting it. In order to do that,
I see that I did not change that here.
Width can be in state-width or fingers[finger]-width
I think latter is mere correct.It should be that way in this patch.
I moved ot back and forth and tested. Noticed no difference.
24.04.2015 13:44, Dmitry Tunin пишет:
Hi,
Some comments below. If it
Hi,
Some comments below. If it is not a problem that width values are
outdated as soon as there are two or more fingers on the touchpad, I
think the change is good.
Regards,
Mathias
Am 24.04.2015 um 01:15 schrieb Dmitry Tunin:
Focaltech touchpads report finger width in packet[5]
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin hanipouspi...@gmail.com
---
Hi,
Some comments below. If it is not a problem that width values are
outdated as soon as there are two or more fingers on the touchpad, I
think the change is good.
Regards,
Mathias
Am 24.04.2015 um 01:15 schrieb Dmitry Tunin:
Focaltech touchpads report finger width in packet[5] of absolute
Hi!
I did not yet figure out how to get sensor data from the controller,
but it works rather well as a RGB led.
Hi Pavel,
From what I've read, the motion controller only sends sensor data when
connected via bluetooth.
Otherwise it should be in report 1 with the buttons and other data.
On 17 April 2015 17:16 Dmitry Torokhov wrote
On Fri, Apr 17, 2015 at 01:03:20PM +0100, S Twiss wrote:
From: Steve Twiss stwiss.opensou...@diasemi.com
Add OnKey driver support for DA9063
Isn't this almost to the letter identical to da9062 that I just looked
at? Please find a way to
On 18 April 2015 08:55 Paul Bolle wrote:
There's still a license mismatch left (it probably got lost in the noise
when I finally noticed that the header comment mentioned the LGPL in
V1).
On Fri, 2015-04-17 at 13:03 +0100, S Twiss wrote:
+ * as published by the Free Software Foundation;
Hi!
If you can send a version without all of the unrelated underscore changes
I'll help clean it up. I don't own one of these controllers
though, so I can't help test the functionality.
I cleaned some of the (easy) comments, and tested that it still
works. Here's the updated version. Thanks,
Fix spelling of magnitude
s/manginude/magnitude
Signed-off-by: Dan Murphy dmur...@ti.com
---
drivers/input/ff-core.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/input/ff-core.c b/drivers/input/ff-core.c
index b81c88c..d10154e 100644
--- a/drivers/input/ff-core.c
Fix the Kconfig for the drv2667 as there was a copy/paste
error.
Signed-off-by: Dan Murphy dmur...@ti.com
---
drivers/input/misc/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig
index 4436ab1..7838f1a 100644
---
Pinnacle / Rushmore packets contain either position info, or bitmap info,
never both. So far we've in essence been storing garbage in the position /
bitmap fields of the fields struct when decoding a bitmap / pos packet.
We've been relying on the following sequence to get away with this:
1)
Hi Dmitry,
This patch-set improves the coordinates reported when 2 fingers are down
on semi-mt alps models, leading to a much smoother 2fg scrolling experience.
This is somewhat the result of a libinput discussion here:
https://bugs.freedesktop.org/show_bug.cgi?id=89683
This has been tested on
Now that the generic process_bitmap function has been improved to offer
accurate coordinates for the first touch we can use it for v5 (dolphin)
touchpads too.
Besides being a nice code cleanup this also fixes the saw tooth pattern
in the coordinates for the second touch the dolphin specific
Rename alps_set_abs_params_mt to alps_set_abs_params_semi_mt,
to make it clear that it is only (to be) used for semi-mt devices.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/input/mouse/alps.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
HID generic devices share the same default name, Wacom HID. This
causes userland programs to show same device names for different
devices, which would confuse end users with same device names for
different devices too.
This patch uses name retrieved from HID descriptor, if a meaningful
name is
Hi Dmitry,
[ adding more relevant people to the discussion ]
On Apr 23 2015 or thereabouts, Benjamin Tissoires wrote:
On Apr 23 2015 or thereabouts, Dmitry Torokhov wrote:
On Wed, Apr 22, 2015 at 11:45:09AM -0400, Benjamin Tissoires wrote:
Synaptics PS/2 touchpad can send only 2 touches in
On Fri, Apr 24, 2015 at 02:47:06PM +, Opensource [Steve Twiss] wrote:
On 18 April 2015 12:48 Mark Brown wrote:
Okay. I think I am getting this.
As of v3.18 there are newer parts to regulator_desc from the commit
a0c7b16 regulator: of: Provide simplified DT parsing method
The search
On 18 April 2015 12:48 Mark Brown wrote:
On Fri, Apr 17, 2015 at 03:23:32PM +0100, S Twiss wrote:
+/* Regulator interrupt handlers */
+static irqreturn_t da9062_ldo_lim_event(int irq, void *data)
+{
+ struct da9062_regulators *regulators = data;
+ struct da9062 *hw =
On 17 April 2015 15:24 Steve Twiss wrote.
Subject: [PATCH V1 1/6] mfd: da9062: DA9062 MFD core driver
From: S Twiss stwiss.opensou...@diasemi.com
Add MFD core driver support for DA9062
Signed-off-by: Steve Twiss stwiss.opensou...@diasemi.com
---
This patch applies against linux-next
Change alps_decode_rushmore to do all decoding itself, rather then relying
on alps_decode_pinnacle and then overriding some fields + or-ing in some
bits.
This is a preparation patch for modifying the decode functions to properly
differentiate between position and bitmap packets.
Signed-off-by:
All alps semi-mt touchpads give us the following data when 2 (or more)
fingers are touching: 1 more or less accurate touch for the first finger
down, and a bitmap with columns and rows in which 1 or more fingers are
seen resulting in a crude (low res) bounding box.
So far for v3, rushmore and v4
With the recent process_bitmap() changes all semi-mt devices always report
the first finger down in slot 0, so stop using input-mt finger tracking
for these.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/input/mouse/alps.c | 8 ++--
1 file changed, 6 insertions(+), 2
This way we can use the more accurate position info in process_bitmap() to
get better results.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/input/mouse/alps.c | 35 ++-
1 file changed, 14 insertions(+), 21 deletions(-)
diff --git
On Fri, 2015-04-24 at 13:45 +, Opensource [Steve Twiss] wrote:
That seems to be a fairly common mistake in the kernel.
It's an easy mistake to make. And as long as people pick an ident that
passes license_is_gpl_compatible() the module will build and load just
fine.
When I did a
25 matches
Mail list logo
