1. 26 Nov, 2009 1 commit
  2. 21 Apr, 2009 1 commit
  3. 09 Oct, 2008 1 commit
  4. 13 Jun, 2008 1 commit
  5. 16 May, 2008 1 commit
  6. 30 Apr, 2008 2 commits
  7. 24 Apr, 2008 1 commit
  8. 20 Apr, 2008 1 commit
  9. 15 Apr, 2008 1 commit
  10. 21 Jan, 2008 2 commits
  11. 19 Oct, 2007 2 commits
    • Jiri Slaby's avatar
      get rid of input BIT* duplicate defines · 7b19ada2
      Jiri Slaby authored
      
      
      get rid of input BIT* duplicate defines
      
      use newly global defined macros for input layer. Also remove includes of
      input.h from non-input sources only for BIT macro definiton. Define the
      macro temporarily in local manner, all those local definitons will be
      removed further in this patchset (to not break bisecting).
      BIT macro will be globally defined (1<<x)
      Signed-off-by: Jiri Slaby's avatarJiri Slaby <jirislaby@gmail.com>
      Cc: <dtor@mail.ru>
      Acked-by: default avatarJiri Kosina <jkosina@suse.cz>
      Cc: <lenb@kernel.org>
      Acked-by: Marcel Holtmann's avatarMarcel Holtmann <marcel@holtmann.org>
      Cc: <perex@suse.cz>
      Acked-by: Mauro Chehab's avatarMauro Carvalho Chehab <mchehab@infradead.org>
      Cc: <vernux@us.ibm.com>
      Cc: <malattia@linux.it>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      7b19ada2
    • Samuel Thibault's avatar
      Console keyboard events and accessibility · 41ab4396
      Samuel Thibault authored
      
      
      Some blind people use a kernel engine called Speakup which uses hardware
      synthesis to speak what gets displayed on the screen.  They use the
      PC keyboard to control this engine (start/stop, accelerate, ...) and
      also need to get keyboard feedback (to make sure to know what they are
      typing, the caps lock status, etc.)
      
      Up to now, the way it was done was very ugly.  Below is a patch to add a
      notifier list for permitting a far better implementation, see ChangeLog
      above for details.
      
      You may wonder why this can't be done at the input layer.  The problem
      is that what people want to monitor is the console keyboard, i.e. all
      input keyboards that got attached to the console, and with the currently
      active keymap (i.e. keysyms, not only keycodes).
      
      This adds a keyboard notifier that such modules can use to get the keyboard
      events and possibly eat them, at several stages:
      
      - keycodes: even before translation into keysym.
      - unbound keycodes: when no keysym is bound.
      - unicode: when the keycode would get translated into a unicode character.
      - keysym: when the keycode would get translated into a keysym.
      - post_keysym: after the keysym got interpreted, so as to see the result
        (caps lock, etc.)
      
      This also provides access to k_handler so as to permit simulation of
      keypresses.
      
      [akpm@linux-foundation.org: various fixes]
      Signed-off-by: Samuel Thibault's avatarSamuel Thibault <samuel.thibault@ens-lyon.org>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      41ab4396
  12. 17 Oct, 2007 2 commits
  13. 23 Aug, 2007 1 commit
  14. 16 Jul, 2007 1 commit
  15. 10 Jul, 2007 1 commit
  16. 08 May, 2007 1 commit
  17. 12 Apr, 2007 2 commits
  18. 15 Mar, 2007 1 commit
  19. 14 Feb, 2007 1 commit
    • Eric W. Biederman's avatar
      [PATCH] Fix SAK_work workqueue initialization. · 7f1f86a0
      Eric W. Biederman authored
      
      
      Somewhere in the rewrite of the work queues my cleanup of SAK handling
      got broken.  Maybe I didn't retest it properly or possibly the API
      was changing so fast I missed something.  Regardless currently
      triggering a SAK now generates an ugly BUG_ON and kills the kernel.
      
      Thanks to Alexey Dobriyan <adobriyan@openvz.org> for spotting this.
      
      This modifies the use of SAK_work to initialize it when the data
      structure it resides in is initialized, and to simply call
      schedule_work when we need to generate a SAK.  I update both
      data structures that have a SAK_work member for consistency.
      
      All of the old PREPARE_WORK calls that are now gone.
      
      If we call schedule_work again before it has processed it
      has generated the first SAK it will simply ignore the duplicate
      schedule_work request.
      Signed-off-by: default avatarEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      7f1f86a0
  20. 11 Feb, 2007 1 commit
    • Eric W. Biederman's avatar
      [PATCH] vt: refactor console SAK processing · 8b6312f4
      Eric W. Biederman authored
      
      
      This does several things.
      - It moves looking up of the current foreground console into process
        context where we can safely take the semaphore that protects this
        operation.
      - It uses the new flavor of work queue processing.
      - This generates a factor of do_SAK, __do_SAK that runs immediately.
      - This calls __do_SAK with the console semaphore held ensuring nothing
        else happens to the console while we process the SAK operation.
      - With the console SAK processing moved into process context this
        patch removes the xchg operations that I used to attempt to attomically
        update struct pid, because of the strange locking used in the SAK processing.
        With SAK using the normal console semaphore nothing special is needed.
      
      Cc: Oleg Nesterov <oleg@tv-sign.ru>
      Signed-off-by: default avatarEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      8b6312f4
  21. 05 Nov, 2006 1 commit
  22. 05 Oct, 2006 1 commit
    • David Howells's avatar
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells authored
      
      
      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: default avatarDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  23. 02 Oct, 2006 1 commit
  24. 14 Sep, 2006 2 commits
  25. 05 Aug, 2006 1 commit
  26. 19 Jul, 2006 2 commits
  27. 06 Jul, 2006 2 commits
  28. 30 Jun, 2006 1 commit
  29. 26 Jun, 2006 3 commits
  30. 25 Jun, 2006 1 commit