summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap2/hsmmc.h
diff options
context:
space:
mode:
authorMehnert <tmehnert@eckelmann.de>2012-03-13 12:13:51 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2012-03-13 13:57:07 +0100
commit1dde9f75b658edcd4fb7e00259206d727702ce61 (patch)
tree4f35d9f8826eb8eec9a5ff3d101ce5b41e4f8c79 /arch/arm/mach-omap2/hsmmc.h
parent192cfd58774b4d17b2fe8bdc77d89c2ef4e0591d (diff)
downloadlinux-3.10-1dde9f75b658edcd4fb7e00259206d727702ce61.tar.gz
linux-3.10-1dde9f75b658edcd4fb7e00259206d727702ce61.tar.bz2
linux-3.10-1dde9f75b658edcd4fb7e00259206d727702ce61.zip
iomux-mx25.h slew rate adjusted for LCD __LD pins
For some reason (sadly i don't identifying the patch right now) two LCD data lines configured PAD_CTL_SRE_SLOW (wrong slew rate) since Kernel 3.1. MX25_PAD_GPIO_E__LD16 and MX25_PAD_GPIO_F__LD17 This results in an fauly behaviour and strange color effects. To ensure that all LCD data pins configured with the proper slew rate, this patch changes to IOMUX define of all LCD __LDxx pins to PAD_CTL_SRE_FAST. This problem may affect other mx25 platforms like mx25pdk. Sadly i can't test it. Of course this problem shouldn't occur when you done your LCD muxing correctly in the bootloader. Best regards, Torsten Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'arch/arm/mach-omap2/hsmmc.h')
0 files changed, 0 insertions, 0 deletions