1. 17 Feb, 2011 7 commits
  2. 02 Feb, 2011 1 commit
  3. 01 Feb, 2011 3 commits
  4. 31 Jan, 2011 3 commits
  5. 27 Jan, 2011 3 commits
  6. 26 Jan, 2011 1 commit
    • Kevin Hilman's avatar
      OMAP3: PM: fix save secure RAM to restore MPU power state · 617fcc98
      Kevin Hilman authored
      
      
      Currently, on HS/EMU devices, MPU power state forced to on during PM
      init by the save secure RAM code.  Rather than forcing the state of
      MPU powerdomain to on, simply read the current value and restore it
      after the ROM code has run.
      
      This only affects the !CPUidle case since when CPUidle is enabled, the
      MPU power state is dynamically changed by CPUidle.  In the !CPUidle
      case, MPU power state is initialized once at init and never touched.
      Acked-by: default avatarTero Kristo <tero.kristo@nokia.com>
      Signed-off-by: default avatarKevin Hilman <khilman@ti.com>
      617fcc98
  7. 25 Jan, 2011 1 commit
    • Torben Hohn's avatar
      console: rename acquire/release_console_sem() to console_lock/unlock() · ac751efa
      Torben Hohn authored
      
      
      The -rt patches change the console_semaphore to console_mutex.  As a
      result, a quite large chunk of the patches changes all
      acquire/release_console_sem() to acquire/release_console_mutex()
      
      This commit makes things use more neutral function names which dont make
      implications about the underlying lock.
      
      The only real change is the return value of console_trylock which is
      inverted from try_acquire_console_sem()
      
      This patch also paves the way to switching console_sem from a semaphore to
      a mutex.
      
      [akpm@linux-foundation.org: coding-style fixes]
      [akpm@linux-foundation.org: make console_trylock return 1 on success, per Geert]
      Signed-off-by: default avatarTorben Hohn <torbenh@gmx.de>
      Cc: Thomas Gleixner <tglx@tglx.de>
      Cc: Greg KH <gregkh@suse.de>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Geert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      ac751efa
  8. 24 Jan, 2011 1 commit
  9. 19 Jan, 2011 3 commits
  10. 18 Jan, 2011 3 commits
    • Felipe Balbi's avatar
      OMAP: PRCM: remove duplicated headers · bc9fcaf3
      Felipe Balbi authored
      
      
      A few headers are included twice, remove them.
      
      Found the following errors using make includecheck:
      arch/arm/mach-omap2/clock44xx_data.c: prm44xx.h is
      included more than once.
      arch/arm/mach-omap2/clockdomains44xx_data.c: cm1_44xx.h
      is included more than once.
      arch/arm/mach-omap2/clockdomains44xx_data.c: cm2_44xx.h
      is included more than once.
      arch/arm/mach-omap2/powerdomain2xxx_3xxx.c: prm-regbits-34xx.h
      is included more than once.
      
      Cc: Paul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Signed-off-by: default avatarFelipe Balbi <balbi@ti.com>
      [paul@pwsan.com: dropped lists from patch cc:s; tweaked subject line]
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      bc9fcaf3
    • Paul Walmsley's avatar
      OMAP4: clockdomain: bypass unimplemented wake-up dependency functions on OMAP4 · 56bc78d4
      Paul Walmsley authored
      Commit 56a6a19d ("omap2plus: prm:
      Trvial build break fix for undefined reference to
      'omap2_prm_read_mod_reg'") generates a lot of warnings on boot since
      clockdomain functions that manipulate wake-up dependencies are not
      implemented yet on OMAP4 for 2.6.38.  This patch bypasses the OMAP2/3
      functions on OMAP4, which in turn avoids the warnings when the
      functions would attempt to call the underlying OMAP2/3 PRCM functions.
      A one-line warning is still logged from the clockdomain code that the
      OMAP4 wake-up dependency code is not yet implemented.
      
      A clockdomain wake-up and sleep dependency implementation for OMAP4
      from Rajendra should be possible to merge during the 2.6.39 merge
      window:
      
          http://www.mail-archive.com/linux-omap@vger.kernel.org/msg41748.html
      
          http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42222.html
      
      Reported-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Acked-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      56bc78d4
    • Paul Walmsley's avatar
      OMAP: counter_32k: init clocksource as part of machine timer init · d8328f3b
      Paul Walmsley authored
      After commit dc548fbb ("ARM: omap: convert
      sched_clock() to use new infrastructure"), OMAPs that use the 32KiHz
      "synchronization timer" as their clocksource crash during boot:
      
      [    0.000000] OMAP clockevent source: GPTIMER1 at 32768 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    Tainted: G        W    (2.6.37-07734-g2467802 #7)
      [    0.000000] PC is at 0x0
      [    0.000000] LR is at sched_clock_poll+0x2c/0x3c
      [    0.000000] pc : [<00000000>]    lr : [<c0060b74>]    psr: 600001d3
      [    0.000000] sp : c058bfd0  ip : c058a000  fp : 00000000
      [    0.000000] r10: 00000000  r9 : 411fc092  r8 : 800330c8
      [    0.000000] r7 : c05a08e0  r6 : c0034c48  r5 : c05ffc40  r4 : c0034c4c
      [    0.000000] r3 : c05ffe6c  r2 : c05a0bc0  r1 : c059f098  r0 : 00000000
      [    0.000000] Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
      [    0.000000] Control: 10c53c7f  Table: 8000404a  DAC: 00000017
      
      This is due to the recent ARM init_sched_clock() changes and the late
      initialization of the counter_32k clock source.  More information here:
      
         http://marc.info/?l=linux-omap&m=129513468605208&w=2
      
      
      
      Fix by initializing the counter_32k clocksource during the machine timer
      initialization.
      Reported-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      Tested-by: default avatarThomas Weber <weber@corscience.de>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      d8328f3b
  11. 13 Jan, 2011 2 commits
  12. 12 Jan, 2011 1 commit
  13. 11 Jan, 2011 4 commits
  14. 10 Jan, 2011 7 commits