drm/amd/display: Call ATOM_INIT instead of ATOM_ENABLE for DMCUB
authorNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Sat, 11 Jan 2020 18:43:39 +0000 (13:43 -0500)
committerAlex Deucher <alexander.deucher@amd.com>
Wed, 22 Jan 2020 21:55:28 +0000 (16:55 -0500)
commitcc934031dc2a0be9535477dbef4b0e94c9f06ecd
treec35daeb22d005a86b5656e08cee12ea3018d07e7
parent0167da498d57dddf31eb30516d1fae0f31ddecb6
drm/amd/display: Call ATOM_INIT instead of ATOM_ENABLE for DMCUB

[Why]
DMCUB command table doesn't support ATOM_ENABLE/ATOM_DISABLE anymore
so we never end up calling the DCN init path in DMCUB.

[How]
Map ATOM_ENABLE to ATOM_INIT only for DMCUB command table offloading.

Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/dc/bios/command_table2.c