From: Randy Li <ayaka@soulik.info>
To: dri-devel@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, randy.li@rock-chips.com,
linux-kernel@vger.kernel.org, daniel.vetter@intel.com,
mchehab@kernel.org, linux-media@vger.kernel.org,
Randy Li <ayaka@soulik.info>
Subject: [PATCH v2 0/2] Add pixel formats for 10/16 bits YUV video
Date: Thu, 5 Jan 2017 00:29:09 +0800 [thread overview]
Message-ID: <1483547351-5792-1-git-send-email-ayaka@soulik.info> (raw)
Those pixel formats mainly comes from Gstreamer and ffmpeg. Currently,
the VOP(video output mixer) found on RK3288 and future support
those 10 bits pixel formats are input. Also the decoder on RK3288
could use them as output.
The fourcc is not enough to store the endian information for those
pixel formats in v4l2, as it doesn't have a flag like drm does.
I have not met the usage of those 16 bits per-channel format,
it is a very large color range, even the DSLR only use 12 bits.
Randy Li (2):
drm_fourcc: Add new P010, P016 video format
[media] v4l: Add 10/16-bits per channel YUV pixel formats
Documentation/media/uapi/v4l/pixfmt-p010.rst | 86 ++++++++++++++++
Documentation/media/uapi/v4l/pixfmt-p010m.rst | 94 ++++++++++++++++++
Documentation/media/uapi/v4l/pixfmt-p016.rst | 126 ++++++++++++++++++++++++
Documentation/media/uapi/v4l/pixfmt-p016m.rst | 136 ++++++++++++++++++++++++++
drivers/gpu/drm/drm_fourcc.c | 3 +
include/uapi/drm/drm_fourcc.h | 2 +
include/uapi/linux/videodev2.h | 4 +
7 files changed, 451 insertions(+)
create mode 100644 Documentation/media/uapi/v4l/pixfmt-p010.rst
create mode 100644 Documentation/media/uapi/v4l/pixfmt-p010m.rst
create mode 100644 Documentation/media/uapi/v4l/pixfmt-p016.rst
create mode 100644 Documentation/media/uapi/v4l/pixfmt-p016m.rst
--
2.7.4
next reply other threads:[~2017-01-04 16:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:29 Randy Li [this message]
2017-01-04 16:29 ` [PATCH v2 1/2] drm_fourcc: Add new P010, P016 video format Randy Li
2017-01-04 17:02 ` Daniel Stone
2017-01-05 2:00 ` Ayaka
2017-01-23 21:16 ` Clint Taylor
2017-02-23 23:58 ` [PATCH v3 " clinton.a.taylor
2017-02-24 11:10 ` Ville Syrjälä
2017-02-27 17:21 ` [PATCH v4 " clinton.a.taylor
2017-02-27 17:41 ` Ville Syrjälä
2017-02-27 18:28 ` Clint Taylor
2017-02-27 18:47 ` Ville Syrjälä
2017-02-27 22:57 ` [PATCH v5 " clinton.a.taylor
2017-02-28 10:58 ` ayaka
2017-02-28 16:37 ` Clint Taylor
2017-02-28 11:56 ` Ville Syrjälä
2017-02-28 16:08 ` Clint Taylor
2017-02-28 16:22 ` Ville Syrjälä
2017-02-28 23:21 ` [PATCH v6 " clinton.a.taylor
2017-10-12 11:56 ` Tapani Pälli
2017-10-17 11:43 ` ayaka
2017-10-24 6:30 ` Tapani Pälli
2017-01-04 16:29 ` [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats Randy Li
2017-01-05 10:30 ` Sakari Ailus
2017-01-05 15:22 ` ayaka
2017-01-05 18:27 ` Sakari Ailus
2017-02-03 14:04 ` Mauro Carvalho Chehab
2017-02-08 9:17 ` Ayaka
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=1483547351-5792-1-git-send-email-ayaka@soulik.info \
--to=ayaka@soulik.info \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=randy.li@rock-chips.com \
--cc=ville.syrjala@linux.intel.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;
as well as URLs for NNTP newsgroup(s).