Preliminary atomic patch

ui/ozone/platform/drm/gpu/drm_device.h

Index: ui/ozone/platform/drm/gpu/drm_device.h
diff --git a/ui/ozone/platform/drm/gpu/drm_device.h b/ui/ozone/platform/drm/gpu/drm_device.h
index 6ff19825e9492cfcc32d8e8e5cbcd15a67510d1b..7404a6a9429c36fc23b2ceda84bb0f924da40b1e 100644
--- a/ui/ozone/platform/drm/gpu/drm_device.h
+++ b/ui/ozone/platform/drm/gpu/drm_device.h
@@ -154,6 +154,10 @@ class OZONE_EXPORT DrmDevice : public base::RefCountedThreadSafe<DrmDevice> {
                                  uint32_t stride,
                                  void* pixels);
 
+  virtual bool CommitProperties(drmModePropertySet* properties,

[dnicoara, 2015/03/09 20:10:40]

This will need to be mocked in test/mock_drm_device.h

[achaulk, 2015/03/09 20:23:48]

Done.

+                                uint32_t flags,

[dnicoara, 2015/03/09 20:10:40]

|flags| and |user_ptr| are never set to different values. Can we just hide them
in the implementation and not pass them in?

[achaulk, 2015/03/09 20:23:48]

They will likely be set to handle some sort of callbacks later on, once that's
figured out

[dnicoara, 2015/03/09 20:42:58]

Are you planing on adding more functionality part of this patch?

If not, we should add these flags later. It would be nice to have |user_ptr| of
some specific type.

[achaulk, 2015/03/09 20:55:18]

Not yet, since we don't even have a complete definition yet, but I suspect flags
will specify what events we want and the user_ptr will just be a generic
callback pointer, but the actual mechanism is unknown for now

[dnicoara, 2015/03/09 20:57:26]

For the callback, we can do the same as SchedulePageFlip and provide a concrete
PageFlipCallback.

[achaulk, 2015/03/09 21:41:00]

Sure, I'll just reuse the same one until we know more about the implementation

+                                void* user_ptr);
+
   // Drm master related
   virtual bool SetMaster();
   virtual bool DropMaster();