[PATCH 08/10] video/hdmi: Reject illegal picture aspect ratios

2017-11-13 Thread Ville Syrjala
From: Ville Syrjälä AVI infoframe can only carry none, 4:3, or 16:9 picture aspect ratios. Return an error if the user asked for something different. Cc: Shashank Sharma Cc: "Lin, Jia" Cc: Akashdeep Sharma

[PATCH 10/10] video/hdmi: Pass buffer size to infoframe unpack functions

2017-11-13 Thread Ville Syrjala
From: Ville Syrjälä To make sure the infoframe unpack functions don't end up examining stack garbage or oopsing, let's pass in the size of the buffer. Cc: Thierry Reding Cc: Hans Verkuil Cc:

[PATCH 09/10] video/hdmi: Constify 'buffer' to the unpack functions

2017-11-13 Thread Ville Syrjala
From: Ville Syrjälä The unpack functions just read from the passed in buffer, so make it const. Cc: Thierry Reding Cc: Hans Verkuil Cc: linux-media@vger.kernel.org Signed-off-by: Ville Syrjälä

[PATCH 01/10] video/hdmi: Allow "empty" HDMI infoframes

2017-11-13 Thread Ville Syrjala
From: Ville Syrjälä HDMI 2.0 Appendix F suggest that we should keep sending the infoframe when switching from 3D to 2D mode, even if the infoframe isn't strictly necessary (ie. not needed to transmit the VIC or stereo information). This is a workaround against some

[PATCH 00/10] drm/edid: Infoframe cleanups and fixes

2017-11-13 Thread Ville Syrjala
From: Ville Syrjälä This series tries to fix some issues with HDMI infoframes. In particular we can currently send a bogus picture aspect ratio in the infoframe. I included stuff to to make the infoframe unpakc more robust, evne though we don't (yet) use it in drm.

[PATCH 4/4] dma-buf: Use rcu_assign_pointer() to set rcu protected pointers

2017-11-02 Thread Ville Syrjala
From: Ville Syrjälä Use rcu_assign_pointer() when setting an rcu protected pointer. This gets rid of another sparse warning. Cc: Dave Airlie Cc: Jason Ekstrand Cc: linaro-mm-...@lists.linaro.org Cc:

[PATCH 2/4] dma-buf/fence: Sparse wants __rcu on the object itself

2017-11-02 Thread Ville Syrjala
From: Chris Wilson In order to silent sparse in dma_fence_get_rcu_safe(), we need to mark the incoming fence object as being RCU protected and not the pointer to the object. Cc: Dave Airlie Cc: Jason Ekstrand Cc:

[PATCH 3/4] drm/syncobj: Use proper methods for accessing rcu protected pointers

2017-11-02 Thread Ville Syrjala
From: Ville Syrjälä Use rcu_dereference_protected() and rcu_assign_pointer() for accessing the rcu protected syncobj->fence pointer. This eliminates several sparse warnings. Cc: Dave Airlie Cc: Jason Ekstrand Cc:

[PATCH 1/4] drm/syncobj: Mark up the fence as an RCU protected pointer

2017-11-02 Thread Ville Syrjala
From: Chris Wilson We take advantage of that syncobj->fence is an RCU-protected pointer, and so sparse complains that it is lacking annotation. Cc: Dave Airlie Cc: Jason Ekstrand Cc: linaro-mm-...@lists.linaro.org Cc:

[PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings

2017-11-02 Thread Ville Syrjala
From: Ville Syrjälä When building drm+i915 I get around 150 lines of sparse noise from dma_fence __rcu warnings. This series eliminates all of that. The first two patches were already posted by Chris, but there wasn't any real reaction, so I figured I'd repost