From: ayaka <ayaka@soulik.info>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: dri-devel@lists.freedesktop.org, 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
Subject: Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
Date: Thu, 5 Jan 2017 23:22:26 +0800 [thread overview]
Message-ID: <9a7e7ffd-27d5-0fff-2be5-03f14cc78683@soulik.info> (raw)
In-Reply-To: <20170105103037.GT3958@valkosipuli.retiisi.org.uk>
On 01/05/2017 06:30 PM, Sakari Ailus wrote:
> Hi Randy,
>
> Thanks for the update.
>
> On Thu, Jan 05, 2017 at 12:29:11AM +0800, Randy Li wrote:
>> The formats added by this patch are:
>> V4L2_PIX_FMT_P010
>> V4L2_PIX_FMT_P010M
>> V4L2_PIX_FMT_P016
>> V4L2_PIX_FMT_P016M
>> Currently, none of driver uses those format, but some video device
>> has been confirmed with could as those format for video output.
>> The Rockchip's new decoder has supported those 10 bits format for
>> profile_10 HEVC/AVC video.
>>
>> Signed-off-by: Randy Li <ayaka@soulik.info>
>>
>> v4l2
>> ---
>> 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 ++++++++++++++++++++++++++
> You need to include the formats in pixfmt.rst in order to compile the
> documentation.
>
> $ make htmldocs
>
> And you'll find it in Documentation/output/media/uapi/v4l/v4l2.html .
>
> In Debian you'll need to install sphinx-common and python3-sphinx-rtd-theme
> .
OK, I would fix them in new version.
The view of byte order for P010 serial is left empty, it is a little
hard for me to use flat-table to draw them. Is there possible to use
something like latex to do this job?
>
> Regarding P010 and the rest --- I'm fine with that, considering also that
> NV12 was never a great name for a format...
>
next prev parent reply other threads:[~2017-01-05 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 16:29 [PATCH v2 0/2] Add pixel formats for 10/16 bits YUV video Randy Li
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-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 [this message]
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=9a7e7ffd-27d5-0fff-2be5-03f14cc78683@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=sakari.ailus@iki.fi \
--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).