[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ftd6mi3e.fsf@intel.com>
Date: Tue, 14 Apr 2020 14:17:57 +0300
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Simon Ser <contact@...rsion.fr>, Yussuf Khalil <dev@...345.net>
Cc: Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...ux.ie>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"dri-devel\@lists.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: [PATCH 5/5] drm/i915: Replace "Broadcast RGB" with "RGB quantization range" property
On Mon, 13 Apr 2020, Simon Ser <contact@...rsion.fr> wrote:
> On Monday, April 13, 2020 11:40 PM, Yussuf Khalil <dev@...345.net> wrote:
>
>> DRM now has a globally available "RGB quantization range" connector
>> property. i915's "Broadcast RGB" that fulfils the same purpose is now
>> considered deprecated, so drop it in favor of the DRM property.
>
> For a UAPI point-of-view, I'm not sure this is fine. Some user-space
> might depend on this property, dropping it would break such user-space.
Agreed.
> Can we make this property deprecated but still keep it for backwards
> compatibility?
Would be nice to make the i915 specific property an "alias" for the new
property, however I'm not sure how you'd make that happen. Otherwise
juggling between the two properties is going to be a nightmare.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
Powered by blists - more mailing lists