[Chromecast] Include output screen resolution in OSD rect info

[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions

Committed: https://crrev.com/8da342224564207f57eb2d565c2585e3672c4f2f
Cr-Commit-Position: refs/heads/master@{#408187}

[halliwell, 2016-07-27 16:05:06]

Description was changed from

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions
==========

to

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions
==========

[halliwell, 2016-07-27 16:05:06]

halliwell@chromium.org changed reviewers:
+ derekjchow@chromium.org, gfhuang@chromium.org

[halliwell, 2016-07-27 16:05:44]

gfhuang: want to confirm this won't cause problems (I think nobody else
implements OSD interface, right?)

Internal CLs to follow.

[gfhuang, 2016-07-27 17:07:59]

On 2016/07/27 16:05:44, halliwell wrote:
> gfhuang: want to confirm this won't cause problems (I think nobody else
> implements OSD interface, right?)
> 
> Internal CLs to follow.

lgtm

[halliwell, 2016-07-27 17:45:15]

The CQ bit was checked by halliwell@chromium.org

[commit-bot: I haz the power, 2016-07-27 17:45:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-07-27 18:22:28]

Description was changed from

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions
==========

to

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions
==========

[commit-bot: I haz the power, 2016-07-27 18:22:29]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-07-27 18:24:09]

Description was changed from

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions
==========

to

==========
[Chromecast] Include output screen resolution in OSD rect info

Current OSD SetClipRect API is ambiguous, as it doesn't specify what
coordinate space the clip rect is in.  This is solved by passing the
OSD screen resolution.

Additionally, pass the output screen resolution through.  Some
implementations need this info in order to scale the OSD correctly.
They could probably get the screen res in vendor-specific ways but
it's more convenient to just plumb it through here.

BUG=internal b/30025430
TEST=manual OSD test on different screen resolutions

Committed: https://crrev.com/8da342224564207f57eb2d565c2585e3672c4f2f
Cr-Commit-Position: refs/heads/master@{#408187}
==========

[commit-bot: I haz the power, 2016-07-27 18:24:10]

Patchset 1 (id:??) landed as
https://crrev.com/8da342224564207f57eb2d565c2585e3672c4f2f
Cr-Commit-Position: refs/heads/master@{#408187}