summaryrefslogtreecommitdiff
path: root/sound/pci/lola
ModeNameSize
-rw-r--r--Makefile140logplain
-rw-r--r--lola.c20058logplain
-rw-r--r--lola.h16687logplain
-rw-r--r--lola_clock.c8216logplain
-rw-r--r--lola_mixer.c26063logplain
-rw-r--r--lola_pcm.c18965logplain
-rw-r--r--lola_proc.c7264logplain
.) The timings are correct, it behaves as if the start address has been shifted many pixels _into_ the framebuffer. This occurs whenever the display mode size is changed - using xrandr in Xorg shows that changing the resolution triggers the problem almost every time, but changing the refresh rate does not. Using devmem2 to disable and re-enable the HDLCD resolves the issue, and repeated disable/enable cycles do not make the issue re-appear. Further debugging shows that we try to update the controller configuration while enabled. Alwys ensure that the HDLCD is disabled prior to updating the controller timings, and use drm_crtc_vblank_off()/drm_crtc_vblank_on() so that DRM knows whether it can expect vblank interrupts. Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
Diffstat (limited to 'tools/usb/ffs-aio-example/multibuff')