1. 23 5月, 2011 2 次提交
  2. 13 5月, 2011 2 次提交
    • A
      OMAP4: DSS2: DSI: Changes for DSI2 on OMAP4 · 5a8b572d
      Archit Taneja 提交于
      Introduce DSI2 PLL clock sources needed by LCD2 channel and DSI2 Protocol
      engine and DISPC Functional clock. Do the following:
      
      - Modify dss_get_dsi_clk_source() and dss_select_dsi_clk_source() to take the
        dsi module number as an argument.
      - Create debugfs files for dsi2, split the corresponding debugfs functions.
      - Allow DPI to use these new clock sources.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      5a8b572d
    • A
      OMAP: DSS2: Pass platform_device as an argument in dsi functions · a72b64b9
      Archit Taneja 提交于
      The DSI interface is represented as a platform device, using the DSI platform
      driver(dsi.c). The current DSI driver design is capable of running only one
      instance of a DSI device. On OMAP4, there are 2 very similar DSI modules which
      can be represented as instances of "omapdss_dsi" platform device.
      
      Add member "module" in "dssdev.phy.dsi" that tells us which DSI module's lanes
      the panel is connected to. Modify dsi.c functions to take the device's
      platform_device struct pointer, provide functions dsi_get_dsidev_from_dssdev()
      and dsi_get_dsidev_from_id() take the panel's omap_dss_device and module number
      respectively, and return the platform_device pointer. Currently, the dsi struct
      is declared globally and is accessed when dsi data is needed. The new pdev
      argument will be used later to provide the platform device's dsi related data.
      Signed-off-by: NArchit Taneja <archit@ti.com>
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      a72b64b9
  3. 11 5月, 2011 5 次提交
  4. 16 3月, 2011 1 次提交
  5. 11 3月, 2011 14 次提交
  6. 10 1月, 2011 9 次提交
  7. 23 10月, 2010 1 次提交
  8. 29 9月, 2010 1 次提交
  9. 05 8月, 2010 1 次提交
    • T
      OMAP: DSS2: DSI: use BTA to end the frame transfer · ab83b14c
      Tomi Valkeinen 提交于
      Previously a work was started on FRAMEDONE interrupt, and this work
      either sent a BTA synchronously or looped until TE_SIZE was zero, to
      wait for the end of the transfer.
      
      This patch changes a BTA to be sent asynchronously from FRAMEDONE
      interrupt, and when a BTA interrupt is received, the transfer is
      finished. This way we do the whole process asynchronously, and also
      inside interrupt context.
      
      This will give us much better latency to handle the end of the frame
      than with the previous work based solution.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@nokia.com>
      ab83b14c
  10. 03 8月, 2010 1 次提交
  11. 24 2月, 2010 2 次提交
  12. 23 2月, 2010 1 次提交