1. 26 Jul, 2010 3 commits
    • Paul Walmsley's avatar
      OMAP1: OPP: add KConfig entry for 96MHz ARM rate (using a 12MHz oscillator) · 936305a9
      Paul Walmsley authored
      Add KConfig entry for one of the OMAP1 DVFS rates that was missing it.
      Based on the surrounding rate KConfigs and the oscillator frequency,
      this patch marks it as valid for all OMAP1 platforms -- Richard,
      Tuukka, Tony, perhaps you can comment if this does not look right?
      
      In the long term, all of these CONFIG_OMAP_ARM_*MHZ should be removed.
      The OPP settings should be associated with the platform information in
      the structure data (perhaps by extending the omap_chip defines).  The
      selection of which rates to use should be handled at runtime; rates
      that are impossible due to xtal frequency mismatch or SoC-type
      mismatch should not be included.  If implemented correctly, this
      should save some CPU time and some memory on OMAP1 kernels.
      Reported-by: default avatarChristoph Egger <siccegge@cs.fau.de>
      Reported-by: default avatarThe VAMOS Research Project <vamos@i4.informatik.uni-erlangen.de>
      Cc: Marek Vasut <marek.vasut@gmail.com>
      Cc: Richard Woodruff <r-woodruff2@ti.com>
      Cc: Tuukka Tikkanen <tuukka.tikkanen@nokia.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      936305a9
    • Paul Walmsley's avatar
      OMAP: clock: add kerneldoc for structures; move flags closer to structs · b3c1cff6
      Paul Walmsley authored
      Add kerneldoc for struct clk, struct clksel_rate, struct clksel.  Move
      flag macros for struct clk.flags and struct clksel_rate.flags closer
      to the structures.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      b3c1cff6
    • Anand Gadiyar's avatar
      OMAP3: wait on IDLEST after enabling USBTLL fclk · 25499d93
      Anand Gadiyar authored
      We need to wait on the IDLEST bit after the clocks are enabled
      before attempting to access any register.
      
      Currently, the USBTLL i-clock ops uses the clkops_omap2_dflt_wait,
      while the USBTLL f-clock ops uses clkops_omap2_dflt. If the
      i-clock is enabled first, the clkops_omap2_dflt_wait is
      short-circuited as the companion f-clock is not enabled.
      This can cause a data abort if the IDLEST has not transitioned,
      and we try to access a USBTLL register.
      
      Since the USBTLL i-clock and f-clock could be enabled in any order,
      this is a bug. Fix it by changing the clkops for the f-clock.
      Signed-off-by: default avatarAnand Gadiyar <gadiyar@ti.com>
      Acked-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      25499d93
  2. 22 Jul, 2010 18 commits
  3. 21 Jul, 2010 14 commits
  4. 20 Jul, 2010 5 commits