On Mon, Feb 13, 2017 at 11:02:42AM +0100, Philipp Zabel wrote:
> On Mon, 2017-02-13 at 11:48 +0200, Sakari Ailus wrote:
> > Hi Hans,
> >
> > On Mon, Feb 13, 2017 at 10:40:41AM +0100, Hans Verkuil wrote:
> > ...
> > > > @@ -839,6 +951,157 @@ enum v4l2_field v4l2_subdev_string_to_field(const char *string)
> > > > return (enum v4l2_field)-1;
> > > > }
> > > >
> > > > +static struct {
> > > > + const char *name;
> > > > + enum v4l2_colorspace colorspace;
> > > > +} colorspaces[] = {
> > > > + { "default", V4L2_COLORSPACE_DEFAULT },
> > > > + { "smpte170m", V4L2_COLORSPACE_SMPTE170M },
> > > > + { "smpte240m", V4L2_COLORSPACE_SMPTE240M },
> > > > + { "rec709", V4L2_COLORSPACE_REC709 },
> > > > + { "bt878", V4L2_COLORSPACE_BT878 },
> > >
> > > Drop this, it's no longer used in the kernel.
> >
> > What about older kernels? Were there drivers that reported it?
>
> Has there ever been a v4l2 subdevice that reported bt878 colorspace on a
> pad via VIDIOC_SUBDEV_G_FMT?
Based on Hans's reply, no. So let's remove that.
--
Sakari Ailus
e-mail: sakari.ailus@xxxxxx XMPP: sailus@xxxxxxxxxxxxxx
