1. 08 6月, 2019 1 次提交
  2. 18 3月, 2019 2 次提交
  3. 08 2月, 2019 3 次提交
  4. 24 1月, 2019 1 次提交
  5. 14 1月, 2019 2 次提交
  6. 29 11月, 2018 1 次提交
  7. 23 11月, 2018 1 次提交
  8. 25 9月, 2018 1 次提交
    • L
      drm: rcar-du: Enable configurable DPAD0 routing on Gen3 · 1f98b2a4
      Laurent Pinchart 提交于
      All Gen3 SoCs supported so far have a fixed association between DPAD0
      and DU channels, which led to hardcoding that association when writing
      the corresponding hardware register. The D3 and E3 will break that
      mechanism as DPAD0 can be dynamically connected to either DU0 or DU1.
      
      Make DPAD0 routing dynamic on Gen3. To ensure a valid hardware
      configuration when the DU starts without the RGB output enabled, DPAD0
      is associated at initialization time to the first DU channel that it can
      be connected to. This makes no change on Gen2 as all Gen2 SoCs can
      connected DPAD0 to DU0, which is the current implicit default value.
      
      As the DPAD0 source is always 0 when a single source is possible on
      Gen2, we can also simplify the Gen2 code in the same function to remove
      a conditional check.
      Signed-off-by: NLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
      Tested-by: NJacopo Mondi <jacopo+renesas@jmondi.org>
      Reviewed-by: NJacopo Mondi <jacopo+renesas@jmondi.org>
      1f98b2a4
  9. 15 9月, 2018 3 次提交
  10. 14 9月, 2018 1 次提交
  11. 05 5月, 2018 3 次提交
  12. 17 4月, 2018 1 次提交
  13. 28 3月, 2018 1 次提交
  14. 08 3月, 2018 1 次提交
  15. 01 10月, 2017 1 次提交
  16. 03 8月, 2017 5 次提交
  17. 26 7月, 2017 1 次提交
    • R
      drm: Convert to using %pOF instead of full_name · 4bf99144
      Rob Herring 提交于
      Now that we have a custom printf format specifier, convert users of
      full_name to use %pOF instead. This is preparation to remove storing
      of the full path string for each node.
      Signed-off-by: NRob Herring <robh@kernel.org>
      Cc: Russell King <linux@armlinux.org.uk>
      Cc: David Airlie <airlied@linux.ie>
      Cc: Daniel Vetter <daniel.vetter@intel.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Cc: Sean Paul <seanpaul@chromium.org>
      Cc: Inki Dae <inki.dae@samsung.com>
      Cc: Joonyoung Shim <jy0922.shim@samsung.com>
      Cc: Seung-Woo Kim <sw0312.kim@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Cc: Kukjin Kim <kgene@kernel.org>
      Cc: Krzysztof Kozlowski <krzk@kernel.org>
      Cc: Javier Martinez Canillas <javier@osg.samsung.com>
      Cc: Xinliang Liu <z.liuxinliang@hisilicon.com>
      Cc: Rongrong Zou <zourongrong@gmail.com>
      Cc: Xinwei Kong <kong.kongxinwei@hisilicon.com>
      Cc: Chen Feng <puck.chen@hisilicon.com>
      Cc: CK Hu <ck.hu@mediatek.com>
      Cc: Philipp Zabel <p.zabel@pengutronix.de>
      Cc: Matthias Brugger <matthias.bgg@gmail.com>
      Cc: Neil Armstrong <narmstrong@baylibre.com>
      Cc: Carlo Caione <carlo@caione.org>
      Cc: Kevin Hilman <khilman@baylibre.com>
      Cc: Thierry Reding <thierry.reding@gmail.com>
      Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
      Cc: Mark Yao <mark.yao@rock-chips.com>
      Cc: Heiko Stuebner <heiko@sntech.de>
      Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
      Cc: Chen-Yu Tsai <wens@csie.org>
      Cc: Jyri Sarha <jsarha@ti.com>
      Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
      Cc: dri-devel@lists.freedesktop.org
      Cc: linux-arm-kernel@lists.infradead.org
      Cc: linux-samsung-soc@vger.kernel.org
      Cc: linux-mediatek@lists.infradead.org
      Cc: linux-amlogic@lists.infradead.org
      Cc: linux-renesas-soc@vger.kernel.org
      Cc: linux-rockchip@lists.infradead.org
      Partially-Reviewed-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Reviewed-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Acked-by: NMaxime Ripard <maxime.ripard@free-electrons.com>
      [seanpaul changed subject prefix and fixed conflict in stm/ltdc.c]
      Signed-off-by: NSean Paul <seanpaul@chromium.org>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      4bf99144
  18. 04 4月, 2017 3 次提交
  19. 03 2月, 2017 1 次提交
    • G
      drm: Rely on mode_config data for fb_helper initialization · e4563f6b
      Gabriel Krisman Bertazi 提交于
      Instead of receiving the num_crts as a parameter, we can read it
      directly from the mode_config structure.  I audited the drivers that
      invoke this helper and I believe all of them initialize the mode_config
      struct accordingly, prior to calling the fb_helper.
      
      I used the following coccinelle hack to make this transformation, except
      for the function headers and comment updates.  The first and second
      rules are split because I couldn't find a way to remove the unused
      temporary variables at the same time I removed the parameter.
      
      // <smpl>
      @r@
      expression A,B,D,E;
      identifier C;
      @@
      (
      - drm_fb_helper_init(A,B,C,D)
      + drm_fb_helper_init(A,B,D)
      |
      - drm_fbdev_cma_init_with_funcs(A,B,C,D,E)
      + drm_fbdev_cma_init_with_funcs(A,B,D,E)
      |
      - drm_fbdev_cma_init(A,B,C,D)
      + drm_fbdev_cma_init(A,B,D)
      )
      
      @@
      expression A,B,C,D,E;
      @@
      (
      - drm_fb_helper_init(A,B,C,D)
      + drm_fb_helper_init(A,B,D)
      |
      - drm_fbdev_cma_init_with_funcs(A,B,C,D,E)
      + drm_fbdev_cma_init_with_funcs(A,B,D,E)
      |
      - drm_fbdev_cma_init(A,B,C,D)
      + drm_fbdev_cma_init(A,B,D)
      )
      
      @@
      identifier r.C;
      type T;
      expression V;
      @@
      - T C;
      <...
      when != C
      - C = V;
      ...>
      // </smpl>
      
      Changes since v1:
       - Rebased on top of the tip of drm-misc-next.
       - Remove mention to sti since a proper fix got merged.
      Suggested-by: NDaniel Vetter <daniel.vetter@intel.com>
      Signed-off-by: NGabriel Krisman Bertazi <krisman@collabora.co.uk>
      Reviewed-by: NEric Anholt <eric@anholt.net>
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      Link: http://patchwork.freedesktop.org/patch/msgid/20170202162640.27261-1-krisman@collabora.co.uk
      e4563f6b
  20. 15 11月, 2016 1 次提交
    • L
      drm: rcar-du: Simplify and fix probe error handling · 4f7b0d26
      Laurent Pinchart 提交于
      It isn't safe to call drm_dev_unregister() without first initializing
      mode setting with drm_mode_config_init(). This leads to a crash if
      either IO memory can't be remapped or vblank initialization fails.
      
      Fix this by reordering the initialization sequence. Move vblank
      initialization after the drm_mode_config_init() call, and move IO
      remapping before drm_dev_alloc() to avoid the need to perform clean up
      in case of failure.
      
      While at it remove the explicit drm_vblank_cleanup() call from
      rcar_du_remove() as the drm_dev_unregister() function already cleans up
      vblank.
      Signed-off-by: NLaurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
      4f7b0d26
  21. 14 11月, 2016 1 次提交
  22. 27 10月, 2016 1 次提交
  23. 17 10月, 2016 1 次提交
  24. 29 8月, 2016 1 次提交
  25. 29 7月, 2016 1 次提交
  26. 10 6月, 2016 1 次提交