1. 03 3月, 2011 6 次提交
  2. 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
  3. 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
  4. 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
  5. 22 2月, 2011 10 次提交
  6. 19 2月, 2011 6 次提交
  7. 18 2月, 2011 3 次提交
  8. 17 2月, 2011 6 次提交
  9. 15 2月, 2011 2 次提交
  10. 12 2月, 2011 4 次提交