Re: [PATCH 2/2] drm/amd/display: Use new connector state when getting color depth

2019-05-22 Thread Harry Wentland
Series is Reviewed-by: Harry Wentland Harry On 2019-05-22 11:11 a.m., Nicholas Kazlauskas wrote: > [CAUTION: External Email] > > [Why] > The current state on the connector is queried when getting the max bpc > rather than the new state. This means that a new max bpc value can only > currently t

Re: [PATCH 2/2] drm/amd/display: Use new connector state when getting color depth

2019-05-22 Thread Deucher, Alexander
Series is: Acked-by: Alex Deucher From: amd-gfx on behalf of Nicholas Kazlauskas Sent: Wednesday, May 22, 2019 11:11 AM To: amd-gfx@lists.freedesktop.org Cc: Li, Sun peng (Leo); Wentland, Harry; Kazlauskas, Nicholas Subject: [PATCH 2/2] drm/amd/display: Use new

[PATCH 2/2] drm/amd/display: Use new connector state when getting color depth

2019-05-22 Thread Nicholas Kazlauskas
[Why] The current state on the connector is queried when getting the max bpc rather than the new state. This means that a new max bpc value can only currently take effect on the commit *after* it changes. The new state should be passed in instead. [How] Pass down the dm_state as drm state to wher