1. 13 Aug, 2008 3 commits
    • Paul Walmsley's avatar
      OMAP2/3 GPTIMER: allow system tick GPTIMER to be configurable at build · 0c00fb73
      Paul Walmsley authored
      Add Kbuild code to allow the builder to select which GPTIMER block to use
      for the Linux clockevents timer.  Practical choices at this point are
      GPTIMER1 or GPTIMER12.  Both of these timers are in the WKUP powerdomain,
      and so are unaffected by chip power management.  GPTIMER1 can use sys_clk
      as a source, for applications where a high-resolution timer is more important
      than power management.  GPTIMER12 has the special property that it has
      the secure 32kHz oscillator as its source clock, which may be less prone
      to glitches than the off-chip 32kHz oscillator.  But on HS devices, it may
      not be available for Linux use.
      
      At this point, it appears that most boards are fine with GPTIMER1, but
      Beagle should use GPTIMER12.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      0c00fb73
    • Paul Walmsley's avatar
      OMAP2/3 clockdomains: autodeps should respect platform flags · b5ea90ae
      Paul Walmsley authored
      Fix the clockdomain autodep code to respect omap_chip platform flags.
      
      Resolves "Unable to handle kernel paging request at virtual address
      5f75706d" panic during power management initialization on OMAP2.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      b5ea90ae
    • Paul Walmsley's avatar
      OMAP2 clock: associate clocks with clockdomains at startup · 8a38aadc
      Paul Walmsley authored
      The OMAP2 clock code was missing code to associate clocks with clockdomains
      at registration time; fix this.
      
      Resolves "Unhandled fault: alignment exception (0x001) at 0xc02c1b4e" (address
      may vary) panic during clock framework init on OMAP2.  The alignment error
      was caused by an attempt to dereference a pointer to a string (1-byte aligned)
      as if it were a pointer to a structure.
      
      Thanks to Felipe Balbi <felipe.balbi@nokia.com> for originally reporting this
      bug.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      8a38aadc
  2. 08 Aug, 2008 10 commits
  3. 06 Aug, 2008 6 commits
  4. 05 Aug, 2008 21 commits