kernel_5.10 no rt

hc

2023-12-11 6778948f9de86c3cfaf36725a7c87dcff9ba247f

 kernel/drivers/gpu/drm/drm_color_mgmt.c
..
..
@@ -33,7 +33,7 @@
33
33
 /**
34
34
  * DOC: overview
35
35
  *
36
- * Color management or color space adjustments is supported through a set of 7
36
+ * Color management or color space adjustments is supported through a set of 5
37
37
  * properties on the &drm_crtc object. They are set up by calling
38
38
  * drm_crtc_enable_color_mgmt().
39
39
  *
..
..
@@ -60,7 +60,7 @@
60
60
  * “CTM”:
61
61
  *	Blob property to set the current transformation matrix (CTM) apply to
62
62
  *	pixel data after the lookup through the degamma LUT and before the
63
- *	lookup through the cubic LUT. The data is interpreted as a struct
63
+ *	lookup through the gamma LUT. The data is interpreted as a struct
64
64
  *	&drm_color_ctm.
65
65
  *
66
66
  *	Setting this to NULL (blob property value set to 0) means a
..
..
@@ -68,40 +68,13 @@
68
68
  *	boot-up state too. Drivers can access the blob for the color conversion
69
69
  *	matrix through &drm_crtc_state.ctm.
70
70
  *
71
- * ”CUBIC_LUT”:
72
- *	Blob property to set the cubic (3D) lookup table performing color
73
- *	mapping after the transformation matrix and before the lookup through
74
- *	the gamma LUT. Unlike the degamma and gamma LUTs that map color
75
- *	components independently, the 3D LUT converts an input color to an
76
- *	output color by indexing into the 3D table using the color components
77
- *	as a 3D coordinate. The LUT is subsampled as 8-bit (or more) precision
78
- *	would require too much storage space in the hardware, so the precision
79
- *	of the color components is reduced before the look up, and the low
80
- *	order bits may be used to interpolate between the nearest points in 3D
81
- *	space.
82
- *
83
- *	The data is interpreted as an array of &struct drm_color_lut elements.
84
- *	Hardware might choose not to use the full precision of the LUT
85
- *	elements.
86
- *
87
- *	Setting this to NULL (blob property value set to 0) means the output
88
- *	color is identical to the input color. This is generally the driver
89
- *	boot-up state too. Drivers can access this blob through
90
- *	&drm_crtc_state.cubic_lut.
91
- *
92
- * ”CUBIC_LUT_SIZE”:
93
- *	Unsigned range property to give the size of the lookup table to be set
94
- *	on the CUBIC_LUT property (the size depends on the underlying hardware).
95
- *	If drivers support multiple LUT sizes then they should publish the
96
- *	largest size, and sub-sample smaller sized LUTs appropriately.
97
- *
98
71
  * “GAMMA_LUT”:
99
72
  *	Blob property to set the gamma lookup table (LUT) mapping pixel data
100
- *	after the cubic LUT to data sent to the connector. The data is
101
- *	interpreted as an array of &struct drm_color_lut elements. Hardware
102
- *	might choose not to use the full precision of the LUT elements nor use
103
- *	all the elements of the LUT (for example the hardware might choose to
104
- *	interpolate between LUT[0] and LUT[4]).
73
+ *	after the transformation matrix to data sent to the connector. The
74
+ *	data is interpreted as an array of &struct drm_color_lut elements.
75
+ *	Hardware might choose not to use the full precision of the LUT elements
76
+ *	nor use all the elements of the LUT (for example the hardware might
77
+ *	choose to interpolate between LUT[0] and LUT[4]).
105
78
  *
106
79
  *	Setting this to NULL (blob property value set to 0) means a
107
80
  *	linear/pass-thru gamma table should be used. This is generally the