diff options
| author | Bhanuprakash Modem <bhanuprakash.modem@intel.com> | 2022-05-31 17:28:04 +0530 |
|---|---|---|
| committer | Bhanuprakash Modem <bhanuprakash.modem@intel.com> | 2022-06-01 16:08:09 +0530 |
| commit | 41a36942082da9b86197179270e904a08c8441b5 (patch) | |
| tree | 5aab94e8817c4a7b9059371c63bb999130410c46 /lib/amdgpu/amd_command_submission.c | |
| parent | 8c1fdd9bb2fc0a964dce72bbc43fe1f463374786 (diff) | |
tests/kms_hdr: Skip if current & requested BPC doesn't match
The "max bpc" property only ensures that the bpc will not go beyond
the value set through this property. It does not guarantee that the
same bpc will be used for the given mode.
If clock/bandwidth constraints permit, the max bpc will be used to
show the mode, otherwise the bpc will be reduced. So, if we really
want a particular bpc set, we can try reducing the resolution, till
we get the bpc that we set in max bpc property.
This patch will skip the test, if there is no valid resolution to get
the same bpc as set by max_bpc property.
V2:
* Refactor the logic
V3:
* Minor changes
V4:
* Drop 4K restriction check
Cc: Swati Sharma <swati2.sharma@intel.com>
CC: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem@intel.com>
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
Diffstat (limited to 'lib/amdgpu/amd_command_submission.c')
0 files changed, 0 insertions, 0 deletions