1. 05 1月, 2015 1 次提交
    • R
      drm: add atomic properties · 88a48e29
      Rob Clark 提交于
      Once a driver is using atomic helpers for modeset, the next step is to
      switch over to atomic properties.  To do this, make sure that any
      modeset objects have their ->atomic_{get,set}_property() vfuncs suitably
      populated if they have custom properties (you did already remember to
      plug in atomic-helper func for the legacy ->set_property() vfuncs,
      right?), and then set DRIVER_ATOMIC bit in driver_features flag.
      
      A new cap is introduced, DRM_CLIENT_CAP_ATOMIC, for the purposes of
      shielding legacy userspace from atomic properties.  Mostly for the
      benefit of legacy DDX drivers that do silly things like getting/setting
      each property at startup (since some of the new atomic properties will
      be able to trigger modeset).
      Signed-off-by: NRob Clark <robdclark@gmail.com>
      [danvet: Squash in fixup patch to check for DRM_MODE_PROP_ATOMIC
      instaed of the CAP define when filtering properties. Reported by
      Tvrtko Uruslin, acked by Rob.]
      Signed-off-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
      88a48e29
  2. 18 12月, 2014 1 次提交
  3. 17 12月, 2014 3 次提交
  4. 27 11月, 2014 1 次提交
  5. 13 11月, 2014 2 次提交
  6. 13 10月, 2014 1 次提交
  7. 30 9月, 2014 1 次提交
  8. 24 9月, 2014 6 次提交
  9. 12 9月, 2014 16 次提交
  10. 11 9月, 2014 2 次提交
  11. 10 9月, 2014 6 次提交