- 24 Mar, 2011 3 commits
-
-
Aaro Koskinen authored
Commit 0b950d3d (Input: tsc2005 - add open/close) introduced a locking issue with the ESD watchdog: __tsc2005_disable() is calling cancel_delayed_work_sync() with mutex held, and the work also needs the same mutex. Fix the problem by using mutex_trylock() in tsc2005_esd_work(). If the mutex is taken, we know we are in the middle of disable or enable and the watchdog check can be skipped. Signed-off-by:
Aaro Koskinen <aaro.koskinen@nokia.com> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Aaro Koskinen authored
Use relative jiffies to schedule the watchdog. Otherwise it will run like a mad one. Signed-off-by:
-
Geert Uytterhoeven authored
drivers/input/touchscreen/tsc2005.c: In function ‘tsc2005_probe’: drivers/input/touchscreen/tsc2005.c:666: error: implicit declaration of function ‘set_irq_wake’ In addition, migrate from set_irq_wake() (marked "do not use" as of commit a0cd9ca2 ("genirq: Namespace cleanup")) to irq_set_irq_wake(). Signed-off-by:
Geert Uytterhoeven <geert@linux-m68k.org> Signed-off-by:
-
- 19 Mar, 2011 1 commit
-
-
Dmitry Torokhov authored
-
- 17 Mar, 2011 22 commits
-
-
Dmitry Torokhov authored
-
Dmitry Torokhov authored
I believe that enable/disable functionality should not be implemented on the individual driver level but rather in device core, potentially reusing parts of PM framework. Therefore the driver-specific "disable" attribute is removed from the mainline driver. Tested-by:
-
Dmitry Torokhov authored
Introduce open and close methods for the input device to keep the device powered down when it is not in use. Also rework interaction between interrupt thread and starting/shutting off/resetting the device: instead of taking a mutex in the intterrupt thread and elsewhere disable interrupts before transitioning the device in a new state. The ESD handling is also separated from the IRQ thread; we poll regularly at a given interval and simply skip reads if we see that valid interrupt happened not so long ago. This allows us not cancel and reschedule ESD work from interrupt context all the time. Tested-by:
-
Dmitry Torokhov authored
Tested-by:
-
Dmitry Torokhov authored
We will most likely rearm it yet again the IRQ thread so doing it here is pointless. Tested-by:
-
Dmitry Torokhov authored
We do not need process context to send input events so let's switch to a regular timer. I am going to get rid of taking ts->mutex in tsc2005_irq_thread() later. Tested-by:
-
Dmitry Torokhov authored
Sparse in unhappy when people use 0 instead of NULL for pointers so let's rework the way we initialize spi_transfer structure in tsc2005_cmd() and tsc2005_write(). Tested-by:
-
Dmitry Torokhov authored
Tested-by:
-
Dmitry Torokhov authored
If implementation to perform self-test/reset has not been provided by the platform code hide 'selftest' sysfs attribute instead of returning error when someone tries to use it. Tested-by:
-
Dmitry Torokhov authored
We need to make sure we have time/work initialized before requesting and enabling interrupts, otherwise we might start using them way too early. Tested-by:
-
Dmitry Torokhov authored
We know what bus we are residing on (SPI) so let's make this data available to the users. Tested-by:
-
Dmitry Torokhov authored
Set up SPI device as parent of the input device so it gets placed into proper place in sysfs tree. Tested-by:
-
Dmitry Torokhov authored
We should not leave garbage pointers in driver structure after we unbind it from the device or if bind fails. Tested-by:
-
Dmitry Torokhov authored
Add proper module description so that it would show in 'modinfo' output. Tested-by:
-
Dmitry Torokhov authored
The boot process is noisy as it is and input core already announces all new device so let's get rid of the banner message in the driver. Tested-by:
-
Dmitry Torokhov authored
TSC2005 is not a platform driver so it should not define "platform:tsc2005" module alias. Tested-by:
-
Dmitry Torokhov authored
Newer code should not be using legacy suspend/resume methods but rather supply dev_pm_ops structure as it allows better control over power management. Tested-by:
-
Dmitry Torokhov authored
Instead of peeking into underlying device and using dev_get/set_drvdata(), let's use SPI layer's implementation to access driver-private data (which may be different from driver-core private data). Tested-by:
-
Lauri Leukkunen authored
Discussions: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg26748.html Introduce a driver for the Texas Instruments TSC2005 touchscreen controller (http://focus.ti.com/docs/prod/folders/print/tsc2005.html). The patch is based on a driver by Lauri Leukkunen, with modifications by David Brownell, Phil Carmody, Imre Deak, Hiroshi DOYU, Ari Kauppi, Tony Lindgren, Jarkko Nikula, Eero Nurkkala and Roman Tereshonkov. Signed-off-by:
Lauri Leukkunen <lauri.leukkunen@nokia.com> [aaro.koskinen@nokia.com: patch description, rebasing & cleanup] Signed-off-by:
Srikar <ext-srikar.1.bhavanarayana@nokia.com> Signed-off-by:
-
Dmitry Torokhov authored
drivers/input is reserved for input core code and input handlers with drivers belonging to one of the sub-directories. Signed-off-by: -
Daniel De Graaf authored
Without a grant reference, full access to the domain's memory is required to use the shared page. Add an additional parameter in xenstore to allow grant mapping to be used. Signed-off-by:
Daniel De Graaf <dgdegra@tycho.nsa.gov> Signed-off-by:
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Acked-by:
Ian Campbell <Ian.Campbell@eu.citrix.com> Signed-off-by:
-
Olaf Hering authored
A virtualized display device is usually viewed with the vncviewer application, either by 'xm vnc domU' or with vncviewer localhost:port. vncviewer and the RFB protocol provides absolute coordinates to the virtual display. These coordinates are either passed through to a PV guest or converted to relative coordinates for a HVM guest. A PV guest receives these coordinates and passes them to the kernels evdev driver. There it can be picked up by applications such as the xorg-input drivers. Using absolute coordinates avoids issues such as guest mouse pointer not tracking host mouse pointer due to wrong mouse acceleration settings in the guests X display. Advertise either absolute or relative coordinates to the input system and the evdev driver, depending on what dom0 provides. The xorg-input driver prefers relative coordinates even if a devices provides both. Signed-off-by:
Olaf Hering <olaf@aepfle.de> Signed-off-by:
Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by:
-
- 16 Mar, 2011 2 commits
-
-
Dmitry Torokhov authored
Also rearrange driver structure initializer a bit. Signed-off-by: -
Magnus Damm authored
Extend the tca6416 driver to use enable_irq_wake() and disable_irq_wake() in the suspend/resume hooks. This makes it possible to wake up from suspend-to-ram using a tca6416 key on the sh7372 mackerel board. Signed-off-by:
Magnus Damm <damm@opensource.se> Signed-off-by:
-
- 15 Mar, 2011 3 commits
-
-
Joonyoung Shim authored
Atmel mXT1386 chip is operated by atmel_mxt_ts driver and it has some different objects. Signed-off-by:
Joonyoung Shim <jy0922.shim@samsung.com> Signed-off-by:
-
Joonyoung Shim authored
Atmel touchscreen chips have different firmware version with each chip, so we cannot distinguish attribute of chip by firmware version. Signed-off-by:
-
Mark Brown authored
Explicitly set all the enable bits when opening the device just in case something left the device in an unexpected state. Signed-off-by:
Mark Brown <broonie@opensource.wolfsonmicro.com> Signed-off-by:
-
- 14 Mar, 2011 1 commit
-
-
Bo Shen authored
The AT42QT1070 QTouch sensor supports up to 7 keys. The driver has been tested on Atmel AT91SAM9M10-G45-EK board, and it should work fine on other platforms. Signed-off-by:
Bo Shen <voice.shen@atmel.com> Signed-off-by:
-
- 13 Mar, 2011 6 commits
-
-
Mark Brown authored
tslib expects pressure measurements so enable them by default for better compatibility. Signed-off-by:
-
Andy Botting authored
This patch add multitouch support for the MacBookPro8,1 and MacBookPro8,2 models. Cc: stable@kernel.org Signed-off-by:
Andy Botting <andy@andybotting.com> Signed-off-by:
Henrik Rydberg <rydberg@euromail.se> Acked-by:
Jiri Kosina <jkosina@suse.cz> Signed-off-by:
-
Ping Cheng authored
Reviewed-by:
Chris Bagwell <chris@cnpbagwell.com> Signed-off-by:
Ping Cheng <pingc@wacom.com> Signed-off-by:
-
Ping Cheng authored
There are two types of 1FGT devices supported in wacom_wac.c. Changing them to follow the existing touchscreen format, i.e., only report BTN_TOUCH as a valid tool type. Touch data will be ignored if pen is in proximity. This requires a touch up event sent if touch was down when pen comes in. The touch up event should be sent before any pen events are emitted. Otherwise, two pointers would race for the cursor. However, we can not send a touch up inside wacom_tpc_pen since pen and touch are on different logical port. That is why we have to check if touch is up before sending pen events. Reviewed-by:
-
Ping Cheng authored
So it would be easier for patch reviewers to follow the data path. Reviewed-by:
-
Ping Cheng authored
2FGT Tablet PC touch events were processed in _TAP_ format. Remove them so we can change to _MT_ format. Signed-off-by:
-
- 27 Feb, 2011 2 commits
-
-
Peter Korsgaard authored
As was recently brought up on the busybox list (http://lists.busybox.net/pipermail/busybox/2011-January/074565.html), evdev_write doesn't properly check the count argument, which will lead to a return value > count on partial writes if the remaining bytes are accessible - causing userspace confusion. Fix it by only handling each full input_event structure and return -EINVAL if less than 1 struct was written, similar to how it is done in evdev_read. Reported-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk> Acked-by:
-
Henrik Rydberg authored
With the current code, pressing the integrated button with an isolating tool does not result in any button report. Fixed with this this patch. Signed-off-by:
-
