1. 07 1月, 2021 1 次提交
  2. 24 12月, 2020 3 次提交
  3. 17 12月, 2020 1 次提交
  4. 16 12月, 2020 2 次提交
  5. 11 12月, 2020 2 次提交
  6. 09 12月, 2020 9 次提交
  7. 03 12月, 2020 3 次提交
  8. 02 12月, 2020 7 次提交
  9. 25 11月, 2020 6 次提交
  10. 20 11月, 2020 1 次提交
    • M
      drm: Pass the full state to connectors atomic functions · eca22edb
      Maxime Ripard 提交于
      The current atomic helpers have either their object state being passed as
      an argument or the full atomic state.
      
      The former is the pattern that was done at first, before switching to the
      latter for new hooks or when it was needed.
      
      Now that the CRTCs have been converted, let's move forward with the
      connectors to provide a consistent interface.
      
      The conversion was done using the coccinelle script below, and built tested
      on all the drivers.
      
      @@
      identifier connector, connector_state;
      @@
      
       struct drm_connector_helper_funcs {
      	...
      	struct drm_encoder* (*atomic_best_encoder)(struct drm_connector *connector,
      -						   struct drm_connector_state *connector_state);
      +						   struct drm_atomic_state *state);
      	...
      }
      
      @@
      identifier connector, connector_state;
      @@
      
       struct drm_connector_helper_funcs {
      	...
      	void (*atomic_commit)(struct drm_connector *connector,
      -			      struct drm_connector_state *connector_state);
      +			      struct drm_atomic_state *state);
      	...
      }
      
      @@
      struct drm_connector_helper_funcs *FUNCS;
      identifier state;
      identifier connector, connector_state;
      identifier f;
      @@
      
       f(..., struct drm_atomic_state *state, ...)
       {
      	<+...
      -	FUNCS->atomic_commit(connector, connector_state);
      +	FUNCS->atomic_commit(connector, state);
      	...+>
       }
      
      @@
      struct drm_connector_helper_funcs *FUNCS;
      identifier state;
      identifier connector, connector_state;
      identifier var, f;
      @@
      
       f(struct drm_atomic_state *state, ...)
       {
      	<+...
      -	var = FUNCS->atomic_best_encoder(connector, connector_state);
      +	var = FUNCS->atomic_best_encoder(connector, state);
      	...+>
       }
      
      @ connector_atomic_func @
      identifier helpers;
      identifier func;
      @@
      
      (
      static struct drm_connector_helper_funcs helpers = {
      	...,
      	.atomic_best_encoder = func,
      	...,
      };
      |
      static struct drm_connector_helper_funcs helpers = {
      	...,
      	.atomic_commit = func,
      	...,
      };
      )
      
      @@
      identifier connector_atomic_func.func;
      identifier connector;
      symbol state;
      @@
      
       func(struct drm_connector *connector,
      -      struct drm_connector_state *state
      +      struct drm_connector_state *connector_state
            )
       {
      	...
      -	state
      +	connector_state
       	...
       }
      
      @ ignores_state @
      identifier connector_atomic_func.func;
      identifier connector, connector_state;
      @@
      
       func(struct drm_connector *connector,
            struct drm_connector_state *connector_state)
      {
      	... when != connector_state
      }
      
      @ adds_state depends on connector_atomic_func && !ignores_state @
      identifier connector_atomic_func.func;
      identifier connector, connector_state;
      @@
      
       func(struct drm_connector *connector, struct drm_connector_state *connector_state)
       {
      +	struct drm_connector_state *connector_state = drm_atomic_get_new_connector_state(state, connector);
      	...
       }
      
      @ depends on connector_atomic_func @
      identifier connector_atomic_func.func;
      identifier connector_state;
      identifier connector;
      @@
      
       func(struct drm_connector *connector,
      -     struct drm_connector_state *connector_state
      +     struct drm_atomic_state *state
      	   )
       { ... }
      
      @ include depends on adds_state @
      @@
      
       #include <drm/drm_atomic.h>
      
      @ no_include depends on !include && adds_state @
      @@
      
      + #include <drm/drm_atomic.h>
        #include <drm/...>
      Signed-off-by: NMaxime Ripard <maxime@cerno.tech>
      Reviewed-by: NRodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
      Reviewed-by: NVille Syrjälä <ville.syrjala@linux.intel.com>
      Acked-by: NThomas Zimmermann <tzimmermann@suse.de>
      Acked-by: NHarry Wentland <harry.wentland@amd.com>
      Cc: Leo Li <sunpeng.li@amd.com>
      Cc: Alex Deucher <alexander.deucher@amd.com>
      Cc: "Christian König" <christian.koenig@amd.com>
      Cc: Jani Nikula <jani.nikula@linux.intel.com>
      Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
      Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
      Cc: Ben Skeggs <bskeggs@redhat.com>
      Cc: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
      Cc: Melissa Wen <melissa.srw@gmail.com>
      Cc: Haneen Mohammed <hamohammed.sa@gmail.com>
      Link: https://patchwork.freedesktop.org/patch/msgid/20201118094758.506730-1-maxime@cerno.tech
      eca22edb
  11. 19 11月, 2020 4 次提交
    • R
      drm/amd/display: Always get CRTC updated constant values inside commit tail · 2b3af270
      Rodrigo Siqueira 提交于
      We recently improved our display atomic commit and tail sequence to
      avoid some issues related to concurrency. One of the major changes
      consisted of moving the interrupt disable and the stream release from
      our atomic commit to our atomic tail (commit 6d90a208
      ("drm/amd/display: Move disable interrupt into commit tail")) .
      However, the new code introduced inside our commit tail function was
      inserted right after the function
      drm_atomic_helper_update_legacy_modeset_state(), which has routines for
      updating internal data structs related to timestamps. As a result, in
      certain conditions, the display module can reach a situation where we
      update our constants and, after that, clean it. This situation generates
      the following warning:
      
       amdgpu 0000:03:00.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev))
       WARNING: CPU: 6 PID: 1269 at drivers/gpu/drm/drm_vblank.c:722
       drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x32b/0x340 [drm]
       ...
       RIP:
       0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x32b/0x340
       [drm]
       ...
       Call Trace:
        ? dc_stream_get_vblank_counter+0x57/0x60 [amdgpu]
        drm_crtc_vblank_helper_get_vblank_timestamp+0x1c/0x20 [drm]
        drm_get_last_vbltimestamp+0xad/0xc0 [drm]
        drm_reset_vblank_timestamp+0x63/0xd0 [drm]
        drm_crtc_vblank_on+0x85/0x150 [drm]
        amdgpu_dm_atomic_commit_tail+0xaf1/0x2330 [amdgpu]
        commit_tail+0x99/0x130 [drm_kms_helper]
        drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
        amdgpu_dm_atomic_commit+0x11/0x20 [amdgpu]
        drm_atomic_commit+0x4a/0x50 [drm]
        drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper]
        drm_mode_setcrtc+0x20b/0x7e0 [drm]
        ? tomoyo_path_number_perm+0x6f/0x200
        ? drm_mode_getcrtc+0x190/0x190 [drm]
        drm_ioctl_kernel+0xae/0xf0 [drm]
        drm_ioctl+0x245/0x400 [drm]
        ? drm_mode_getcrtc+0x190/0x190 [drm]
        amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
        __x64_sys_ioctl+0x91/0xc0
        do_syscall_64+0x38/0x90
        entry_SYSCALL_64_after_hwframe+0x44/0xa9
       ...
      
      For fixing this issue we rely upon a refactor introduced on
      drm_atomic_helper_update_legacy_modeset_state ("Remove the timestamping
      constant update from drm_atomic_helper_update_legacy_modeset_state()")
      which decouples constant values update from
      drm_atomic_helper_update_legacy_modeset_state to a new helper.
      Basically, this commit uses this new helper and place it right after our
      release module to avoid a situation where our CRTC struct gets wrong
      values.
      
      Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1373
      Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1349Reviewed-by: NHarry Wentland <harry.wentland@amd.com>
      Signed-off-by: NRodrigo Siqueira <Rodrigo.Siqueira@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      2b3af270
    • B
      drm/amd/display: Add comments to hdcp property change code · 31c0ed90
      Bhawanpreet Lakha 提交于
      [Why]
      These comments are helpful in understanding which case each if
      statement handles.
      
      [How]
      Add comments for state transitions (9 possible cases)
      Signed-off-by: NBhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
      Reviewed-by: NZhan Liu <zhan.liu@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      31c0ed90
    • B
      drm/amd/display: Add display only once. · 97f6c917
      Bhawanpreet Lakha 提交于
      [Why]
      We call add display multiple times because DESIRED->ENABLED cannot
      happen instantaneously. We can't compare the new_state/old_state to
      avoid this because on unplug we set the state to DESIRED and on hotplug
      the state will still be DESIRED.
      
      [How]
      Add a flag to dm_connector_state to keep track of when to enable or
      disable HDCP
      Signed-off-by: NBhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
      Reviewed-by: NZhan Liu <zhan.liu@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      97f6c917
    • R
      drm/amd/display: Always get CRTC updated constant values inside commit tail · 8976f73b
      Rodrigo Siqueira 提交于
      We recently improved our display atomic commit and tail sequence to
      avoid some issues related to concurrency. One of the major changes
      consisted of moving the interrupt disable and the stream release from
      our atomic commit to our atomic tail (commit 6d90a208
      ("drm/amd/display: Move disable interrupt into commit tail")) .
      However, the new code introduced inside our commit tail function was
      inserted right after the function
      drm_atomic_helper_update_legacy_modeset_state(), which has routines for
      updating internal data structs related to timestamps. As a result, in
      certain conditions, the display module can reach a situation where we
      update our constants and, after that, clean it. This situation generates
      the following warning:
      
       amdgpu 0000:03:00.0: drm_WARN_ON_ONCE(drm_drv_uses_atomic_modeset(dev))
       WARNING: CPU: 6 PID: 1269 at drivers/gpu/drm/drm_vblank.c:722
       drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x32b/0x340 [drm]
       ...
       RIP:
       0010:drm_crtc_vblank_helper_get_vblank_timestamp_internal+0x32b/0x340
       [drm]
       ...
       Call Trace:
        ? dc_stream_get_vblank_counter+0x57/0x60 [amdgpu]
        drm_crtc_vblank_helper_get_vblank_timestamp+0x1c/0x20 [drm]
        drm_get_last_vbltimestamp+0xad/0xc0 [drm]
        drm_reset_vblank_timestamp+0x63/0xd0 [drm]
        drm_crtc_vblank_on+0x85/0x150 [drm]
        amdgpu_dm_atomic_commit_tail+0xaf1/0x2330 [amdgpu]
        commit_tail+0x99/0x130 [drm_kms_helper]
        drm_atomic_helper_commit+0x123/0x150 [drm_kms_helper]
        amdgpu_dm_atomic_commit+0x11/0x20 [amdgpu]
        drm_atomic_commit+0x4a/0x50 [drm]
        drm_atomic_helper_set_config+0x7c/0xc0 [drm_kms_helper]
        drm_mode_setcrtc+0x20b/0x7e0 [drm]
        ? tomoyo_path_number_perm+0x6f/0x200
        ? drm_mode_getcrtc+0x190/0x190 [drm]
        drm_ioctl_kernel+0xae/0xf0 [drm]
        drm_ioctl+0x245/0x400 [drm]
        ? drm_mode_getcrtc+0x190/0x190 [drm]
        amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
        __x64_sys_ioctl+0x91/0xc0
        do_syscall_64+0x38/0x90
        entry_SYSCALL_64_after_hwframe+0x44/0xa9
       ...
      
      For fixing this issue we rely upon a refactor introduced on
      drm_atomic_helper_update_legacy_modeset_state ("Remove the timestamping
      constant update from drm_atomic_helper_update_legacy_modeset_state()")
      which decouples constant values update from
      drm_atomic_helper_update_legacy_modeset_state to a new helper.
      Basically, this commit uses this new helper and place it right after our
      release module to avoid a situation where our CRTC struct gets wrong
      values.
      
      Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1373Reviewed-by: NHarry Wentland <harry.wentland@amd.com>
      Signed-off-by: NRodrigo Siqueira <Rodrigo.Siqueira@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      8976f73b
  12. 17 11月, 2020 1 次提交