Re: [PATCH 25/29] drm/omap: Pass drm_display_mode to .check_timings() and .set_timings()

2018-12-10 Thread Sebastian Reichel
Hi, On Wed, Dec 05, 2018 at 05:00:18PM +0200, Laurent Pinchart wrote: > The omap_dss_device .check_timings() and .set_timings() operations > operate on struct videomode, while the DRM API operates on struct > drm_display_mode. This forces conversion from to videomode in the > callers. While

Re: [PATCH 25/29] drm/omap: Pass drm_display_mode to .check_timings() and .set_timings()

2018-12-10 Thread Laurent Pinchart
Hi Sebastian, On Monday, 10 December 2018 00:26:28 EET Sebastian Reichel wrote: > On Wed, Dec 05, 2018 at 05:00:18PM +0200, Laurent Pinchart wrote: > > The omap_dss_device .check_timings() and .set_timings() operations > > operate on struct videomode, while the DRM API operates on struct > >

[PATCH 25/29] drm/omap: Pass drm_display_mode to .check_timings() and .set_timings()

2018-12-05 Thread Laurent Pinchart
The omap_dss_device .check_timings() and .set_timings() operations operate on struct videomode, while the DRM API operates on struct drm_display_mode. This forces conversion from to videomode in the callers. While that's not a problem per se, it creates a difference with the drm_bridge API.