1. 27 2月, 2021 1 次提交
    • A
      drm/amd/display: Add module parameter for freesync video mode · 0eb1af2e
      Aurabindo Pillai 提交于
      [Why]
      This option shall be opt-in by default since it is a temporary solution
      until long term solution is agreed upon which may require userspace interface
      changes. This feature give the user a seamless experience when freesync aware
      programs (media players for instance) switches to a compatible freesync mode
      when playing videos. Enabling this feature also have the potential side effect
      of causing higher power consumption due to running a mode with lower resolution
      and base clock frequency with the highest base clock supported on the monitor as
      per its advertised modes. There has been precedent of manufacturing modes in the
      kernel. In AMDGPU, the existing usage are for common modes and scaling modes.
      Other driver have a similar approach as well.
      
      [How]
      Adds a module parameter to enable freesync video mode modeset
      optimization. Enabling this mode allows the driver to skip a full modeset when a
      freesync compatible mode is requested by the userspace. This parameter will also
      add some additional modes that are within the connected monitor's VRR range
      corresponding to common video modes, which media players can use for a seamless
      experience while making use of freesync.
      Signed-off-by: NAurabindo Pillai <aurabindo.pillai@amd.com>
      Acked-by: NChristian König <christian.koenig@amd.com>
      Reviewed-by: NShashank Sharma <shashank.sharma@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      0eb1af2e
  2. 24 2月, 2021 1 次提交
  3. 19 2月, 2021 2 次提交
  4. 10 2月, 2021 3 次提交
  5. 06 1月, 2021 2 次提交
  6. 16 12月, 2020 3 次提交
  7. 02 12月, 2020 1 次提交
  8. 19 11月, 2020 1 次提交
  9. 14 11月, 2020 1 次提交
  10. 13 11月, 2020 2 次提交
  11. 27 10月, 2020 1 次提交
  12. 16 10月, 2020 1 次提交
  13. 08 10月, 2020 1 次提交
    • J
      drm/amdgpu: add per device user friendly xgmi events for vega20 · b4a7db71
      Jonathan Kim 提交于
      Non-outbound data metrics are non useful so mark them as legacy.
      Bucket new perf counters into device and not device ip.
      Bind events to chip instead of IP.
      Report available event counters and not number of hw counter banks.
      Move DF public macros to private since not needed outside of IP version.
      
      v5: cleanup by moving per chip configs into structs
      
      v4: After more discussion, replace *_LEGACY references with IP references
      to indicate concept of pmu-typed versus event-config-typed event
      registration.
      
      v3: attr groups const array is global but attr groups are allocated per
      device which doesn't work and causes problems on memory allocation and
      de-allocation for pmu unregister. Switch to building const attr groups
      per pmu instead to simplify solution.
      
      v2: add comments on sysfs structure and formatting.
      Signed-off-by: NJonathan Kim <jonathan.kim@amd.com>
      Reviewed-by: NHarish Kasiviswanathan <harish.kasiviswanathan@amd.com>
      Signed-off-by: NAlex Deucher <alexander.deucher@amd.com>
      b4a7db71
  14. 01 10月, 2020 3 次提交
  15. 16 9月, 2020 3 次提交
  16. 27 8月, 2020 3 次提交
  17. 25 8月, 2020 5 次提交
  18. 19 8月, 2020 1 次提交
  19. 15 8月, 2020 1 次提交
  20. 07 8月, 2020 1 次提交
  21. 05 8月, 2020 3 次提交