diff options
| author | Imre Deak <imre.deak@intel.com> | 2019-08-08 17:02:05 +0300 |
|---|---|---|
| committer | Imre Deak <imre.deak@intel.com> | 2019-08-20 17:19:23 +0300 |
| commit | 357dbe1869d88a2f08bcee4eebceff4ee9014424 (patch) | |
| tree | 98d3906ea3d839f9127f78368a3ea8efd765663e /tests/kms_properties.c | |
| parent | 50251bcb2e8783f86ebdd86ce38adc9e3777f82f (diff) | |
tests/kms_properties: Fix upper bound of 'max bpc' range
The available range reported by the driver is the inclusive [min_bpc,
max_bpc], so fix the upper bound used by the test accordingly. This
issue had the side-effect (on ICL for instance) of limiting 'max bpc' to
10 (instead of restoring it to the default 12) for all the tests
following kms_properties, as seen from the logs in the referenced bug
below.
Reference: https://bugs.freedesktop.org/show_bug.cgi?id=109593
Cc: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Simon Ser <simon.ser@intel.com>
Diffstat (limited to 'tests/kms_properties.c')
| -rw-r--r-- | tests/kms_properties.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/kms_properties.c b/tests/kms_properties.c index eb9cbdda..18cf96e0 100644 --- a/tests/kms_properties.c +++ b/tests/kms_properties.c @@ -91,7 +91,7 @@ static void max_bpc_prop_test(int fd, uint32_t id, uint32_t type, drmModePropert if (atomic) req = drmModeAtomicAlloc(); - for ( i = prop->values[0]; i < prop->values[1] ; i++) { + for (i = prop->values[0]; i <= prop->values[1]; i++) { if (!atomic) { ret = drmModeObjectSetProperty(fd, id, type, prop_id, i); |