1. 08 3月, 2011 3 次提交
    • P
      OMAP2+: powerdomain: add pwrdm_can_ever_lose_context() · 694606c4
      Paul Walmsley 提交于
      Some drivers wish to know whether the device that they control can
      ever lose context, for example, when the device's enclosing
      powerdomain loses power.  They can use this information to determine
      whether it is necessary to save and restore device context, or whether
      it can be skipped.  Implement the powerdomain portion of this by
      adding the function pwrdm_can_ever_lose_context().  This is not for
      use directly from driver code, but instead is intended to be called
      from driver-subarch integration code (i.e., arch/arm/*omap* code).
      
      Currently, the result from this function should be passed into the
      driver code via struct platform_data, but at some point this should
      be part of some common or OMAP-specific device code.
      
      While here, update file copyrights.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      694606c4
    • P
      OMAP2+: powerdomain: fix bank power state bitfields · 4cb49fec
      Paul Walmsley 提交于
      The bank power state bitfields in the powerdomain data are
      encoded incorrectly.  These fields are intended to be bitfields,
      representing a set of power states that the memory banks support.
      However, when only one power state was supported by a given bank,
      the field was incorrectly set to the bit shift -- not the mask.
      While here, update some file copyrights.
      
      The OMAP4 autogeneration scripts have been updated accordingly.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      4cb49fec
    • P
      OMAP2/3: WKUP powerdomain: mark as being always on · cad7a34b
      Paul Walmsley 提交于
      Mark the WKUP powerdomain as being always on -- at least, as long as the
      chip has power.  This will be used to enable the powerdomain code to
      determine whether a given powerdomain is ever able to power off.  While
      here, update the file copyright.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      
      cad7a34b
  2. 02 3月, 2011 2 次提交
  3. 26 2月, 2011 1 次提交
    • S
      omap4: prcm: Fix the CPUx clockdomain offsets · 51c404b2
      Santosh Shilimkar 提交于
      CPU0 and CPU1 clockdomain is at the offset of 0x18 from the LPRM base.
      The header file has set it wrongly to 0x0. Offset 0x0 is for CPUx power
      domain control register
      
      Fix the same.
      
      The autogen scripts is fixed thanks to Benoit Cousson
      
      With the old value, the clockdomain code would access the
      *_PWRSTCTRL.POWERSTATE field when it thought it was accessing the
      *_CLKSTCTRL.CLKTRCTRL field.  In the worst case, this could cause
      system power management to behave incorrectly.
      Signed-off-by: NSantosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Cc: Benoit Cousson <b-cousson@ti.com>
      [paul@pwsan.com: added second paragraph to commit message]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      51c404b2
  4. 25 2月, 2011 1 次提交
    • P
      OMAP2+: clocksource: fix crash on boot when !CONFIG_OMAP_32K_TIMER · cbc94380
      Paul Walmsley 提交于
      
      OMAP2+ kernels built without CONFIG_OMAP_32K_TIMER crash on boot after the
      2.6.38 sched_clock changes:
      
      [    0.000000] OMAP clockevent source: GPTIMER1 at 13000000 Hz
      [    0.000000] Unable to handle kernel NULL pointer dereference at virtual address 00000000
      [    0.000000] pgd = c0004000
      [    0.000000] [00000000] *pgd=00000000
      [    0.000000] Internal error: Oops: 80000005 [#1] SMP
      [    0.000000] last sysfs file:
      [    0.000000] Modules linked in:
      [    0.000000] CPU: 0    Not tainted  (2.6.38-rc5-00057-g04aa67de #152)
      [    0.000000] PC is at 0x0
      [    0.000000] LR is at sched_clock_poll+0x2c/0x3c
      
      Without CONFIG_OMAP_32K_TIMER, the kernel has an clockevent and
      clocksource resolution about three orders of magnitude higher than
      with CONFIG_OMAP_32K_TIMER set.  The tradeoff is that the lowest
      power consumption states are not available.
      
      Fix by calling init_sched_clock() from the GPTIMER clocksource init code.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      cbc94380
  5. 23 2月, 2011 1 次提交
    • J
      OMAP2/3: clock: fix fint calculation for DPLL_FREQSEL · ea68c00e
      John Ogness 提交于
      In OMAP35X TRM Rev 2010-05 Figure 7-18 "DPLL With EMI Reduction
      Feature", it is shown that the internal frequency is calculated by
      CLK_IN/(N+1). However, the value passed to _dpll_test_fint() is
      already "N+1" since Linux is using the values to divide by. In the
      technical reference manual, "N" is referring to the divider's register
      value (0-127).
      
      During power management testing, it was observed that programming the
      wrong jitter correction value can cause the system to become unstable
      and eventually crash.
      Signed-off-by: NJohn Ogness <john.ogness@linutronix.de>
      [paul@pwsan.com: added second paragraph to commit message]
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      ea68c00e
  6. 22 2月, 2011 10 次提交
  7. 19 2月, 2011 6 次提交
  8. 18 2月, 2011 3 次提交
  9. 17 2月, 2011 6 次提交
  10. 15 2月, 2011 2 次提交
  11. 12 2月, 2011 4 次提交
  12. 11 2月, 2011 1 次提交