[PATCH V10 40/46] drm/colorop: Define LUT_1D interpolation

[Xaver Hugl]

> It would become mutable only for hardware that supports switching the
> interpolation. It would remain immutable otherwise.
Please let's avoid making (more) properties *sometimes* immutable, it
just makes it easier to use KMS wrong, with no benefits to it.
If a compositor is written against a driver/hardware where it's
mutable, it's easy to assume that the property would always be
mutable, but that same code will not work on setups where it's
immutable - as the kernel (atm even silently, without a warning!)
rejects every commit touching immutable properties, even if you set it
to the one supported value.

A property should imo only be immutable if it's truly meant to be a
read-only API (forever), like with immutable property blobs or plane
types.