1. 18 2月, 2010 1 次提交
    • W
      pcmcia/yenta: add module parameter for O2 speedups · 35169529
      Wolfram Sang 提交于
      O2-bridges can do read prefetch and write burst. However, for some combinations
      of older bridges and cards, this causes problems, so it is disabled for those
      bridges. Now, as some users know their setup works with the speedups enabled, a
      new parameter is introduced to the driver. Now, a user can specifically enable
      or disable these features, while the default is what we have today: detect the
      bridge and decide accordingly. Fixes Bugzilla entry 15014.
      
      Simplify and unify the printouts, fix a whitespace issue while we are here.
      Signed-off-by: NWolfram Sang <w.sang@pengutronix.de>
      Tested-by: frodone@gmail.com
      [linux@dominikbrodowski.net: whitespace fixes]
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      35169529
  2. 16 12月, 2009 1 次提交
  3. 08 12月, 2009 1 次提交
    • D
      pcmcia: CodingStyle fixes · 9fea84f4
      Dominik Brodowski 提交于
      Fix several CodingStyle issues in drivers/pcmcia/ . checkpatch.pl no longer
      reports errors in the PCMCIA core. The remaining warnings mostly relate to
      wrong indent -- PCMCIA historically used 4 spaces --, to lines over 80
      characters and to hundreds of typedefs. The cleanup of those will follow
      in the future.
      Signed-off-by: NDominik Brodowski <linux@dominikbrodowski.net>
      9fea84f4
  4. 03 11月, 2009 1 次提交
  5. 29 9月, 2009 2 次提交
  6. 22 9月, 2009 1 次提交
  7. 10 9月, 2009 1 次提交
  8. 23 8月, 2008 1 次提交
  9. 11 12月, 2007 1 次提交
  10. 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
  11. 08 2月, 2007 1 次提交
  12. 26 10月, 2006 2 次提交
  13. 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
  14. 03 7月, 2006 1 次提交
  15. 01 7月, 2006 4 次提交
  16. 06 1月, 2006 4 次提交
  17. 29 10月, 2005 1 次提交
  18. 26 9月, 2005 5 次提交
  19. 15 9月, 2005 2 次提交
  20. 10 9月, 2005 2 次提交
  21. 08 9月, 2005 1 次提交
    • D
      [PATCH] yenta: make ToPIC95 bridges work with 16bit cards · ea2f1590
      Daniel Ritz 提交于
      ToPIC95 brides (and maybe some other too) require to use the ExCA registers
      to power up the socket if a 16bit card is pluged.  allow socket drivers to
      set a flag so that yenta does just that.  also clean up yenta_get_status()
      a bit to use the new yenta_get_power() function.
      
      Side note: ToPIC97 bridges (at least in Rev.5 i have) don't require this.
      
      Ryan Underwood <nemesis-lists@icequake.net> said:
      
       According to the mail that David Hinds received from a Toshiba engineer,
       ToPIC95 and 97 do require this, and ToPIC100 does not.  Maybe you have a
       later revision.
      
       For all chips, 16-bit cards can be enabled through ExCA.  So doesn't it
       make sense just to make this the default behavior for all Toshiba chips,
       to avoid corner cases showing up later?
      
      Daniel responded:
      
       I disagree with ryan to change anything for topic97 bridges.  they work.
       and I couldn't find (read google) any report of a topic97 breaking on
       applying power with the CB registers.
      
       I'm having several toshba notebooks at work (and home) with topic95,97,100
       bridges.  Only the ones with a topic95 didn't work.
      Signed-off-by: NDaniel Ritz <daniel.ritz@gmx.ch>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      ea2f1590
  22. 05 8月, 2005 1 次提交
  23. 02 8月, 2005 1 次提交
    • P
      [PATCH] Obvious bugfix for yenta resource allocation · f7d1d23c
      Paul Mackerras 提交于
      Recent changes (well, dating from 12 July) have broken cardbus on my
      powerbook: I get 3 messages saying "no resource of type xxx available,
      trying to continue", and if I plug in my wireless card, it complains
      that there are no resources allocated to the card.  This all worked in
      2.6.12.
      
      Looking at the code in yenta_socket.c, function yenta_allocate_res,
      it's obvious what is wrong: if we get to line 639 (i.e. there wasn't a
      usable preassigned resource), we will always flow through to line 668,
      which is the printk that I was seeing, even if a resource was
      successfully allocated.  It looks to me as though there should be a
      return statement after the two config_writel's in each of the 3
      branches of the if statements, so that the function returns after
      successfully setting up the resource.
      
      The patch below adds these return statements, and with this patch,
      cardbus works on my powerbook once again.
      Signed-off-by: NPaul Mackerras <paulus@samba.org>
      Acked-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      f7d1d23c
  24. 31 7月, 2005 1 次提交
  25. 30 7月, 2005 1 次提交
  26. 28 7月, 2005 1 次提交