Hi,
in short: this patch is "CANCELLED" : )
There is no need to add the pixel clock as a mandatory property because
now the clock value is ajusted in adjusted_mode.
Please have a look to patches:
- drm/stm: ltdc: use crtc_mode_fixup to update adjusted_mode clock
- drm/bridge/synopsys: dsi: use
Add the DPI/RGB input pixel clock in mandatory properties
because it really offers a better preciseness for timing
computations.
Signed-off-by: Philippe Cornu
---
Please apply "dt-bindings: display: stm32: correct clock-names
in dsi panel example" before this patch.
Changes in v3: remove the not
Add the DPI/RGB input pixel clock in mandatory properties
because it really offers a better preciseness for timing
computations.
Signed-off-by: Philippe Cornu
---
Please apply "dt-bindings: display: stm32: correct clock-names
in dsi panel example" before this patch.
Changes in v3: remove the not
Hi Rob,
On 10/27/2017 04:38 PM, Rob Herring wrote:
> On Thu, Oct 26, 2017 at 06:12:36PM +0200, Philippe Cornu wrote:
>> Add the DPI/RGB input pixel clock in mandatory properties
>> because it really offers a better preciseness for timing
>> computations.
>> Note: Fix also the DSI panel example whe
On Thu, Oct 26, 2017 at 06:12:36PM +0200, Philippe Cornu wrote:
> Add the DPI/RGB input pixel clock in mandatory properties
> because it really offers a better preciseness for timing
> computations.
> Note: Fix also the DSI panel example where "ref" & "pclk"
> clocks were swapped.
>
> Signed-off-b
Add the DPI/RGB input pixel clock in mandatory properties
because it really offers a better preciseness for timing
computations.
Note: Fix also the DSI panel example where "ref" & "pclk"
clocks were swapped.
Signed-off-by: Philippe Cornu
---
Documentation/devicetree/bindings/display/st,stm32-ltd
