drm/amd/display: Fix mismatch type comparison
[ Upstream commit 26873260d394b1e33cdd720154aedf0af95327f9 ] The mismatch type comparison/assignment may cause data loss. Since the values are always non-negative, it is safe to use unsigned variables to resolve the mismatch. Signed-off-by: Navid Assadian <navid.assadian@amd.com> Reviewed-by: Joshua Aberback <joshua.aberback@amd.com> Tested-by: Daniel Wheeler <daniel.wheeler@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
990e4fb37b
commit
6e5935b755
@@ -875,8 +875,8 @@ static bool spl_get_optimal_number_of_taps(
|
||||
bool *enable_isharp)
|
||||
{
|
||||
int num_part_y, num_part_c;
|
||||
int max_taps_y, max_taps_c;
|
||||
int min_taps_y, min_taps_c;
|
||||
unsigned int max_taps_y, max_taps_c;
|
||||
unsigned int min_taps_y, min_taps_c;
|
||||
enum lb_memory_config lb_config;
|
||||
bool skip_easf = false;
|
||||
|
||||
|
||||
@@ -479,7 +479,7 @@ struct spl_sharpness_range {
|
||||
};
|
||||
struct adaptive_sharpness {
|
||||
bool enable;
|
||||
int sharpness_level;
|
||||
unsigned int sharpness_level;
|
||||
struct spl_sharpness_range sharpness_range;
|
||||
};
|
||||
enum linear_light_scaling { // convert it in translation logic
|
||||
|
||||
Reference in New Issue
Block a user