exo: Add Surface::SetBufferScale.

exo: Add Surface::SetBufferScale.

The buffer scale allow clients to supply higher resolution buffer
data for use on high resolution displays.

BUG=549781
TEST=exo_unittest --gtest_filter=SurfaceTest.SetBufferScale

Committed: https://crrev.com/7efa4b0e51409c538d7a05f6f315c51ae3c7f3b6
Cr-Commit-Position: refs/heads/master@{#367797}

[reveman, 2015-12-28 08:50:54]

reveman@chromium.org changed reviewers:
+ lpique@chromium.org

[lpique, 2016-01-04 19:36:20]

https://codereview.chromium.org/1548163002/diff/1/components/exo/surface.cc
File components/exo/surface.cc (right):

https://codereview.chromium.org/1548163002/diff/1/components/exo/surface.cc#n...
components/exo/surface.cc:289: 1.0f / pending_buffer_scale_));
The call to ScaleToFlooredSize() includes (as the name indicates) flooring to an
integer value.

Shouldn't this set a scale transform of "contents_size /
texture_mailbox.size_in_pixels()" so that the adjusted size is used to set the
scale?

[reveman, 2016-01-05 09:02:48]

https://codereview.chromium.org/1548163002/diff/1/components/exo/surface.cc
File components/exo/surface.cc (right):

https://codereview.chromium.org/1548163002/diff/1/components/exo/surface.cc#n...
components/exo/surface.cc:289: 1.0f / pending_buffer_scale_));
On 2016/01/04 at 19:36:20, lpique wrote:
> The call to ScaleToFlooredSize() includes (as the name indicates) flooring to
an integer value.
> 
> Shouldn't this set a scale transform of "contents_size /
texture_mailbox.size_in_pixels()" so that the adjusted size is used to set the
scale?

Good point. Done.

[reveman, 2016-01-05 09:03:00]

The CQ bit was checked by reveman@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-05 09:03:03]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1548163002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1548163002/20001

[commit-bot: I haz the power, 2016-01-05 09:18:08]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-05 09:18:08]

Dry run: This issue passed the CQ dry run.

[lpique, 2016-01-05 18:52:01]

lgtm

[reveman, 2016-01-06 08:25:13]

The CQ bit was checked by reveman@chromium.org

[commit-bot: I haz the power, 2016-01-06 08:25:49]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1548163002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1548163002/20001

[commit-bot: I haz the power, 2016-01-06 08:30:01]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-01-06 08:30:57]

Description was changed from

==========
exo: Add Surface::SetBufferScale.

The buffer scale allow clients to supply higher resolution buffer
data for use on high resolution displays.

BUG=549781
TEST=exo_unittest --gtest_filter=SurfaceTest.SetBufferScale
==========

to

==========
exo: Add Surface::SetBufferScale.

The buffer scale allow clients to supply higher resolution buffer
data for use on high resolution displays.

BUG=549781
TEST=exo_unittest --gtest_filter=SurfaceTest.SetBufferScale

Committed: https://crrev.com/7efa4b0e51409c538d7a05f6f315c51ae3c7f3b6
Cr-Commit-Position: refs/heads/master@{#367797}
==========

[commit-bot: I haz the power, 2016-01-06 08:30:58]

Patchset 2 (id:??) landed as
https://crrev.com/7efa4b0e51409c538d7a05f6f315c51ae3c7f3b6
Cr-Commit-Position: refs/heads/master@{#367797}