1. 08 5月, 2007 1 次提交
  2. 28 4月, 2007 1 次提交
  3. 25 4月, 2007 2 次提交
  4. 12 4月, 2007 1 次提交
  5. 16 3月, 2007 2 次提交
    • D
      Input: i8042 - add HP Pavilion DV4017EA to the MUX blacklist · 6e782584
      Dmitry Torokhov 提交于
      This should get rid of "atkbd.c: Suprious NAK on isa0060/serio0"
      messages caused by broken MUX implementation. The box does not
      have external PS/2 ports so disabling MUX mode is safe.
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      6e782584
    • H
      Input: HIL - fix rwlock recursion bug · 9575499d
      Helge Deller 提交于
      The following bug happens when insmoding hp_sdc_mlc.ko:
      
          HP SDC MLC: Registering the System Domain Controller's HIL MLC.
          BUG: rwlock recursion on CPU#0, hotplug/1814, 00854734
          Backtrace:
           [<10267560>] _raw_write_lock+0x50/0x88
           [<10104008>] _write_lock_irqsave+0x14/0x24
           [<008537d4>] hp_sdc_mlc_out+0x38/0x25c [hp_sdc_mlc]
           [<0084ebd8>] hilse_donode+0x308/0x470 [hil_mlc]
           [<0084ed80>] hil_mlcs_process+0x40/0x6c [hil_mlc]
           [<10130f80>] tasklet_action+0x78/0xb8
           [<10130cec>] __do_softirq+0x60/0xcc
           [<1010428c>] __lock_text_end+0x38/0x48
           [<10108348>] do_cpu_irq_mask+0xf0/0x11c
           [<1010b068>] intr_return+0x0/0xc
      Signed-off-by: NHelge Deller <deller@gmx.de>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      9575499d
  6. 08 3月, 2007 1 次提交
  7. 01 3月, 2007 2 次提交
  8. 18 2月, 2007 3 次提交
  9. 15 2月, 2007 1 次提交
    • T
      [PATCH] remove many unneeded #includes of sched.h · cd354f1a
      Tim Schmielau 提交于
      After Al Viro (finally) succeeded in removing the sched.h #include in module.h
      recently, it makes sense again to remove other superfluous sched.h includes.
      There are quite a lot of files which include it but don't actually need
      anything defined in there.  Presumably these includes were once needed for
      macros that used to live in sched.h, but moved to other header files in the
      course of cleaning it up.
      
      To ease the pain, this time I did not fiddle with any header files and only
      removed #includes from .c-files, which tend to cause less trouble.
      
      Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha,
      arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig,
      allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all
      configs in arch/arm/configs on arm.  I also checked that no new warnings were
      introduced by the patch (actually, some warnings are removed that were emitted
      by unnecessarily included header files).
      Signed-off-by: NTim Schmielau <tim@physik3.uni-rostock.de>
      Acked-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      cd354f1a
  10. 13 2月, 2007 1 次提交
  11. 10 2月, 2007 1 次提交
  12. 08 2月, 2007 1 次提交
  13. 18 1月, 2007 1 次提交
  14. 01 1月, 2007 1 次提交
  15. 08 12月, 2006 2 次提交
  16. 02 12月, 2006 1 次提交
  17. 24 11月, 2006 2 次提交
  18. 22 11月, 2006 1 次提交
    • D
      WorkStruct: Pass the work_struct pointer instead of context data · 65f27f38
      David Howells 提交于
      Pass the work_struct pointer to the work function rather than context data.
      The work function can use container_of() to work out the data.
      
      For the cases where the container of the work_struct may go away the moment the
      pending bit is cleared, it is made possible to defer the release of the
      structure by deferring the clearing of the pending bit.
      
      To make this work, an extra flag is introduced into the management side of the
      work_struct.  This governs auto-release of the structure upon execution.
      
      Ordinarily, the work queue executor would release the work_struct for further
      scheduling or deallocation by clearing the pending bit prior to jumping to the
      work function.  This means that, unless the driver makes some guarantee itself
      that the work_struct won't go away, the work function may not access anything
      else in the work_struct or its container lest they be deallocated..  This is a
      problem if the auxiliary data is taken away (as done by the last patch).
      
      However, if the pending bit is *not* cleared before jumping to the work
      function, then the work function *may* access the work_struct and its container
      with no problems.  But then the work function must itself release the
      work_struct by calling work_release().
      
      In most cases, automatic release is fine, so this is the default.  Special
      initiators exist for the non-auto-release case (ending in _NAR).
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      65f27f38
  19. 17 11月, 2006 2 次提交
  20. 03 11月, 2006 2 次提交
  21. 16 10月, 2006 1 次提交
  22. 12 10月, 2006 1 次提交
  23. 11 10月, 2006 2 次提交
  24. 10 10月, 2006 1 次提交
  25. 07 10月, 2006 1 次提交
  26. 05 10月, 2006 1 次提交
    • 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
  27. 04 10月, 2006 1 次提交
  28. 01 10月, 2006 1 次提交
    • O
      [PATCH] update legacy io handling for pmac · 30cbc222
      Olaf Hering 提交于
      ppc can boot one single binary on prep, chrp and pmac boards.  ppc64 can
      boot one single binary on pseries and G5 boards.  pmac has no legacy io,
      probing for PC style legacy hardware (or accessing the legacy io area
      regulary) may lead to a hard crash:
      
      * add check for parport_pc, exit on pmac.  32bit chrp has no
        ->check_legacy_ioport, the probe is always called.  64bit chrp has
        check_legacy_ioport, check for a "parallel" node
      
      * add check for isapnp, only PReP boards may have real ISA slots.  32bit
        PReP will have no ->check_legacy_ioport, the probe is always called.
      
      * update code in i8042_platform_init.  Run ->check_legacy_ioport first,
        always call request_region.  No functional change.  Remove whitespace
        before i8042_reset init.
      Signed-off-by: NOlaf Hering <olaf@aepfle.de>
      Acked-by: NBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Cc: Paul Mackerras <paulus@samba.org>
      Cc: Adam Belay <ambx1@neo.rr.com>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      30cbc222
  29. 14 9月, 2006 2 次提交