Commit d9ec5cfd authored by Leo Li's avatar Leo Li Committed by Alex Deucher

drm/amd/display: Use switch table for dc_to_smu_clock_type

Using a static int array will cause errors if the given dm_pp_clk_type
is out-of-bounds. For robustness, use a switch table, with a default
case to handle all invalid values.

v2: 0 is a valid clock type for smu_clk_type. Return SMU_CLK_COUNT
    instead on invalid mapping.
Signed-off-by: default avatarLeo Li <sunpeng.li@amd.com>
Reviewed-by: default avatarNicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
parent d196bbbc
...@@ -151,18 +151,31 @@ static void get_default_clock_levels( ...@@ -151,18 +151,31 @@ static void get_default_clock_levels(
static enum smu_clk_type dc_to_smu_clock_type( static enum smu_clk_type dc_to_smu_clock_type(
enum dm_pp_clock_type dm_pp_clk_type) enum dm_pp_clock_type dm_pp_clk_type)
{ {
#define DCCLK_MAP_SMUCLK(dcclk, smuclk) \ enum smu_clk_type smu_clk_type = SMU_CLK_COUNT;
[dcclk] = smuclk
switch (dm_pp_clk_type) {
static int dc_clk_type_map[] = { case DM_PP_CLOCK_TYPE_DISPLAY_CLK:
DCCLK_MAP_SMUCLK(DM_PP_CLOCK_TYPE_DISPLAY_CLK, SMU_DISPCLK), smu_clk_type = SMU_DISPCLK;
DCCLK_MAP_SMUCLK(DM_PP_CLOCK_TYPE_ENGINE_CLK, SMU_GFXCLK), break;
DCCLK_MAP_SMUCLK(DM_PP_CLOCK_TYPE_MEMORY_CLK, SMU_MCLK), case DM_PP_CLOCK_TYPE_ENGINE_CLK:
DCCLK_MAP_SMUCLK(DM_PP_CLOCK_TYPE_DCEFCLK, SMU_DCEFCLK), smu_clk_type = SMU_GFXCLK;
DCCLK_MAP_SMUCLK(DM_PP_CLOCK_TYPE_SOCCLK, SMU_SOCCLK), break;
}; case DM_PP_CLOCK_TYPE_MEMORY_CLK:
smu_clk_type = SMU_MCLK;
return dc_clk_type_map[dm_pp_clk_type]; break;
case DM_PP_CLOCK_TYPE_DCEFCLK:
smu_clk_type = SMU_DCEFCLK;
break;
case DM_PP_CLOCK_TYPE_SOCCLK:
smu_clk_type = SMU_SOCCLK;
break;
default:
DRM_ERROR("DM_PPLIB: invalid clock type: %d!\n",
dm_pp_clk_type);
break;
}
return smu_clk_type;
} }
static enum amd_pp_clock_type dc_to_pp_clock_type( static enum amd_pp_clock_type dc_to_pp_clock_type(
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment