Re: [PATCH 1/2] input: keypad: tc3589x: localize platform data

On Fri, 27 Mar 2015, Dmitry Torokhov wrote: On Thu, Mar 19, 2015 at 09:38:56AM -0700, Dmitry Torokhov wrote: Hi Linus, On Thu, Mar 19, 2015 at 03:52:44PM +0100, Linus Walleij wrote: This driver can only get its platform data from the device tree, and all platforms using it does

latest mouse quirks

Hi, please don't apply them. There's a typo in an ID. I'll resubmit. Regards Oliver -- To unsubscribe from this list: send the line unsubscribe linux-input in the body of a message to majord...@vger.kernel.org More majordomo info at

[PATCH v2 2/6] input/serio: drop pci_ids dependency

This driver does not use any PCI IDs, don't include the pci_ids.h header. Signed-off-by: Michael S. Tsirkin m...@redhat.com --- drivers/input/serio/gscps2.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/input/serio/gscps2.c b/drivers/input/serio/gscps2.c index 94ab494..ecba666

Re: [PATCH v2 1/2] HID: hid-sensor-hub: Enhance get feature report API

On Sat, 2015-03-28 at 21:58 +0100, Hartmut Knaack wrote: Srinivas Pandruvada schrieb am 17.01.2015 um 01:39: Some hid sensor feature report can contain more than one reports. This API can now support receiving multiple values from the feature report. Also update the parameters in the

[PATCH v2] Input - mt: Fix input_mt_get_slot_by_key

The case occurred recently with a touchscreen using twice a slot during a single EV_SYN event: E: 0.288415 # SYN_REPORT (0) -- E: 0.296207 0003 002f # EV_ABS / ABS_MT_SLOT 0 E: 0.296207 0003 0039 -001 # EV_ABS / ABS_MT_TRACKING_ID

[PATCH 0/3] Balanced slots, attempt #2

Hi, So, it occurs that the balanced slots assignment introduced in v4.0 had some troubles and the Synaptics part was reverted. I tried to spend some time today to figure out a solution, and the only way I can get something from it is to add a band aid in input_mt_set_slots(). It should not be

[PATCH 3/3] Input: synaptics - allocate 3 slots to keep stability in image sensors

When slowly dropping 1, 2 and then 3 fingers on an image sensor touchpad, we can see that the first finger gets reassigned a new slot while it did not move. This is due to the kernel tracking algorithm which can not assign correctly the 3 touches, being out of slots. Declaring that we support 3

[PATCH 1/3] Input: mt - prevent balanced slot assignment to assign twice the slot

If two touches are under the dmax distance, it looks like they can now be assigned to the same slot. Add a band aid to prevent such situation and be able to use the balanced slot assignment. Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com --- drivers/input/input-mt.c | 7 ++-

[PATCH 2/3] Revert Revert Input: synaptics - use dmax in input_mt_assign_slots

This reverts commit 09d042a2eb90 (Revert Input: synaptics - use dmax in input_mt_assign_slots) Now that balanced slots assignments seem to be fixed, let's reenable the use in synaptics.c and wait for users to complain if there are still problems. Signed-off-by: Benjamin Tissoires

[PATCH V2 2/3] Input: Add binding document for ADC keypad

Add a binding document for a generic ADC keypad. Buttons on an ADC keypad are connected in a resistor ladder to an ADC. The binding describes the mapping of ADC channel and voltage ranges to buttons. Note that this binding only describes simple ADC keypads where only a single button press can be

Re: [PATCH] Input: ALPS - fix max coordinates for v5 and v7 protocols

On Sat, 2015-03-21 at 20:36 -0700, Dmitry Torokhov wrote: Commit 3296f71cd2fde7a2ad52e66a27eae419f6328066 (Input: ALPS - consolidate setting protocol parameters) inadvertently moved call to alps_dolphin_get_device_area() from v5 to v7 protocol, causing both protocols report incorrect maximum