- Aug 07, 2014
-
-
Dmitry Torokhov authored
Prepare first round of input updates for 3.17.
-
Dmitry Torokhov authored
Merge large update to Wacom driver, converting it from USB to a HID driver and unifying wired and bluetooth support, from Benjamin Tissoires.
-
Benjamin Tissoires authored
Putting the various MODULE_* makes them appear several times in modinfo because wacom.h is used both in wacom_sys.c and wacom_wac.h. Having the macros near the module declaration makes them appear only once. Add also MODULE_VERSION(DRIVER_VERSION) to export the current version number. Signed-off-by:
Benjamin Tissoires <benjamin.tissoires@redhat.com> Signed-off-by:
Dmitry Torokhov <dmitry.torokhov@gmail.com>
-
Benjamin Tissoires authored
Bluetooth Wacom tablets are now handled by the regular wacom.ko driver. Remove the now useless hid-wacom driver. Signed-off-by:
Ping Cheng <pingc@wacom.com> Tested-by:
Przemo Firszt <przemo@firszt.eu> Signed-off-by:
-
Benjamin Tissoires authored
Reviewed-by:
-
Przemo Firszt authored
Every call of wacom_set_report was passing "id" as a separate parameter and buffer also passed the same information. We can use first u8 of the buffer instead of "id" Signed-off-by:
-
Benjamin Tissoires authored
Bluetooth Intuos 4 use 1-bit definition while the USB ones use a 4-bits definition. This changes the size of the raw image we receive, and thus the kernel will only accept 1-bit images for Bluetooth and 4-bits for USB. Signed-off-by:
-
Benjamin Tissoires authored
A good point of this change is that now, the Intuos4 bluetooth can handle the different tools (artpen, airbrush, mice), and we get a common interface between USB and BT for accessing the LEDs/OLEDs. Signed-off-by:
-
Benjamin Tissoires authored
First, merge the Graphire BT tablet. Signed-off-by:
-
Benjamin Tissoires authored
Now that wacom is a hid driver, there is no point in having a separate driver for bluetooth devices. This patch prepares the common paths of Bluetooth devices in the common wacom driver. It also adds the sysfs file "speed" used by Bluetooth devices. Signed-off-by:
-
Dexuan Cui authored
With this patch, we can press a key to wake up the VM after the VM executes "echo freeze > /sys/power/state". Signed-off-by:
Dexuan Cui <decui@microsoft.com> Signed-off-by:
K. Y. Srinivasan <kys@microsoft.com> Signed-off-by:
-
- Aug 01, 2014
-
-
Fabio Estevam authored
We can annotate the suspend/resume functions with '__maybe_unused' and get rid of the ifdef, which makes the code smaller and simpler. Signed-off-by:
Fabio Estevam <fabio.estevam@freescale.com> Signed-off-by:
-
Pramod Gurav authored
Signed-off-by:
Pramod Gurav <pramod.gurav@smartplayin.com> Signed-off-by:
-
Pramod Gurav authored
This switches the driver to using managed resources to simplify error handling and to do away with remove function. Signed-off-by:
-
- Jul 31, 2014
-
-
Hans de Goede authored
Add support for querying the physical size from the touchpad for Rushmore and v7 touchpads, and use that to tell userspace the device resolution. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Signed-off-by:
-
Fabio Estevam authored
We can annonate the suspend/resume functions with '__maybe_unused' and get rid of the ifdef, which makes the code smaller and simpler. Signed-off-by:
-
Fabio Estevam authored
When a kernel has CONFIG_PM=y and CONFIG_PM_SLEEP=n the following warnings are seen: drivers/input/touchscreen/mcs5000_ts.c:252:12: warning: 'mcs5000_ts_suspend' defined but not used [-Wunused-function] static int mcs5000_ts_suspend(struct device *dev) ^ drivers/input/touchscreen/mcs5000_ts.c:262:12: warning: 'mcs5000_ts_resume' defined but not used [-Wunused-function] static int mcs5000_ts_resume(struct device *dev) Protect the suspend/resume functions with CONFIG_PM_SLEEP in order to fix these build warnings. Signed-off-by: -
Pramod Gurav authored
Input device must be released(input_free_device) when ads7846_probe_dt fails. This fixes the same by releasing resources on failure. Signed-off-by:
-
- Jul 29, 2014
-
-
Jason Gerecke authored
Signed-off-by:
Jason Gerecke <killertofu@gmail.com> Signed-off-by:
-
Nick Dyer authored
By writing zero to both the active and idle cycle times the maXTouch device is put into a deep sleep mode when it consumes minimal power. It is unnecessary to change the configuration of any other objects (for example to disable T9 touchscreen). It is counterproductive to reset the chip on resume, it will result in a long delay. However it is necessary to issue a calibrate command after the chip has spent any time in deep sleep. This patch also deals with the situation where the power configuration is zero on probe, which would mean that the device never wakes up to execute commands. Signed-off-by:
Nick Dyer <nick.dyer@itdev.co.uk> Acked-by:
Benson Leung <bleung@chromium.org> Acked-by:
Yufeng Shen <miletus@chromium.org> Signed-off-by:
-
Roger Quadros authored
Update the bindings for touchscreen size. Signed-off-by:
Roger Quadros <rogerq@ti.com> Acked-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Roger Quadros authored
Update the bindings for touchscreen size. Signed-off-by:
-
Roger Quadros authored
Provide device tree support and binding information. Also provide support for a new chip "pixcir_tangoc". Signed-off-by:
-
Roger Quadros authored
Some variants of the Pixcir touch controller support up to 5 simultaneous fingers and hardware tracking IDs. Prepare the driver for that. Signed-off-by:
-
Roger Quadros authored
Switch to using the Type-B Multi-Touch protocol. Reviewed-by:
Henrik Rydberg <rydberg@euromail.se> Signed-off-by:
-
- Jul 27, 2014
-
-
Yunkang Tang authored
Such as found on the new Toshiba Portégé Z30-A and Z40-A. Signed-off-by:
Yunkang Tang <yunkang.tang@cn.alps.com> [hdegoede@redhat.com: Remove softbutton handling, this is done in userspace] [hdegoede@redhat.com: Report INPUT_PROP_BUTTONPAD] [hdegoede@redhat.com: Do not report fake PRESSURE, reporting BTN_TOUCH is enough] [hdegoede@redhat.com: Various cleanups / refactoring] Signed-off-by:
-
Hans de Goede authored
Signed-off-by:
-
Hans de Goede authored
So that decode functions can return a failure when appropriate. Signed-off-by:
-
Hans de Goede authored
If we detect more then 2 fingers report 2 touches, rather then only reporting the upper left corner of the bounding box. Signed-off-by:
-
Hans de Goede authored
Move all the semi-mt specific handling shared between the v3 and v4 handling code to a common helper function. Signed-off-by:
-
Hans de Goede authored
For v3 protocol devices, use the more accurate single touch data when the mt data contains only one finger. Note the mt data reporting a finger count of 1 should never happen, but better safe then sorry. This brings the v3 bitmap handling in line with what the v4 code does, allowing to factor out the common bits into a helper function. Signed-off-by:
-
Hans de Goede authored
When there are 2 fingers on the pad we don't know which one is which, so use input_mt_assign_slots to make sure the right set of coordinates ends up in the right slot. Besides ensuring things end up in the right slot, this also results in a nice cleanup, since sync_frame also handles non mt position and btn_touch reporting. Signed-off-by:
-
Hans de Goede authored
This is a preparation patch for switching the DIY mt handling to using input_mt_assign_slots && input_mt_sync_frame. struct alps_fields is quite large, so while making changes to almost all uses of it lets put it in our priv data instead of on the stack. Having it in our priv data also allows using it directly for storing values which need to be cached, rather then having separate x, y, z, fingers, etc. copies in our priv data. Signed-off-by:
-
Hans de Goede authored
This fixes 2 fingers at the same height or width on the touchpad getting reported at different y / x coordinates. Note num_bits is always at least 1. Signed-off-by:
-
Hans de Goede authored
alps_process_bitmap was resetting the point bit-count as soon as it saw 2 0 bits in a row. This means that unless the high point actually is at the end of the bitmap, it would always get its num_bits set to 0. Instead reset num_bits to 0 on a 0->1 transition, so that with > 2 fingers we only count the number of bits occupied by the highest finger. Signed-off-by:
-
Hans de Goede authored
Factor out the identical code for getting the bitmap points for x and y into a helper function. Signed-off-by:
-
Hans de Goede authored
Rushmore models don't have the Y-axis data in the bitmap inverted. Since we now have 2 different Y orientations, make the Y bitmap data processing use a forward loop like the X bitmap data processing, unifying the 2, and invert the data later, except on Rushmore. So far no-one has noticed this because the synaptics driver only uses the non mt coordinates (except on clickpads, and there are no alps clickpads using process_bitmap). Signed-off-by:
-
Hans de Goede authored
V3 models only report mt bitmap data when there are 2 or more fingers on the touchpad. So always generate 2 positions in alps_process_bitmap, and for v3 models only fall back to st data when there was no mt data in a mt packet (which should never happen). This fixes 2 finger scrolling not working when using 2 fingers close to each other. Signed-off-by:
-
Yunkang Tang authored
Signed-off-by:
-
- Jul 26, 2014
-
-
Pramod Gurav authored
Signed-off-by:
-
