summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/mxsfb/mxsfb_out.c
diff options
context:
space:
mode:
authorStefan Agner2016-12-14 21:48:09 +0100
committerDave Airlie2017-03-10 02:10:49 +0100
commit53990e416bb7adaa59d045f325a47f31a11b75ee (patch)
treed87ea97b09ecedad96ffaf192c35dc1ee616517f /drivers/gpu/drm/mxsfb/mxsfb_out.c
parentdrm: mxsfb: use bus_format to determine LCD bus width (diff)
downloadkernel-qcow2-linux-53990e416bb7adaa59d045f325a47f31a11b75ee.tar.gz
kernel-qcow2-linux-53990e416bb7adaa59d045f325a47f31a11b75ee.tar.xz
kernel-qcow2-linux-53990e416bb7adaa59d045f325a47f31a11b75ee.zip
drm: mxsfb: fix pixel clock polarity
The DRM subsystem specifies the pixel clock polarity from a controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means the controller drives the data on pixel clocks falling edge. That is the controllers DOTCLK_POL=0 (Default is data launched at negative edge). Also change the data enable logic to be high active by default and only change if explicitly requested via bus_flags. With that defaults are: - Data enable: high active - Pixel clock polarity: controller drives data on negative edge Signed-off-by: Stefan Agner <stefan@agner.ch> Acked-by: Marek Vasut <marex@denx.de> Signed-off-by: Dave Airlie <airlied@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/mxsfb/mxsfb_out.c')
0 files changed, 0 insertions, 0 deletions