summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/esas2r
diff options
context:
space:
mode:
authorhersen wu <hersenxs.wu@amd.com>2019-06-26 13:06:07 -0400
committerAlex Deucher <alexander.deucher@amd.com>2019-07-18 14:12:08 -0500
commit41a5a2a8531f95d18bb4efddea581ccb469e8ee5 (patch)
treeef09199ae11386e89ab48057d6ce7fc4fa221cdc /drivers/scsi/esas2r
parent8a5b5d425e5454fdef0e5457826f4aa7f96cf463 (diff)
downloadlinux-41a5a2a8531f95d18bb4efddea581ccb469e8ee5.tar.bz2
drm/amd/display: init res_pool dccg_ref, dchub_ref with xtalin_freq
[WHY] dc sw clock implementation of navi10 and raven are not exact the same. dcccg, dchub reference clock initialization is done after dc calls vbios dispcontroller_init table. for raven family, before dispcontroller_init is called by dc, the ref clk values are referred by sw clock implementation and program asic register using wrong values. this causes dchub pstate error. This need provide valid ref clk values. for navi10, since dispcontroller_init is not called, dchubbub_global_timer_enable = 0, hubbub2_get_dchub_ref_freq will hit aeert. this need remove hubbub2_get_dchub_ref_freq from this location and move to dcn20_init_hw. [HOW] for all asic, initialize dccg, dchub ref clk with data from vbios firmware table by default. for raven asic family, use these data from vbios, for asic which support sw dccg component, like navi10, read ref clk by sw dccg functions and update the ref clk. Signed-off-by: hersen wu <hersenxs.wu@amd.com> Reviewed-by: Jun Lei <Jun.Lei@amd.com> Acked-by: Leo Li <sunpeng.li@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/scsi/esas2r')
0 files changed, 0 insertions, 0 deletions