- 05 Aug, 2006 5 commits
-
-
Rick Koch authored
Signed-off-by:
Rick Koch <n1gp@hotmail.com> Signed-off-by:
Dmitry Torokhov <dtor@mail.ru>
-
Shaun Jackman authored
- Use the touch status bit rather than the pressure bits to distinguish a BTN_TOUCH event. Non-pressure-sensitive touchscreens always report full pressure - Report ABS_PRESSURE information only if the touchscreen supports it Signed-off-by:
Shaun Jackman <sjackman@gmail.com> Signed-off-by:
-
Shaun Jackman authored
Fix 10-byte protocol checksum calculation and do not discard packet early unless it is missing lead in byte. Signed-off-by:
-
Dmitry Torokhov authored
Signed-off-by: -
Adrian Bunk authored
Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
-
- 19 Jul, 2006 17 commits
-
-
Anssi Hannula authored
Signed-off-by:
Anssi Hannula <anssi.hannula@gmail.com> Signed-off-by:
-
Anssi Hannula authored
Signed-off-by:
-
Anssi Hannula authored
Signed-off-by:
-
Anssi Hannula authored
The userspace interface of the force feedback part is changed and documentation in uinput.h is updated accordingly. MODULE_VERSION is also incremented to reflect the revision. Signed-off-by:
-
Anssi Hannula authored
Signed-off-by:
-
Anssi Hannula authored
This replaces the older PID driver which was never completed. Signed-off-by:
-
Anssi Hannula authored
Signed-off-by:
-
Anssi Hannula authored
Consolidate core implementing memoryless devices in one module; added support for gain and envelopes and periodic => rumble conversion. Signed-off-by:
-
Anssi Hannula authored
Implement a new force feedback interface, in which all non-driver-specific operations are separated to a common module. This includes handling effect type validations, locking, etc. The effects are now file descriptor specific instead of the previous strange half-process half-fd specific behaviour. The effect memory of devices is not emptied if the root user opens and closes the device while another user is using effects. This is a minor change and most likely no force feedback aware programs are affected by this negatively. Otherwise the userspace interface is left unaltered. Signed-off-by:
-
Anssi Hannula authored
Move fixp-arith.h from drivers/usb/input to drivers/input, as the part of force feedback support that requires trigonometric functions is being moved there. Signed-off-by:
-
Dmitry Torokhov authored
This will allow building input core module from several files which is needed for the reworked force feedback support. Signed-off-by: -
Randy Dunlap authored
Signed-off-by:
Randy Dunlap <rdunlap@xenotime.net> Signed-off-by:
-
Nick Martin authored
Although the Spaceball 4000FLX Lefty is already supported by the spaceball driver, it does not register properly due to SPACEBALL_MAX_ID being set too low. Increment SPACEBALL_MAX_ID such that the 4000FLX Lefty is properly recognized. Signed-off-by:
Nick Martin <nim+linux@nimlabs.org> Signed-off-by:
-
Dmitry Torokhov authored
Signed-off-by: -
Dmitry Torokhov authored
Signed-off-by: -
Dmitry Torokhov authored
Fixes Coverity #id 303 Signed-off-by: -
Dmitry Torokhov authored
The start() method need to be called every time we create a new handle. This includes not only registering new devices but also when registering new handlers. Signed-off-by:
-
- 15 Jul, 2006 3 commits
-
-
Dmitry Torokhov authored
Fixes Coverity #id 978 Signed-off-by: -
Andrew Morton authored
Signed-off-by:
-
Przemek Iskra authored
Signed-off-by:
Vojtech Pavlik <vojtech@suse.cz> Signed-off-by:
-
- 07 Jul, 2006 3 commits
-
-
Dmitry Torokhov authored
Fixes Coverity #id 864 Signed-off-by: -
Dmitry Torokhov authored
This is more user-friendly and also fixes Coverity #id 249 Signed-off-by: -
Dmitry Torokhov authored
Fixes Coverity #id 916 Signed-off-by:
-
- 06 Jul, 2006 4 commits
-
-
Andrew Morton authored
Signed-off-by:
-
Dmitry Torokhov authored
Create input_inject_event() function which is to be used by input handlers as opposed to input_event() which is reserved for drivers implementing input devices. The difference is that if device is "grabbed" by some process input_inject_event() will ignore events unless sent from the handle that is currently owns the device. Signed-off-by: -
Dmitry Torokhov authored
The new start() method is called immediately after connect() and also when "grabbed" device is released by its owner. This will allow input handlers to re-synchronize state of once-grabbed device with the rest of devices. Signed-off-by: -
Dmitry Torokhov authored
This method used to enforce exclusive access to iforce devices, but presenlty there are no known users of this method. Signed-off-by:
-
- 05 Jul, 2006 3 commits
-
-
Andreas Schwab authored
Fix a typo in the toplevel makefile. Signed-off-by:
Andreas Schwab <schwab@suse.de> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
David Woodhouse authored
asm-powerpc/cputime.h doesn't declare jiffies64_to_cputime64() or cputime64_sub(), and due to CONFIG_VIRT_CPU_ACCOUNTING it's not picking up the definition from asm-generic like x86-64 & friends do. Cc: Dave Jones <davej@redhat.com> Cc: Andrew Morton <akpm@osdl.org> Signed-off-by:
David Woodhouse <dwmw2@infradead.org> Signed-off-by:
-
Benjamin Herrenschmidt authored
With the new interrupt rework, an interrupt "host" map() callback can be called after the interrupt is already active. It's called again for an already mapped interrupt to allow changing the trigger setup, and currently this is not guarded with a test of wether the interrupt is requested or not. I plan to change some of this logic to be a bit less lenient against random reconfiguring of live interrupts but just not yet. The ported MPIC driver has a bug where when that happens, it will mask the interrupt. This changes it to preserve the previous masking of the interrupt instead. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
- 04 Jul, 2006 5 commits
-
-
Linus Torvalds authored
* master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq: Move workqueue exports to where the functions are defined. [CPUFREQ] Misc cleanups in ondemand. [CPUFREQ] Make ondemand sampling per CPU and remove the mutex usage in sampling path. [CPUFREQ] Add queue_delayed_work_on() interface for workqueues. [CPUFREQ] Remove slowdown from ondemand sampling path.
-
Linus Torvalds authored
No devfs_fs.h header any more.. Signed-off-by: -
git://git.infradead.org/hdrinstall-2.6Linus Torvalds authored
* git://git.infradead.org/hdrinstall-2.6: Remove export of include/linux/isdn/tpam.h Remove <linux/i2c-id.h> and <linux/i2c-algo-ite.h> from userspace export Restrict headers exported to userspace for SPARC and SPARC64 Add empty Kbuild files for 'make headers_install' in remaining arches. Add Kbuild file for Alpha 'make headers_install' Add Kbuild file for SPARC 'make headers_install' Add Kbuild file for IA64 'make headers_install' Add Kbuild file for S390 'make headers_install' Add Kbuild file for i386 'make headers_install' Add Kbuild file for x86_64 'make headers_install' Add Kbuild file for PowerPC 'make headers_install' Add generic Kbuild files for 'make headers_install' Basic implementation of 'make headers_check' Basic implementation of 'make headers_install'
-
Arjan van de Ven authored
There is a code sequence where the locking is substream->self_group.lock -> ins->scbs[index].lock substream->self_group.lock is interrupt safe, and taken from irq context as well (trace is snipped for brevity) so what can happen is cpu 0 cpu 1 user context user context take ins->scbs[index].lock without disabling interrupts get substream->self_group.lock (irqsafe) try to get ins->scbs[index].lock (spins) interrupt happens try to get substream->self_group.lock (spins) which is an obvious AB-BA deadlock fix is to just take the lock with _irqsafe Signed-off-by:
Arjan van de Ven <arjan@linux.intel.com> Cc: Jaroslav Kysela <perex@suse.cz> Acked-by:
Takashi Iwai <tiwai@suse.de> Signed-off-by:
-
Zach Brown authored
mthca: initialize send and receive queue locks separately lockdep identifies a lock by the call site of its initialization. By initializing the send and receive queue locks in mthca_wq_init() we confuse lockdep. It warns that that the ordered acquiry of both locks in mthca_modify_qp() is recursive acquiry of one lock: ============================================= [ INFO: possible recursive locking detected ] --------------------------------------------- modprobe/1192 is trying to acquire lock: (&wq->lock){....}, at: [<f892b4db>] mthca_modify_qp+0x60/0xa7b [ib_mthca] but task is already holding lock: (&wq->lock){....}, at: [<f892b4ce>] mthca_modify_qp+0x53/0xa7b [ib_mthca] Initializing the locks separately in mthca_alloc_qp_common() stops the warning and will let lockdep enforce proper ordering on paths that acquire both locks. Signed-off-by:Zach Brown <zach.brown@oracle.com> Cc: Roland Dreier <rolandd@cisco.com> Cc: Arjan van de Ven <arjan@linux.intel.com> Cc: Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
