mån 2019-04-15 klockan 19:26 +0530 skrev Sharma, Shashank: > > -----Original Message----- > > From: Lankhorst, Maarten > > Sent: Monday, April 15, 2019 4:28 PM > > To: Shankar, Uma <uma.shan...@intel.com>; intel-gfx@lists.freedeskt > > op.org; dri- > > de...@lists.freedesktop.org > > Cc: Syrjala, Ville <ville.syrj...@intel.com>; emil.l.velikov@gmail. > > com; > > s...@ravnborg.org; Roper, Matthew D <matthew.d.ro...@intel.com>; > > seanp...@chromium.org; brian.star...@arm.com; dcasta...@chromium.or > > g; > > Sharma, Shashank <shashank.sha...@intel.com> > > Subject: Re: [v3 6/7] drm: Add Client Cap for advance gamma mode > > > > fre 2019-04-12 klockan 15:51 +0530 skrev Uma Shankar: > > > Introduced a client cap for advance cap mode > > > capability. Userspace should set this to get > > > to be able to use the new gamma_mode property. > > > > > > If this is not set, driver will work in legacy > > > mode. > > > > > > Suggested-by: Ville Syrjälä <ville.syrj...@linux.intel.com> > > > Signed-off-by: Uma Shankar <uma.shan...@intel.com> > > > > Nack, this doesn't seem like a sensible idea. We already guard it > > behind the gamma mode property. Userspace shouldn't set the gamma > > mode > > to a value it doesn't understand. > > > > ~Maarten > > Hey Maarten, > In that case, what do you suggest should be the right way to do this > ? > > @Ville, any comments here ? > I would say drop this patch, and just enable segmented gamma unconditionally, it's not the first property that can cause trouble when not understood.
~Maarten
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
