[PATCHv2 20/31] drm/omap: HDMI: Fix HSW value

2016-03-01 Thread Tomi Valkeinen
On 29/02/16 23:55, Laurent Pinchart wrote: > Hi Tomi, > > Thank you for the patch. > > On Friday 26 February 2016 11:36:08 Tomi Valkeinen wrote: >> On OMAP4 and OMAP5 ES1.0 the HDMI_WP_VIDEO_TIMING_H:HSW field is >> set directly to the HSW value. On later SoCs the field needs to be >> programme

[PATCHv2 20/31] drm/omap: HDMI: Fix HSW value

2016-02-29 Thread Laurent Pinchart
Hi Tomi, Thank you for the patch. On Friday 26 February 2016 11:36:08 Tomi Valkeinen wrote: > On OMAP4 and OMAP5 ES1.0 the HDMI_WP_VIDEO_TIMING_H:HSW field is > set directly to the HSW value. On later SoCs the field needs to be > programmed with the value of HSW-1. > > Currently the driver alway

[PATCHv2 20/31] drm/omap: HDMI: Fix HSW value

2016-02-26 Thread Tomi Valkeinen
On OMAP4 and OMAP5 ES1.0 the HDMI_WP_VIDEO_TIMING_H:HSW field is set directly to the HSW value. On later SoCs the field needs to be programmed with the value of HSW-1. Currently the driver always programs the field with the HSW value. Most videomodes seem to work fine with that, but at least low r