| commit | 06e4cd64174b48345cbd99179b780a2bf4f96ab6 | |
| author | Dave Airlie <airlied@redhat.com> | |
| Tue, 20 Dec 2011 11:44:30 +0000 (20 11:44 +0000) | ||
| committer | Dave Airlie <airlied@redhat.com> | |
| Tue, 20 Dec 2011 19:58:27 +0000 (20 19:58 +0000) | ||
| tree | 45e6614b7842ba1d020780999a0e31d48b7e242d | treesnapshot (tar.gz zip) |
| parent | 4bc22a1aa02a0aae97a905091727345085281e61 | commitdiff |
drm/radeon/kms: don't use 0 bpc for adjusting hdmi clock
If the bpc is set from the connector is 0, we then use it later to adjust
in a special case the HDMI pixel clock, however if the bpc is 0, we end up
passing a 0 pixel clock into the code.
I'm not sure if this is the correct answer or if we should avoid the HDMI
clock adjustment for 0 values.
This fixes a divide by 0 on my Llano system with a HDMI monitor and hdmi
audio enabled.
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
If the bpc is set from the connector is 0, we then use it later to adjust
in a special case the HDMI pixel clock, however if the bpc is 0, we end up
passing a 0 pixel clock into the code.
I'm not sure if this is the correct answer or if we should avoid the HDMI
clock adjustment for 0 values.
This fixes a divide by 0 on my Llano system with a HDMI monitor and hdmi
audio enabled.
Reviewed-by: Alex Deucher <alexdeucher@gmail.com>
Signed-off-by: Dave Airlie <airlied@redhat.com>
| drivers/gpu/drm/radeon/atombios_crtc.c | diffblobblamehistory |