Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-08 Thread Marek Vasut
On 02/08/2017 08:19 AM, Daniel Vetter wrote: > On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: >> On 2016-12-14 13:25, Marek Vasut wrote: >>> On 12/14/2016 09:48 PM, Stefan Agner wrote: The DRM subsystem specifies the pixel clock polarity from a controllers

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-08 Thread Marek Vasut
On 02/08/2017 08:19 AM, Daniel Vetter wrote: > On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: >> On 2016-12-14 13:25, Marek Vasut wrote: >>> On 12/14/2016 09:48 PM, Stefan Agner wrote: The DRM subsystem specifies the pixel clock polarity from a controllers perspective:

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-07 Thread Daniel Vetter
On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: > On 2016-12-14 13:25, Marek Vasut wrote: >> On 12/14/2016 09:48 PM, Stefan Agner wrote: >>> The DRM subsystem specifies the pixel clock polarity from a >>> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >>> the

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-07 Thread Daniel Vetter
On Wed, Feb 8, 2017 at 6:19 AM, Stefan Agner wrote: > On 2016-12-14 13:25, Marek Vasut wrote: >> On 12/14/2016 09:48 PM, Stefan Agner wrote: >>> The DRM subsystem specifies the pixel clock polarity from a >>> controllers perspective: DRM_BUS_FLAG_PIXDATA_NEGEDGE means >>> the controller drives

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-07 Thread Stefan Agner
Dave, Marek, On 2016-12-14 13:25, Marek Vasut wrote: > On 12/14/2016 09:48 PM, Stefan Agner wrote: >> 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

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2017-02-07 Thread Stefan Agner
Dave, Marek, On 2016-12-14 13:25, Marek Vasut wrote: > On 12/14/2016 09:48 PM, Stefan Agner wrote: >> 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

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2016-12-14 Thread Marek Vasut
On 12/14/2016 09:48 PM, Stefan Agner wrote: > 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 >

Re: [PATCH v2] drm/mxsfb: fix pixel clock polarity

2016-12-14 Thread Marek Vasut
On 12/14/2016 09:48 PM, Stefan Agner wrote: > 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 >

[PATCH v2] drm/mxsfb: fix pixel clock polarity

2016-12-14 Thread Stefan Agner
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

[PATCH v2] drm/mxsfb: fix pixel clock polarity

2016-12-14 Thread Stefan Agner
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