-
Miguel Casas authored
This CL wires 3 display/monitor fields from EDID parsing to the Chrome private API where they surface, as described in the DD [1], namely: 1- manufacturer id 2- product id 3- year of manufacture. (Note that ToT Ozone DRM already parses this list's 1 and 2; this CL adds code to parse 3). A diagram of the touched areas is in the DD [1] extracted for quick access in: https://i.imgur.com/yx8H0R3.jpg (also [2]). but in a nutshell: Ozone DRM creates a DisplaySnapshot from the EDID, and passes it to Browser Process via Mojo and/or IPC (being migrated); in Browser DisplayChangeObserver transforms that snapshot into a ManagedDisplayInfo, and in turn passes it to the DisplayManager that creates a Display that is used later on upon request by DisplayInfoProviderChromeOS to fill in the JS data struct. There's a bit of confusion on ToT between product_id and product_code, so this CL follows the spec and aligns them all, i.e. EDID parser produces a |product_code|, which is a pack of the manufacturer id and product id. Unittests extended, tested on soraka+simplechrome. [1] go/js-edid-chromeos [2] https://imgur.com/a/aqNDD Bug: 821393 Change-Id: Ia219b4eeb92cf3eae3e58046340f1b81c34c9ea2 Reviewed-on: https://chromium-review.googlesource.com/959547 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#543512}
9b90891e