summaryrefslogtreecommitdiffstats
path: root/arch/s390/Kconfig
diff options
context:
space:
mode:
authorTimur Tabi <timur@freescale.com>2012-05-10 16:57:28 -0500
committerFlorian Tobias Schandinat <FlorianSchandinat@gmx.de>2012-05-13 13:08:56 +0000
commit5e7b911f9a3e582635801675b7fe935b16cd4af5 (patch)
tree5ff0b6bf83310af0f4516836291d911960f2cf5a /arch/s390/Kconfig
parent24bb7a6efc528ea6d6270ac2c788f23bb32c2331 (diff)
downloadlinux-stable-5e7b911f9a3e582635801675b7fe935b16cd4af5.tar.gz
linux-stable-5e7b911f9a3e582635801675b7fe935b16cd4af5.tar.bz2
linux-stable-5e7b911f9a3e582635801675b7fe935b16cd4af5.zip
drivers/video: fsl-diu-fb: don't initialize the THRESHOLDS registers
The THRESHOLDS register configures thresholds for two interrupts, but these interrupts are not used in the DIU driver. An early version of the driver may have used the "lines before vsync" interrupt, which requires the LS_BF_VS of THRESHOLDS to be initialized. Unfortunately, the initialization of this register does not do a read-modify-write to set only LS_BF_VS. On the MPC8610, the value written is correct. On other chips, like the P1022, the value overwrites some reserved bits. This results in a performance drop on the P1022. Since the default value is acceptable as-is on all SOCs, we should just avoid touching this register. Signed-off-by: Timur Tabi <timur@freescale.com> Signed-off-by: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Diffstat (limited to 'arch/s390/Kconfig')
0 files changed, 0 insertions, 0 deletions