1. 09 12月, 2006 4 次提交
  2. 08 12月, 2006 2 次提交
  3. 02 12月, 2006 12 次提交
  4. 26 11月, 2006 1 次提交
  5. 22 11月, 2006 1 次提交
  6. 17 11月, 2006 5 次提交
  7. 05 11月, 2006 1 次提交
    • A
      Input: HID - add a quirk for the Logitech USB Receiver · 41ad5fba
      Anssi Hannula 提交于
      Logitech USB Receiver (046d:c101) has two interfaces. The first one
      contains fields from HID_UP_KEYBOARD and HID_UP_LED, and the other one
      contains fields from HID_UP_CONSUMER and HID_UP_LOGIVENDOR. This device
      is used with multiple wireless Logitech products, including UltraX Media
      Remote.
      
      All fields on both interfaces are either keys or leds. All fields in the
      first interface are marked as Absolute, while the fields in the second
      interface are marked as Relative. Marking the keys as relative causes
      hidinput_hid_event() to send release events right after key press
      events.
      
      The device has EV_REP set, so the userspace expects the device to send
      repeat events if a key is held down. However, as hidinput_hid_event()
      sends release events immediately, repeat events are not sent at all. In
      fact, the userspace has no way of knowing if a key is being held down.
      
      Fix this by adding a quirk for 046d:c101 which changes relative keys to
      absolute ones.
      Signed-off-by: NAnssi Hannula <anssi.hannula@gmail.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      41ad5fba
  8. 04 11月, 2006 4 次提交
  9. 18 10月, 2006 8 次提交
  10. 05 10月, 2006 2 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
    • M
      [PATCH] itmtouch: fix inverted flag to indicate touch location correctly, correct white space · 77dc2db6
      Mark Assad 提交于
      There is a bug in the current version of the itmtouch USB touchscreen
      driver.  The if statment that checks if pressure is being applied to the
      touch screen is now missing a ! (not), so events are no longer being
      reported correctly.
      
      The original source code for this line was as follows:
      
      	#define UCP(x) ((unsigned char*)(x))
      	#define UCOM(x,y,z) ((UCP((x)->transfer_buffer)[y]) & (z))
      
      	...
      	if (!UCOM(urb, 7, 0x20)) {
      
      And was cleaned to:
      
      	unsigned char *data = urb->transfer_buffer;
      	....
      	 if (data[7] & 0x20) {
      
      (note the lack of '!')
      
      This has been tested on an LG L1510BF and an LG1510SF touch screen.
      Signed-off-by: NMark Assad <massad@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      77dc2db6