From: Philipp Zabel <p.zabel@pengutronix.de>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Steve Longerbeam <slongerbeam@gmail.com>
Subject: Re: [PATCH v2 4/4] media-ctl: add colorimetry support
Date: Mon, 13 Feb 2017 11:02:42 +0100 [thread overview]
Message-ID: <1486980162.2873.33.camel@pengutronix.de> (raw)
In-Reply-To: <20170213094823.GG16975@valkosipuli.retiisi.org.uk>
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?
regards
Philipp
next prev parent reply other threads:[~2017-02-13 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 9:33 [PATCH v2 1/4] media-ctl: add pad support to set/get_frame_interval Philipp Zabel
2017-02-13 9:33 ` [PATCH v2 2/4] media-ctl: print the configured frame interval Philipp Zabel
2017-02-13 9:33 ` [PATCH v2 3/4] media-ctl: propagate " Philipp Zabel
2017-02-13 9:33 ` [PATCH v2 4/4] media-ctl: add colorimetry support Philipp Zabel
2017-02-13 9:40 ` Hans Verkuil
2017-02-13 9:48 ` Sakari Ailus
2017-02-13 9:58 ` Hans Verkuil
2017-02-13 10:02 ` Philipp Zabel [this message]
2017-02-13 10:05 ` Sakari Ailus
2017-02-13 10:06 ` Hans Verkuil
2017-02-13 9:49 ` Philipp Zabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1486980162.2873.33.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=slongerbeam@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox