1. 09 Mar, 2011 1 commit
    • Paul Walmsley's avatar
      OMAP2/3: VENC hwmod: add OCPIF_SWSUP_IDLE flag to interface · c39bee8a
      Paul Walmsley authored
      According to the hwmod interface data, the DSS submodule "VENC" uses a
      clock, "dss_54m_fck"/"dss_tv_fck", which the PRCM cannot autoidle.  By
      default, the hwmod code assumes that interface clocks can be autoidled
      by the PRCM.  When the interface clock can't be autoidled by the PRCM,
      those interfaces must be marked with the OCPIF_SWSUP_IDLE flag.
      Otherwise, the "interface clock" will always have a non-zero use
      count, and the device won't enter idle.  This problem was observed on
      N8x0.
      
      Fix the immediate problem by marking the VENC interface with the
      OCPIF_SWSUP_IDLE flag.  But it's not clear that
      "dss_54m_fck"/"dss_tv_fck" is really the correct interface clock for
      VENC.  It may be that the VENC interface should use a
      hardware-autoidling interface clock.  This is the situation on OMAP4,
      which uses "l3_div_ck" as the VENC interface clock, which can be
      autoidled by the PRCM.  Clarification from TI is needed.
      
      Problem found and patch tested on N8x0 by Tony Lindgren
      <tony@atomide.com>.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Senthilvadivu Guruswamy <svadivu@ti.com>
      Cc: Sumit Semwal <sumit.semwal@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      c39bee8a
  2. 08 Mar, 2011 2 commits
  3. 04 Mar, 2011 1 commit
  4. 03 Mar, 2011 8 commits
  5. 01 Mar, 2011 23 commits
  6. 28 Feb, 2011 5 commits
    • Paul Walmsley's avatar
      OMAP2+: clockevent: set up GPTIMER clockevent hwmod right before timer init · 38698bef
      Paul Walmsley authored
      Set up the GPTIMER hwmod used for the clockevent source immediately
      before it is used.  This avoids the need to set up all of the hwmods
      until the boot process is further along.  (In general, we want to defer
      as much as possible until late in the boot process.)
      
      This second version fixes a bug pointed out by Santosh Shilimkar
      <santosh.shilimkar@ti.com>, that would cause the kernel to use an
      incorrect timer hwmod name if the selected GPTIMER was not 1 or 12 -
      thanks Santosh.  Also, Tarun Kanti DebBarma <tarun.kanti@ti.com>
      pointed out that the original patch did not apply cleanly; this has
      now been fixed.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Acked-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Tarun Kanti DebBarma <tarun.kanti@ti.com>
      38698bef
    • Paul Walmsley's avatar
      OMAP2+: hwmod: add ability to setup individual hwmods · a2debdbd
      Paul Walmsley authored
      Add omap_hwmod_setup_one(), which is intended for use early in boot to
      selectively setup the hwmods needed for system clocksources and
      clockevents, and any other hwmod that is needed in early boot.
      omap_hwmod_setup_all() can then be called later in the boot process.
      The point is to minimize the amount of code that needs to be run
      early.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      a2debdbd
    • Paul Walmsley's avatar
      OMAP2+: hwmod: ignore attempts to re-setup a hwmod · 48d54f3f
      Paul Walmsley authored
      Previously, if a hwmod had already been set up, and the code attempted
      to set up the hwmod again, an error would be returned.  This is not
      really useful behavior if we wish to allow the OMAP core code to setup
      the hwmods needed for the Linux clocksources and clockevents before
      the rest of the hwmods are setup.  So, instead of generating errors,
      just ignore the attempt to re-setup the hwmod.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      48d54f3f
    • Paul Walmsley's avatar
      OMAP2+: hwmod: find MPU initiator hwmod during in _register() · 569edd70
      Paul Walmsley authored
      Move the code that looks for the MPU initiator hwmod to run during
      the individual hwmod _register() function.  (Previously, it ran after
      all hwmods were registered in the omap_hwmod_late_init() function.)
      
      This is done so code can late-initialize a few individual hwmods --
      for example, for the system timer -- before the entire set of hwmods is
      initialized later in boot via omap_hwmod_late_init().
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      569edd70
    • Paul Walmsley's avatar
      OMAP2+: hwmod: rename some init functions · 550c8092
      Paul Walmsley authored
      Rename omap_hwmod_init() to omap_hwmod_register().  Rename
      omap_hwmod_late_init() to omap_hwmod_setup_all().  Also change all of
      the callers to reflect the new names.  While here, update some
      copyrights.
      
      Suggested by Tony Lindgren <tony@atomide.com>.
      
      N.B. The comment in mach-omap2/serial.c may no longer be correct, given
           recent changes in init order.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Kevin Hilman <khilman@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      550c8092