Re: [RFC][PATCH v2] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

On 18-07-2017 17:56, John Stultz wrote: > On Tue, Jul 18, 2017 at 4:10 AM, Jose Abreu wrote: >> Hi John, >> >> >> On 18-07-2017 05:22, John Stultz wrote: >>> Currently the hikey dsi logic cannot generate accurate byte >>> clocks values for all pixel clock values. Thus if a mode clock >>> is selec

Re: [RFC][PATCH v2] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

On Tue, Jul 18, 2017 at 4:10 AM, Jose Abreu wrote: > Hi John, > > > On 18-07-2017 05:22, John Stultz wrote: >> Currently the hikey dsi logic cannot generate accurate byte >> clocks values for all pixel clock values. Thus if a mode clock >> is selected that cannot match the calculated byte clock, t

Re: [RFC][PATCH v2] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

Hi John, On 18-07-2017 05:22, John Stultz wrote: > Currently the hikey dsi logic cannot generate accurate byte > clocks values for all pixel clock values. Thus if a mode clock > is selected that cannot match the calculated byte clock, the > device will boot with a blank screen. > > This patch use

[RFC][PATCH v2] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

Currently the hikey dsi logic cannot generate accurate byte clocks values for all pixel clock values. Thus if a mode clock is selected that cannot match the calculated byte clock, the device will boot with a blank screen. This patch uses the new mode_valid callback (many thanks to Jose Abreu for u