Load and apply a vcgt table from an ICC file to the internal display

ui/ozone/common/gpu/ozone_gpu_messages.h

Index: ui/ozone/common/gpu/ozone_gpu_messages.h
diff --git a/ui/ozone/common/gpu/ozone_gpu_messages.h b/ui/ozone/common/gpu/ozone_gpu_messages.h
index 14d2a10761e11063e18921471765292c37023570..0b568d2d1704f85516cedafe28b40df019f3085c 100644
--- a/ui/ozone/common/gpu/ozone_gpu_messages.h
+++ b/ui/ozone/common/gpu/ozone_gpu_messages.h
@@ -102,6 +102,13 @@ IPC_MESSAGE_CONTROL0(OzoneGpuMsg_TakeDisplayControl)
 // Let other entity control the display
 IPC_MESSAGE_CONTROL0(OzoneGpuMsg_RelinquishDisplayControl)
 
+// Provides the gamma ramp for display adjustment.
+IPC_MESSAGE_CONTROL4(OzoneGpuMsg_SetGammaRamp,
+                     int64_t,                // display ID,
+                     std::vector<uint16_t>,  // r
+                     std::vector<uint16_t>,  // g,
+                     std::vector<uint16_t>)  // b

[dcheng, 2015/04/28 18:45:34]

From a security perspective, I'd be happier if we sent this as a vector of RGB
triples, rather than having the IPC handler verify that r.size() == g.size() ==
b.size(). This does require repacking the data to pass to the system later, but
I don't think this is perf sensitive, is it?

[robert.bradford, 2015/04/29 13:40:14]

dcheng@ please see updated patch. I combine and split the data either side of
the IPC. Is this what you were thinking about?

I had to add a typedef to get IPC macros to accept the nested templated types in
ozone_gpu_messages.h and used the same type name in all the places this vector
of tuples is used.

Let me know what you think.

On 2015/04/28 18:45:34, dcheng wrote:

+
 //------------------------------------------------------------------------------
 // Browser Messages
 // These messages are from the GPU to the browser process.