1. 23 Sep, 2016 1 commit
  2. 22 Sep, 2016 4 commits
    • Jyri Sarha's avatar
      drm/tilcdc: Remove "default" from blue-and-red-wiring property binding · 34355ee0
      Jyri Sarha authored
      Remove "default" keyword from blue-and-red-wiring devicetree property
      binding document. The code does not support and there is no intention
      to support it.
      Reported-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarJyri Sarha <jsarha@ti.com>
      34355ee0
    • Wei Yongjun's avatar
      drm/tilcdc: Fix non static symbol warning · 30457676
      Wei Yongjun authored
      Fixes the following sparse warning:
      
      drivers/gpu/drm/tilcdc/tilcdc_drv.c:64:5: warning:
       symbol 'tilcdc_atomic_check' was not declared. Should it be static?
      Signed-off-by: default avatarWei Yongjun <weiyongjun1@huawei.com>
      Signed-off-by: default avatarJyri Sarha <jsarha@ti.com>
      30457676
    • Baoyou Xie's avatar
      drm/tilcdc: mark symbols static where possible · 952e8fae
      Baoyou Xie authored
      We get 3 warnings when building kernel with W=1:
      drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c:142:29: warning: no previous prototype for 'tilcdc_get_overlay' [-Wmissing-prototypes]
      drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c:198:13: warning: no previous prototype for 'tilcdc_convert_slave_node' [-Wmissing-prototypes]
      drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c:264:12: warning: no previous prototype for 'tilcdc_slave_compat_init' [-Wmissing-prototypes]
      
      In fact, these functions are only used in the file in which they are
      declared and don't need a declaration, but can be made static.
      So this patch marks these functions with 'static'.
      Signed-off-by: default avatarBaoyou Xie <baoyou.xie@linaro.org>
      Signed-off-by: default avatarJyri Sarha <jsarha@ti.com>
      952e8fae
    • Baoyou Xie's avatar
      drm/tilcdc: add missing header dependencies · 0fd86779
      Baoyou Xie authored
      We get 4 warnings when building kernel with W=1:
      drivers/gpu/drm/tilcdc/tilcdc_tfp410.c:393:12: warning: no previous prototype for 'tilcdc_tfp410_init' [-Wmissing-prototypes]
      drivers/gpu/drm/tilcdc/tilcdc_tfp410.c:398:13: warning: no previous prototype for 'tilcdc_tfp410_fini' [-Wmissing-prototypes]
      drivers/gpu/drm/tilcdc/tilcdc_panel.c:443:12: warning: no previous prototype for 'tilcdc_panel_init' [-Wmissing-prototypes]
      drivers/gpu/drm/tilcdc/tilcdc_panel.c:448:13: warning: no previous prototype for 'tilcdc_panel_fini' [-Wmissing-prototypes]
      
      In fact, these functions are declared in
      drivers/gpu/drm/tilcdc/tilcdc_tfp410.h,
      drivers/gpu/drm/tilcdc/tilcdc_panel.h,
      so this patch adds missing header dependencies.
      Signed-off-by: default avatarBaoyou Xie <baoyou.xie@linaro.org>
      Signed-off-by: default avatarJyri Sarha <jsarha@ti.com>
      0fd86779
  3. 07 Sep, 2016 6 commits
  4. 01 Sep, 2016 7 commits
  5. 31 Aug, 2016 3 commits
    • Dave Airlie's avatar
      Revert "drm: make DRI1 drivers depend on BROKEN" · 2b2fd56d
      Dave Airlie authored
      This reverts commit d10571fc.
      
      This isn't how we get to do this unfortunately.
      Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
      2b2fd56d
    • Dave Airlie's avatar
      Merge tag 'topic/drm-misc-2016-08-31' of git://anongit.freedesktop.org/drm-intel into drm-next · 5e7a1d01
      Dave Airlie authored
      More -misc stuff
      - moar drm_crtc.c split up&documentation
      - some fixes for the simple kms helpers (Andrea)
      - I included all the dri1 patches from David - we're not removing any code
        or drivers, and it seems to have worked as a wake-up call to motivate a
        few more people to upstream kms conversions for these. Feel free to
        revert if you disagree strongly.
      - a few other single patches
      
      * tag 'topic/drm-misc-2016-08-31' of git://anongit.freedesktop.org/drm-intel: (24 commits)
        drm: drm_probe_helper: Fix output_poll_work scheduling
        drm: bridge/dw-hdmi: Fix colorspace and scan information registers values
        drm/doc: Polish docs for drm_property&drm_property_blob
        drm: Unify handling of blob and object properties
        drm: Extract drm_property.[hc]
        drm: move drm_mode_legacy_fb_format to drm_fourcc.c
        drm/doc: Polish docs for drm_mode_object
        drm: Remove drm_mode_object->atomic_count
        drm: Extract drm_mode_object.[hc]
        drm/doc: Polish kerneldoc for encoders
        drm: Extract drm_encoder.[hc]
        drm/fb-helper: don't call remove_conflicting_framebuffers for FB=m && DRM=y
        drm/atomic-helper: Add NO_DISABLE_AFTER_MODESET flag support for plane commit
        drm/atomic-helper: Disable appropriate planes in disable_planes_on_crtc()
        drm/atomic-helper: Add atomic_disable CRTC helper callback
        drm: simple_kms_helper: add support for bridges
        drm: simple_kms_helper: make connector optional at init time
        drm/bridge: introduce bridge detaching mechanism
        drm/simple-helpers: Always add planes to the state update
        drm: reduce GETCLIENT to a minimum
        ...
      5e7a1d01
    • Peter Ujfalusi's avatar
      drm: drm_probe_helper: Fix output_poll_work scheduling · 339fd362
      Peter Ujfalusi authored
      drm_kms_helper_poll_enable_locked() should check if we have delayed event
      pending and if we have, schedule the work to run without delay.
      
      Currently the output_poll_work is only scheduled if any of the connectors
      have DRM_CONNECTOR_POLL_CONNECT or DRM_CONNECTOR_POLL_DISCONNECT with
      DRM_OUTPUT_POLL_PERIOD delay. It does not matter if we have delayed event
      already registered to be handled. The detection will be delayd by
      DRM_OUTPUT_POLL_PERIOD in any case.
      Furthermore if none of the connectors are marked as POLL_CONNECT or
      POLL_DISCONNECT because all connectors are either POLL_HPD or they are
      always connected: the output_poll_work will not run at all even if we
      have delayed event marked.
      
      When none of the connectors require polling, their initial status change
      from unknown to connected/disconnected is not going to be handled until
      the first kms application starts or if we have fb console enabled.
      
      Note that in general the output poll work should be enabled already
      when this happens, but at driver load usually the first probe happens
      before the output polling is enabled. This patch fixes this case.
      Signed-off-by: default avatarPeter Ujfalusi <peter.ujfalusi@ti.com>
      [danvet: Note when exactly this is an issue, since the probe code
      schedules the poll work itself already.]
      Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
      Link: http://patchwork.freedesktop.org/patch/msgid/20160831110905.31289-1-peter.ujfalusi@ti.com
      339fd362
  6. 30 Aug, 2016 1 commit
  7. 29 Aug, 2016 16 commits
  8. 25 Aug, 2016 2 commits