1. 15 Jul, 2008 5 commits
  2. 17 May, 2008 1 commit
  3. 15 Apr, 2008 1 commit
  4. 08 Feb, 2008 1 commit
    • David Brownell's avatar
      at91_mci: use generic GPIO calls · 6e996ee8
      David Brownell authored
      
      
      Update the AT91 MMC driver to use the generic GPIO calls instead of the
      AT91-specific calls; and to request (and release) those GPIO signals.
      
      That required updating the probe() fault cleanup codepaths.  Now there
      is a single sequence for freeing resources, in reverse order of their
      allocation.  Also that code uses use dev_*() for messaging, and has less
      abuse of KERN_ERR.
      
      Likewise with updating remove() cleanup.  This had to free the GPIOs,
      and while adding that code I noticed and fixed two other problems:  it
      was poking at a workqueue owned by the mmc core; and in one (rare)
      case would try freeing an IRQ that it didn't allocate.
      Signed-off-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarNicolas Ferre <nicolas.ferre@atmel.com>
      Signed-off-by: default avatarPierre Ossman <drzeus@drzeus.cx>
      6e996ee8
  5. 22 Oct, 2007 1 commit
  6. 17 Oct, 2007 1 commit
  7. 23 Sep, 2007 4 commits
  8. 11 Sep, 2007 1 commit
  9. 09 Aug, 2007 1 commit
  10. 25 Jul, 2007 1 commit
  11. 20 Jul, 2007 1 commit
  12. 09 Jul, 2007 2 commits
  13. 07 Jun, 2007 1 commit
  14. 01 May, 2007 2 commits
  15. 08 Feb, 2007 1 commit
  16. 04 Feb, 2007 2 commits
  17. 03 Jan, 2007 1 commit
  18. 11 Dec, 2006 6 commits
  19. 01 Dec, 2006 1 commit
  20. 30 Nov, 2006 1 commit
  21. 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
  22. 28 Sep, 2006 1 commit
  23. 24 Sep, 2006 1 commit
    • Russell King's avatar
      [MMC] MMC_CAP_BYTEBLOCK flag for non-log2 block sizes capable hosts · 42431acb
      Russell King authored
      
      
      Some MMC hosts can only handle log2 block sizes.  Unfortunately,
      the MMC password support needs to be able to send non-log2 block
      sizes.  Provide a capability so that the MMC password support can
      decide whether it should use this support or not.
      
      The unfortunate side effect of this host limitation is that any
      MMC card protected by a password which is not a log2 block size
      can not be accessed on a host which only allows a log2 block size.
      
      This change just adds the flag.  The MMC password support code
      needs updating to use it (if and when it is finally submitted.)
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      42431acb
  24. 02 Jul, 2006 1 commit
  25. 30 Jun, 2006 1 commit