[lkml]   [2013]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4/4] [media] em28xx: Fix vidioc fmt vid cap v4l2 compliance
On Thu 18 July 2013 04:07:51 Devin Heitmueller wrote:
> On Tue, Jul 16, 2013 at 7:06 PM, Alban Browaeys
> <> wrote:
> > Set fmt.pix.priv to zero in vidioc_g_fmt_vid_cap
> > and vidioc_try_fmt_vid_cap.
> Any reason not to have the v4l2 core do this before dispatching to the
> driver? Set it to zero before the core calls g_fmt. This avoids all
> the drivers (most of which don't use the field) from having to set the
> value themselves.

There is still one driver (sn9c102) that's (ab)using it. Although perhaps I
should take a look at it and fix it.

Note that priv only needs to be cleared for try/s_fmt. g_fmt does clear it
already in the core before handing it over to the driver.

That said, I am undecided whether to put this in the core. We might actually
start to use this field for something useful in the future. By having drivers
clear it explicitly it will be easier to do that.



 \ /
  Last update: 2013-07-18 10:21    [W:0.053 / U:11.872 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site