Skip to content

L
linux-davinci
Switch branch/tag
  1. 13 Aug, 2008 4 commits
    • Paul Walmsley's avatar
      BeagleBoard: make Beagle use GPTIMER12 for system ticks · 9882ca1b
      Paul Walmsley authored 
      There is suspicion that the 32kHz input clock to the OMAP may be noisy
on BeagleBoards.  On OMAP2/3 GPTIMER1, this can cause the timer
counter register to warp to unknown values or miss interrupt
conditions.  So, use GPTIMER12 instead, which apparently has its own
secure 32kHz oscillator and will hopefully not be prone to the
suspected sys_32k glitches.

This is only a workaround.  If sys_32k is noisy, other system peripherals
may be affected.

This workaround is a collective product of several people, most notably
Philip Balister <philip@balister.org>, Dirk Behme <dirk.behme@googlemail.com>,
Koen Kooi <k.kooi@student.utwente.nl>, Tony Lindgren <tony@atomide.com>,
Steve Sakoman <sakoman@gmail.com>, Khasim Syed Mohammed <khasim@ti.com>
Richard Woodruff <r-woodruff2@ti.com>, Kevin Hilman <khilman@deeprootsystems.com>.
I apologize if there is anyone whom I've missed.
Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
Cc: Khasim Syed Mohammed <khasim@ti.com>
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Cc: Steve Sakoman <sakoman@gmail.com>
Cc: Richard Woodruff <r-woodruff2@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Philip Balister <philip@balister.org>
Cc: Dirk Behme <dirk.behme@googlemail.com>
Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      9882ca1b
    • 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
  3. 08 Aug, 2008 10 commits
  5. 06 Aug, 2008 6 commits
  7. 05 Aug, 2008 20 commits