1. 13 7月, 2009 1 次提交
  2. 19 2月, 2009 1 次提交
  3. 08 1月, 2009 1 次提交
  4. 07 1月, 2009 1 次提交
  5. 27 11月, 2008 1 次提交
  6. 23 11月, 2008 1 次提交
  7. 07 8月, 2008 1 次提交
  8. 26 7月, 2008 1 次提交
  9. 22 7月, 2008 1 次提交
  10. 11 7月, 2008 1 次提交
  11. 10 7月, 2008 1 次提交
  12. 19 5月, 2008 1 次提交
    • R
      [ARM] pxa: separate PXA25x and PXA27x UDC register definitions · 284d115e
      Russell King 提交于
      The PXA25x and PXA27x USB device controller register definitions are
      different.  Currently, they live side by side in pxa-regs.h, but only
      one set is available depending on the setting of PXA25x or PXA27x.
      
      This means that if we build to support both PXA25x and PXA27x, the
      PXA27x definitions are unavailable, even to PXA27x specific code.
      
      Remove these definitions from pxa-regs.h, and place them in separate
      files.  Include these files where appropriate.
      
      Note: according to the dependencies in drivers/usb/gadget/Kconfig,
      we do not support the UDC on PXA27x nor PXA3xx CPUs, so remove the
      platform devices from pxa27x.c and pxa3xx.c.
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      284d115e
  13. 25 4月, 2008 1 次提交
  14. 11 4月, 2008 1 次提交
  15. 05 3月, 2008 1 次提交
  16. 02 2月, 2008 4 次提交
  17. 13 10月, 2007 2 次提交
  18. 23 8月, 2007 1 次提交
  19. 31 7月, 2007 1 次提交
  20. 13 7月, 2007 3 次提交
  21. 28 4月, 2007 2 次提交
  22. 22 4月, 2007 1 次提交
    • E
      [ARM] 4304/1: removes the unnecessary bit number from CKENnn_XXXX · 7053acbd
      Eric Miao 提交于
      This patch removes the unnecessary bit number from CKENnn_XXXX
      definitions for PXA, so that
      
      	CKEN0_PWM0 --> CKEN_PWM0
      	CKEN1_PWM1 --> CKEN_PWM1
      	...
      	CKEN24_CAMERA --> CKEN_CAMERA
      
      The reasons for the change of these defitions are:
      
      1. they do not scale - they are currently valid for pxa2xx, but
      definitely not valid for pxa3xx, e.g., pxa3xx has bit 3 for camera
      instead of bit 24
      
      2. they are unnecessary - the peripheral name within the definition
      has already announced its usage, we don't need those bit numbers
      to know which peripheral we are going to enable/disable clock for
      
      3. they are inconvenient - think about this: a driver programmer
      for pxa has to remember which bit in the CKEN register to turn
      on/off
      
      Another change in the patch is to make the definitions equal to its
      clock bit index, so that
      
         #define CKEN_CAMERA  (24)
      
      instead of
      
         #define CKEN_CAMERA  (1 << 24)
      
      this change, however, will add a run-time bit shift operation in
      pxa_set_cken(), but the benefit of this change is that it scales
      when bit index exceeds 32, e.g., pxa3xx has two registers CKENA
      and CKENB, totally 64 bit for this, suppose CAMERA clock enabling
      bit is CKENB:10, one can simply define CKEN_CAMERA to be (32 + 10)
      and so that pxa_set_cken() need minimum change to adapt to that.
      Signed-off-by: Neric miao <eric.y.miao@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      7053acbd
  23. 11 3月, 2007 1 次提交
  24. 10 3月, 2007 1 次提交
  25. 15 2月, 2007 2 次提交
    • T
      [PATCH] Scheduled removal of SA_xxx interrupt flags fixups · 38515e90
      Thomas Gleixner 提交于
      The obsolete SA_xxx interrupt flags have been used despite the scheduled
      removal.  Fixup the remaining users.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Acked-by: NIngo Molnar <mingo@elte.hu>
      Cc: "Luck, Tony" <tony.luck@intel.com>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Cc: Jeff Garzik <jeff@garzik.org>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Roland Dreier <rolandd@cisco.com>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: James Bottomley <James.Bottomley@steeleye.com>
      Cc: Greg KH <greg@kroah.com>
      Cc: Dave Airlie <airlied@linux.ie>
      Cc: James Simmons <jsimmons@infradead.org>
      Cc: "Antonino A. Daplas" <adaplas@pol.net>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      38515e90
    • 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
  26. 08 2月, 2007 2 次提交
  27. 21 12月, 2006 1 次提交
    • D
      USB: gadget driver unbind() is optional; section fixes; misc · 6bea476c
      David Brownell 提交于
      Allow gadget drivers to omit the unbind() method.  When they're
      statically linked, that's an appropriate memory saving tweak.
      
      Similarly, provide consistent/simpler handling for a should-not-happen
      error case:  removing a peripheral controller driver when a gadget
      driver is still loaded.  Such code dates back to early versions of the
      first implementation of the gadget API, and has never been triggered.
      
      Includes relevant section annotation fixs for gmidi.c, file_storage.c,
      and serial.c; we don't yet have an "init or exit" annotation.  Also
      some whitespace fixes in gmidi.c (space at EOL, before tabs, etc).
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      6bea476c
  28. 02 12月, 2006 1 次提交
  29. 21 10月, 2006 1 次提交
  30. 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
  31. 28 9月, 2006 1 次提交
    • D
      USB: pxa2xx_udc understands GPIO based VBUS sensing · b2bbb20b
      David Brownell 提交于
      This updates the PXA 25x UDC board-independent infrastructure for VBUS sensing
      and the D+ pullup.  The original code evolved from rather bizarre support on
      Intel's "Lubbock" reference hardware, so that on more sensible hardware it
      doesn't work as well as it could/should.
      
      The change is just to teach the UDC driver how to use built-in PXA GPIO pins
      directly.  This reduces the amount of board-specfic object code needed, and
      enables the use of a VBUS sensing IRQ on boards (like Gumstix) that have one.
      With VBUS sensing, the UDC is unclocked until a host is actually connected.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      b2bbb20b