1. 15 8月, 2017 12 次提交
  2. 02 6月, 2017 1 次提交
  3. 07 4月, 2017 1 次提交
    • R
      drm: omap: use common OF graph helpers · 09bffa6e
      Rob Herring 提交于
      The OMAP driver has its own OF graph helpers that are similar to the
      common helpers. This commit replaces most of the calls with the common
      helpers. There's still a couple of custom helpers left, but the driver
      needs more extensive changes to get rid of them.
      
      In dss_init_ports, we invert the loop, looping through the known ports
      and matching them to DT nodes rather than looping thru DT nodes and
      matching them to the ports.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Signed-off-by: NSean Paul <seanpaul@chromium.org>
      09bffa6e
  4. 03 4月, 2017 2 次提交
  5. 01 3月, 2017 1 次提交
  6. 03 6月, 2016 1 次提交
  7. 31 5月, 2016 1 次提交
  8. 20 5月, 2016 6 次提交
  9. 29 12月, 2015 1 次提交
  10. 17 12月, 2015 1 次提交
  11. 02 7月, 2015 1 次提交
    • T
      OMAPDSS: fix probing if rfbi device is enabled · 0438ec90
      Tomi Valkeinen 提交于
      After the commit 736e60dd ("OMAPDSS:
      componentize omapdss") the dss core device will wait until all the
      subdevices have been successfully probed. However, we don't have a
      working driver for RFBI, so if RFBI device exists, omapdss will never
      get probed.
      
      All the .dtsi files set RFBI as disabled, except am4372.dtsi. This
      causes omapdss probe to not finish on AM4 devices.
      
      This patch makes omapdss driver skip adding rfbi device as a
      subcomponent, solving the issue.
      
      This should be reverted when we have a working RFBI driver.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Reported-by: NFelipe Balbi <balbi@ti.com>
      0438ec90
  12. 17 6月, 2015 5 次提交
    • T
      OMAPDSS: componentize omapdss · 736e60dd
      Tomi Valkeinen 提交于
      omapdss kernel module contains drivers for multiple devices, one for
      each DSS submodule. The probing we have at the moment is a mess, and
      doesn't give us proper deferred probing nor ensure that all the devices
      are probed before omapfb/omapdrm start using omapdss.
      
      This patch solves the mess by using the component system for DSS
      submodules.
      
      The changes to all DSS submodules (dispc, dpi, dsi, hdmi4/5, rfbi, sdi,
      venc) are the same: probe & remove functions are changed to bind &
      unbind, and new probe & remove functions are added which call
      component_add/del.
      
      The dss_core driver (dss.c) acts as a component master. Adding and
      matching the components is simple: all dss device's child devices are
      added as components.
      
      However, we do have some dependencies between the drivers. The order in
      which they should be probed is reflected by the list in core.c
      (dss_output_drv_reg_funcs). The drivers are registered in that order,
      which causes the components to be added in that order, which makes the
      components to be bound in that order. This feels a bit fragile, and we
      probably should improve the code to manage binds in random order.
      However, for now, this works fine.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      736e60dd
    • T
      OMAPDSS: remove uses of __init/__exit · ede92695
      Tomi Valkeinen 提交于
      The following patches will add component handling to omapdss, improving
      the handling of deferred probing. However, at the moment we're using
      quite a lot of __inits and __exits in the driver, which prevent normal
      dynamic probing and removal.
      
      This patch removes most of the uses of __init and __exit, so that we can
      register drivers after module init, and so that we can unregister
      drivers even if the module is built-in.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      ede92695
    • T
      OMAPDSS: fix dss_init_ports error handling · f5a1a1f8
      Tomi Valkeinen 提交于
      The return value of dss_init_ports() is not handled at all, causing
      crashes later if the call failed.
      
      This patch adds the error handling, and we also move the call to a
      slightly earlier place to make bailing out easier.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      f5a1a1f8
    • T
      OMAPDSS: refactor dss probe function · 7e328f5a
      Tomi Valkeinen 提交于
      Refactor dss probe function by extracting the setup for video plls into
      a separate function. The call to this function is also moved to a
      slightly earlier phase, so that in error case we can bail out more
      easily.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      7e328f5a
    • T
      OMAPDSS: move 'dss_initialized' to dss driver · f99467b3
      Tomi Valkeinen 提交于
      We have a flag, 'dss_initialized', which tells omapfb and omapdrm if
      omapdss is available. At the moment it can be set even if the dss
      submodules are not all ready, in case something gets deferred.
      
      Move the flag to dss_core driver so that it'll signal the availability
      of the dss drivers move accurately.
      
      For now, it'll signal that dss_core is ready, which is not quite correct
      but still better than previously.  The following patches will add
      component system to omapdss, and after those patches 'dss_initialized'
      will signal that all the submodules are ready.
      Signed-off-by: NTomi Valkeinen <tomi.valkeinen@ti.com>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      f99467b3
  13. 20 4月, 2015 1 次提交
  14. 04 2月, 2015 4 次提交
  15. 12 11月, 2014 2 次提交