1. 15 4月, 2011 2 次提交
    • T
      OMAP: DSS2: DSI: fix dsi_dump_clocks() · 4eb68edb
      Tomi Valkeinen 提交于
      On OMAP4, reading DSI_PLL_CONFIGURATION2 register requires the L3 clock
      (CIO_CLK_ICG) to PLL. Currently dsi_dump_clocks() tries to read that
      register without enabling the L3 clock, leading to crash if DSI is not
      in use.
      
      The status of the bit being read from DSI_PLL_CONFIGURATION2 is
      available from dsi_clock_info->use_sys_clk, so we can avoid the whole
      problem by just using that.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      4eb68edb
    • T
      OMAP: DSS2: DSI: fix use_sys_clk & highfreq · ae038af1
      Tomi Valkeinen 提交于
      use_sys_clk and highfreq fields in dsi.current_cinfo were never set.
      Luckily they weren't used anywhere so it didn't cause any problems.
      
      This patch fixes those fields and they are now set at the same time as
      the rest of the fields.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      ae038af1
  2. 15 3月, 2011 8 次提交
  3. 11 3月, 2011 14 次提交
  4. 10 1月, 2011 2 次提交
  5. 23 10月, 2010 1 次提交
  6. 05 8月, 2010 12 次提交
  7. 03 8月, 2010 1 次提交
    • T
      OMAP: DSS2: DSI: change DSI timeout functions · 4ffa3571
      Tomi Valkeinen 提交于
      Using nanoseconds as arguments to functions that set the DSI timeouts was
      perhaps not so good idea. The timeouts are based on different DSI clocks,
      so the possible range for the timeouts vary greatly depending on the
      clocks. Also, the multipliers used with the timeouts cause big gaps in the
      timeout range, meaning that the nanosecond based functions could cause the
      timeout to be quite far from the intended value.
      
      This patch changes the functions to take the plain tick values with the
      multiplier enable/disable bits, and sets the TA/LP_RX/HS_TX timeouts to
      maximum. While the timeouts could be much lower, the fact is that when
      TA/LP_RX/HS_TX timeout happens, we are in an error situation and not in a
      hurry anyway.
      
      STOP_STATE_COUNTER is a different matter, but it is only used at
      initialization time, and won't normally affect the performance.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
      4ffa3571