Revert of ash: reset color management when new screens are hotplugged

Revert of ash: reset color management when new screens are hotplugged (patchset #3 id:30009 of https://codereview.chromium.org/1914343003/ )

Reason for revert:
This is causing issues on ARM/exynos5420-peach-pit Chromebook.
Let's revert this for now as I don't have a device to investigate.

BUG=609256
Original issue's description:
> ash: reset color management when new screens are plugged
>
> With the DRM drivers on ChromeOS, the color management tables and matrices
> are stored at the pipe level (part of the display hardware that is
> configurable regardless of the actual connector it is attached to). This
> allows display configuration to remain active while different processes are
> using the driver (for example switching VT).
>
> As a result, when an external screen is connected to a Chromebook, a given
> color configuration might be applied to it and remain stored in the driver
> after the screen is disconnected. If another external screen is now
> connected the previously applied color management will remain if there is
> not a profile for that display.
>
> This change takes care of resetting the color management matrices/tables on
> newly connected screen before we apply a new configuration.
>
> BUG=495196
> TEST=Manual testing with hotplugging of a display and identify correct
> behavior.
>
> Committed: https://crrev.com/5932a0131851f35b74be5d2fc86a3834defd4d8c
> Cr-Commit-Position: refs/heads/master@{#391491}

TBR=robert.bradford@intel.com,oshima@chromium.org,spang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=495196
Committed: https://crrev.com/5f1b82e8460a3d4d0a45346cdcdf5862be27c2c7
Cr-Commit-Position: refs/heads/master@{#391781}

[llandwerlin-old, 2016-05-05 09:23:06]

Created Revert of ash: reset color management when new screens are hotplugged

[commit-bot: I haz the power, 2016-05-05 09:23:19]

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

[commit-bot: I haz the power, 2016-05-05 09:23:51]

Description was changed from

==========
Revert of ash: reset color management when new screens are hotplugged (patchset
#3 id:30009 of https://codereview.chromium.org/1914343003/ )

Reason for revert:
This is causing issues on ARM/exynos5420-peach-pit Chromebook.
Let's revert this for now as I don't have a device to investigate.

BUG=609256

Original issue's description:
> ash: reset color management when new screens are plugged
> 
> With the DRM drivers on ChromeOS, the color management tables and matrices
> are stored at the pipe level (part of the display hardware that is
> configurable regardless of the actual connector it is attached to). This
> allows display configuration to remain active while different processes are
> using the driver (for example switching VT).
> 
> As a result, when an external screen is connected to a Chromebook, a given
> color configuration might be applied to it and remain stored in the driver
> after the screen is disconnected. If another external screen is now
> connected the previously applied color management will remain if there is
> not a profile for that display.
> 
> This change takes care of resetting the color management matrices/tables on
> newly connected screen before we apply a new configuration.
> 
> BUG=495196
> TEST=Manual testing with hotplugging of a display and identify correct
> behavior.
> 
> Committed: https://crrev.com/5932a0131851f35b74be5d2fc86a3834defd4d8c
> Cr-Commit-Position: refs/heads/master@{#391491}

TBR=robert.bradford@intel.com,oshima@chromium.org,spang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=495196
==========

to

==========
Revert of ash: reset color management when new screens are hotplugged (patchset
#3 id:30009 of https://codereview.chromium.org/1914343003/ )

Reason for revert:
This is causing issues on ARM/exynos5420-peach-pit Chromebook.
Let's revert this for now as I don't have a device to investigate.

BUG=609256

Original issue's description:
> ash: reset color management when new screens are plugged
> 
> With the DRM drivers on ChromeOS, the color management tables and matrices
> are stored at the pipe level (part of the display hardware that is
> configurable regardless of the actual connector it is attached to). This
> allows display configuration to remain active while different processes are
> using the driver (for example switching VT).
> 
> As a result, when an external screen is connected to a Chromebook, a given
> color configuration might be applied to it and remain stored in the driver
> after the screen is disconnected. If another external screen is now
> connected the previously applied color management will remain if there is
> not a profile for that display.
> 
> This change takes care of resetting the color management matrices/tables on
> newly connected screen before we apply a new configuration.
> 
> BUG=495196
> TEST=Manual testing with hotplugging of a display and identify correct
> behavior.
> 
> Committed: https://crrev.com/5932a0131851f35b74be5d2fc86a3834defd4d8c
> Cr-Commit-Position: refs/heads/master@{#391491}

TBR=robert.bradford@intel.com,oshima@chromium.org,spang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=495196
==========

[commit-bot: I haz the power, 2016-05-05 09:23:52]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-05 09:25:23]

Description was changed from

==========
Revert of ash: reset color management when new screens are hotplugged (patchset
#3 id:30009 of https://codereview.chromium.org/1914343003/ )

Reason for revert:
This is causing issues on ARM/exynos5420-peach-pit Chromebook.
Let's revert this for now as I don't have a device to investigate.

BUG=609256

Original issue's description:
> ash: reset color management when new screens are plugged
> 
> With the DRM drivers on ChromeOS, the color management tables and matrices
> are stored at the pipe level (part of the display hardware that is
> configurable regardless of the actual connector it is attached to). This
> allows display configuration to remain active while different processes are
> using the driver (for example switching VT).
> 
> As a result, when an external screen is connected to a Chromebook, a given
> color configuration might be applied to it and remain stored in the driver
> after the screen is disconnected. If another external screen is now
> connected the previously applied color management will remain if there is
> not a profile for that display.
> 
> This change takes care of resetting the color management matrices/tables on
> newly connected screen before we apply a new configuration.
> 
> BUG=495196
> TEST=Manual testing with hotplugging of a display and identify correct
> behavior.
> 
> Committed: https://crrev.com/5932a0131851f35b74be5d2fc86a3834defd4d8c
> Cr-Commit-Position: refs/heads/master@{#391491}

TBR=robert.bradford@intel.com,oshima@chromium.org,spang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=495196
==========

to

==========
Revert of ash: reset color management when new screens are hotplugged (patchset
#3 id:30009 of https://codereview.chromium.org/1914343003/ )

Reason for revert:
This is causing issues on ARM/exynos5420-peach-pit Chromebook.
Let's revert this for now as I don't have a device to investigate.

BUG=609256

Original issue's description:
> ash: reset color management when new screens are plugged
>
> With the DRM drivers on ChromeOS, the color management tables and matrices
> are stored at the pipe level (part of the display hardware that is
> configurable regardless of the actual connector it is attached to). This
> allows display configuration to remain active while different processes are
> using the driver (for example switching VT).
>
> As a result, when an external screen is connected to a Chromebook, a given
> color configuration might be applied to it and remain stored in the driver
> after the screen is disconnected. If another external screen is now
> connected the previously applied color management will remain if there is
> not a profile for that display.
>
> This change takes care of resetting the color management matrices/tables on
> newly connected screen before we apply a new configuration.
>
> BUG=495196
> TEST=Manual testing with hotplugging of a display and identify correct
> behavior.
>
> Committed: https://crrev.com/5932a0131851f35b74be5d2fc86a3834defd4d8c
> Cr-Commit-Position: refs/heads/master@{#391491}

TBR=robert.bradford@intel.com,oshima@chromium.org,spang@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=495196

Committed: https://crrev.com/5f1b82e8460a3d4d0a45346cdcdf5862be27c2c7
Cr-Commit-Position: refs/heads/master@{#391781}
==========

[commit-bot: I haz the power, 2016-05-05 09:25:24]

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