diff options
| author | Madhav Chauhan <[email protected]> | 2017-04-05 09:04:23 -0400 |
|---|---|---|
| committer | Jani Nikula <[email protected]> | 2017-04-06 14:45:26 +0300 |
| commit | 97f55ca5b6625bb4ddeca7b1272b53ca04ab3cf0 (patch) | |
| tree | bb5cdbc0cb9916c3e493c5bb9b837e446a4d7262 /tools/perf/scripts/python/bin | |
| parent | 68f357cb734738d60a749abb6673e7b63ccf0221 (diff) | |
drm/i915/glk: limit pixel clock to 99% of cdclk workaround
As per BSPEC, valid cdclk values for glk are 79.2, 158.4, 316.8 Mhz.
Practically we can achive only 99% of these cdclk values (HW team
checking on this). So cdclk should be calculated for the given pixclk as
per that otherwise it may lead to screen corruption, explained below:
1. For DSI AUO panel(1920x1200 @60) required pixclk is 157100 KHZ
2. glk_calc_cdclk returns 79200 KHZ for this pixclk, For 2PPC it
will be 158400 KHZ
3. Practically 100% of the cdclk can’t be achieved, so 99% of 158400
KHZ = 156816 which is less than the desired pixlclk and causes
panel corruption.
v2: Rebased to new CDLCK code framework
v3: Addressed review comments from Ander/Jani
- Add comment in code about 99% usage of CDCLK
- Calculate max dot clock as well with 99% limit
v4 by Jani:
- drop superfluous whitespace change
- rewrite code comments to clarify
v5: Added details of non-working scenario in commit message
Cc: Ander Conselvan de Oliveira <[email protected]>
Cc: Ville Syrjälä <[email protected]>
Signed-off-by: Madhav Chauhan <[email protected]>
Signed-off-by: Jani Nikula <[email protected]>
Reviewed-by: Ander Conselvan de Oliveira <[email protected]>
Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions