On 2017-10-26 12:06 PM, Christian König wrote: > From: Christian König <[email protected]> > > Just set the bit so that DC does the hardware programming. > > Signed-off-by: Christian König <[email protected]> > --- > drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c > b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c > index 2188f20..ed4351a 100644 > --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c > +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c > @@ -417,6 +417,8 @@ static int amdgpu_dm_init(struct amdgpu_device *adev) > > init_data.dce_environment = DCE_ENV_PRODUCTION_DRV; > > + init_data.flags.gpu_vm_support = true; > +
Hi Christian, what ASIC has this been tested on? I'm not sure that this won't break dGPU. dGPU doesn't have vm_support but I think DC will still try to write the same registers as for CZ on dGPU if we enable this. We at least need to make sure it doesn't blow up. As for Raven we use this flag on Windows but only tested the case where VM is actually programmed. If VM isn't programmed it might still work but we'd need to give that a spin. Harry > if (amdgpu_dc_log) > init_data.log_mask = DC_DEFAULT_LOG_MASK; > else > _______________________________________________ amd-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/amd-gfx
