1. 10 3月, 2011 3 次提交
    • B
      OMAP3: hwmod data: Fix incorrect SmartReflex -> L4 CORE interconnect links · b9ccf8af
      Benoit Cousson 提交于
      Commit d3442726 ("OMAP3: PM: Adding
      smartreflex hwmod data") added data that claims that the L4 CORE has
      two slave interfaces that originate from the SmartReflex modules,
      omap3_l4_core__sr1 and omap3_l4_core__sr2.  But as those two data
      structure records show, it's L4 CORE that has a master port towards
      SR1 and SR2.
      Move the incorrect data from slaves list to master list.
      
      Based on a path by Paul Walmsley <paul@pwsan.com>
      
          https://patchwork.kernel.org/patch/623171/
      
      That is based on a patch by Benoît Cousson <b-cousson@ti.com>:
      
          https://patchwork.kernel.org/patch/590561/Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NBenoît Cousson <b-cousson@ti.com>
      Cc: Sanjeev Premi <premi@ti.com>
      Cc: Thara Gopinath <thara@ti.com>
      b9ccf8af
    • T
      Merge branch 'omap-l3-for-next' of... · 0dde52a9
      Tony Lindgren 提交于
      Merge branch 'omap-l3-for-next' of git://dev.omapzoom.org/pub/scm/santosh/kernel-omap4-base into omap-for-linus
      0dde52a9
    • P
      OMAP2/3: VENC hwmod: add OCPIF_SWSUP_IDLE flag to interface · c39bee8a
      Paul Walmsley 提交于
      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: NPaul 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: NTony Lindgren <tony@atomide.com>
      c39bee8a
  2. 09 3月, 2011 8 次提交
  3. 05 3月, 2011 1 次提交
  4. 03 3月, 2011 8 次提交
  5. 02 3月, 2011 10 次提交
  6. 01 3月, 2011 10 次提交