Lines Matching refs:LUT

14510   *	pixel data after the lookup through the degamma LUT and before the
14511 - *	lookup through the gamma LUT. The data is interpreted as a struct
14512 + *	lookup through the cubic LUT. The data is interpreted as a struct
14523 + *	the gamma LUT. Unlike the degamma and gamma LUTs that map color
14524 + *	components independently, the 3D LUT converts an input color to an
14526 + *	as a 3D coordinate. The LUT is subsampled as 8-bit (or more) precision
14533 + *	Hardware might choose not to use the full precision of the LUT
14544 + *	If drivers support multiple LUT sizes then they should publish the
14548   *	Blob property to set the gamma lookup table (LUT) mapping pixel data
14551 - *	Hardware might choose not to use the full precision of the LUT elements
14552 - *	nor use all the elements of the LUT (for example the hardware might
14553 - *	choose to interpolate between LUT[0] and LUT[4]).
14554 + *	after the cubic LUT to data sent to the connector. The data is
14556 + *	might choose not to use the full precision of the LUT elements nor use
14557 + *	all the elements of the LUT (for example the hardware might choose to
14558 + *	interpolate between LUT[0] and LUT[4]).
16584 +	bool "Support 3D cubic LUT"
29375 -	 * an update to the LUT, clear dsp_lut_en.
29383 -	 * In order to write the LUT to the internal memory,
29396 -		DRM_DEV_ERROR(vop->dev, "display LUT RAM enable timeout!\n");
29538 -	 * If we have a GAMMA LUT in the state, then let's make sure
29540 -	 * which means the LUT internal memory needs to be re-written.
29696 -			DRM_DEBUG_KMS("Invalid LUT size; got %d, expected %d\n",
30860 -			DRM_DEV_ERROR(dev, "no gamma LUT size defined\n");