drm/amd/display: Fix wrongly passed static prefix
authorTakashi Iwai <tiwai@suse.de>
Thu, 28 Nov 2019 08:27:14 +0000 (09:27 +0100)
committerAlex Deucher <alexander.deucher@amd.com>
Thu, 6 Feb 2020 20:04:38 +0000 (15:04 -0500)
Currently, gcc spews a warning as:
  drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hubbub.c: In function ‘hubbub1_verify_allow_pstate_change_high’:
  ./include/drm/drm_print.h:316:2: warning: ‘debug_data’ may be used uninitialized in this function [-Wmaybe-uninitialized]

This is because the code checks against a static value although it's
basically a constant and guaranteed to be set.

This patch changes the type prefix from static to const for addressing
the compile warning above and also for letting the compiler optimize
better.

Fixes: 62d591a8e00c ("drm/amd/display: create new files for hubbub functions")
Reviewed-by: Harry Wentland <harry.wentland@amd.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/dc/dcn10/dcn10_hubbub.c

index 870735deaca718bc9e08a165b02fbc390ead3310..3e851713cf8de8428b786720d6ed958f8d824066 100644 (file)
@@ -128,8 +128,8 @@ bool hubbub1_verify_allow_pstate_change_high(
         * pstate takes around ~100us on linux. Unknown currently as to
         * why it takes that long on linux
         */
-       static unsigned int pstate_wait_timeout_us = 200;
-       static unsigned int pstate_wait_expected_timeout_us = 40;
+       const unsigned int pstate_wait_timeout_us = 200;
+       const unsigned int pstate_wait_expected_timeout_us = 40;
        static unsigned int max_sampled_pstate_wait_us; /* data collection */
        static bool forced_pstate_allow; /* help with revert wa */