1. 12 7月, 2007 1 次提交
  2. 02 7月, 2007 1 次提交
  3. 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
  4. 01 7月, 2006 1 次提交
  5. 02 2月, 2006 1 次提交
  6. 05 1月, 2006 1 次提交
  7. 30 10月, 2005 1 次提交
  8. 28 10月, 2005 1 次提交
    • T
      [ARM] 2787/2: PXA27x low power modes support · 80a18573
      Todd Poynor 提交于
      Patch from Todd Poynor
      
      Add symbols for PXA2xx PWRMODE register M field that selects low-power
      mode, replace unadorned constants.  Honor power mode parameter of
      pxa_cpu_suspend(mode), no longer force to 3 (sleep).  Full Deep Sleep
      low-power mode support for PXA27x is pending generic PM interfaces to
      select more than 2 suspend-to-RAM-style power modes, but this is
      expected soon. This can be hardcoded in the meantime by replacing the
      pxa_cpu_suspend() parameter value.  From David Burrage and Todd Poynor.
      Try #2 removes one of the register copies and moves the code to save the
      pxa_cpu_suspend parameter to immediately surround the call that requires
      the parameter value be preserved.
      Signed-off-by: NTodd Poynor <tpoynor@mvista.com>
      Signed-off-by: NNicolas Pitre <nico@cam.org>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      80a18573
  9. 01 7月, 2005 1 次提交
  10. 14 6月, 2005 1 次提交
  11. 04 6月, 2005 1 次提交
    • T
      [PATCH] ARM: 2691/1: PXA27x sleep fixes take 2 · 8775420d
      Todd Poynor 提交于
      Patch from Todd Poynor
      
      PXA27x sleep fixes:
      * set additional sleep/wakeup registers for Mainstone boards.
      * move CKEN=0 to pxa25x-specific code; that value is harmful on pxa27x.
      * save/restore additional registers, including some found necessary for
      C5 processors and/or newer blob versions.
      * enable future support of additional sleep modes for PXA27x (eg,
      standby, deep sleep).
      * split off cpu-specific sleep processing between pxa27x and pxa25x into
      separate files (partly in preparation for additional sleep modes).
      Includes fixes from David Burrage.
      
      Signed-off-by: Todd Poynor
      Signed-off-by: Nicolas Pitre
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      8775420d
  12. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4