evie/android_kernel_oneplus_msm8998
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

msm: mdss: expose correct number of supported blending stages

Browse source 
User-space decides how many layers to send for MDP composition using
max blending stage value passed by the driver. Currently driver sends
this value based on its internal enum value which does not reflect the
correct number of blending stages that HW supports. So user-space makes
independent assumption to derive at correct value by deducting 2. This
is incorrect design and may lead to unforeseen issues. Fix it by sending
correct max blending stage value.

Change-Id: Iaaed7b6824e6ef445ca202fb993d1061811b5ce0
Signed-off-by: Ujwal Patel <ujwalp@codeaurora.org>
This commit is contained in:
Ujwal Patel 2014-12-03 21:54:32 -08:00 • committed by David Keitel
parent 0db371cd8a
commit 6fe2b845dd
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
drivers/video/fbdev/msm/mdss_mdp.c
View file

@ -1095,11 +1095,11 @@ static void mdss_mdp_hw_rev_caps_init(struct mdss_data_type *mdata)
case MDSS_MDP_HW_REV_109: case MDSS_MDP_HW_REV_109:
case MDSS_MDP_HW_REV_110: case MDSS_MDP_HW_REV_110:
mdss_set_quirk(mdata, MDSS_QUIRK_BWCPANIC); mdss_set_quirk(mdata, MDSS_QUIRK_BWCPANIC);
mdata->max_target_zorder = MDSS_MDP_MAX_STAGE; mdata->max_target_zorder = 7; /* excluding base layer */
mdata->max_cursor_size = 128; mdata->max_cursor_size = 128;
break; break;
default: default:
mdata->max_target_zorder = MDSS_MDP_STAGE_4; mdata->max_target_zorder = 4; /* excluding base layer */
mdata->max_cursor_size = 64; mdata->max_cursor_size = 64;
} }
} }