Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
從我的 iPad 傳送 > Mauro Carvalho Chehab 於 2017年2月3日 下午10:04 寫道： > > Em Thu, 5 Jan 2017 20:27:17 +0200 > Sakari Ailus escreveu: > >> Hi Randy, >> >>> On Thu, Jan 05, 2017 at 11:22:26PM +0800, ayaka wrote: >>> >>> 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 > > 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? >> >> Hmm. Not as far as I know. We recently switched from DocBook mostly due to >> ReST being more simple to use AFAIU. I think LaTeX output could be produced >> ReST, that might not be very helpful here though. > > No, you can't use LaTeX, as it won't be properly displayed on all output > formats. There are a few options to define tables in ReST, but we prefer > using flat-table because the other formats are harder to maintain at the > V4L2 uAPI documentation. > > Just one note about this series: it won't be merged upstream until > someone adds a driver needing those pixel formats. > I made a mistake, the pixel format I want is not P010, I would post a new patch for that. > Regards, > Mauro > > > Thanks, > Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
Em Thu, 5 Jan 2017 20:27:17 +0200 Sakari Ailus escreveu: > Hi Randy, > > On Thu, Jan 05, 2017 at 11:22:26PM +0800, ayaka wrote: > > > > > > 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 > > >> > > >>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? > > Hmm. Not as far as I know. We recently switched from DocBook mostly due to > ReST being more simple to use AFAIU. I think LaTeX output could be produced > ReST, that might not be very helpful here though. No, you can't use LaTeX, as it won't be properly displayed on all output formats. There are a few options to define tables in ReST, but we prefer using flat-table because the other formats are harder to maintain at the V4L2 uAPI documentation. Just one note about this series: it won't be merged upstream until someone adds a driver needing those pixel formats. Regards, Mauro Thanks, Mauro -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
Hi Randy, On Thu, Jan 05, 2017 at 11:22:26PM +0800, ayaka wrote: > > > 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 > >> > >>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? Hmm. Not as far as I know. We recently switched from DocBook mostly due to ReST being more simple to use AFAIU. I think LaTeX output could be produced ReST, that might not be very helpful here though. > > > >Regarding P010 and the rest --- I'm fine with that, considering also that > >NV12 was never a great name for a format... > > > -- Kind regards, Sakari Ailus e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
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 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... -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
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 > > 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 . Regarding P010 and the rest --- I'm fine with that, considering also that NV12 was never a great name for a format... -- Kind regards, Sakari Ailus e-mail: sakari.ai...@iki.fi XMPP: sai...@retiisi.org.uk -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH v2 2/2] [media] v4l: Add 10/16-bits per channel YUV pixel formats
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
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 ++
include/uapi/linux/videodev2.h| 4 +
5 files changed, 446 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
diff --git a/Documentation/media/uapi/v4l/pixfmt-p010.rst
b/Documentation/media/uapi/v4l/pixfmt-p010.rst
new file mode 100644
index 000..82b300c
--- /dev/null
+++ b/Documentation/media/uapi/v4l/pixfmt-p010.rst
@@ -0,0 +1,86 @@
+.. -*- coding: utf-8; mode: rst -*-
+
+.. _V4L2-PIX-FMT-P010:
+
+**
+V4L2_PIX_FMT_P010 ('P010')
+**
+
+
+V4L2_PIX_FMT_P010
+Formats with ½ horizontal and vertical chroma resolution. One luminance and
+one chrominance plane with alternating
+chroma samples as simliar to ``V4L2_PIX_FMT_NV12``
+
+
+Description
+===
+
+It is a two-plane versions of the YUV 4:2:0 format. The three
+components are separated into two sub-images or planes. The Y plane is
+first. The Y plane has 10 bits per pixel. For ``V4L2_PIX_FMT_P010``, a
+combined CbCr plane immediately follows the Y plane in memory. The CbCr
+plane is the same width, in bytes, as the Y plane (and of the image),
+but is half as tall in pixels. Each CbCr pair belongs to four pixels.
+For example, Cb\ :sub:`0`/Cr\ :sub:`0` belongs to Y'\ :sub:`00`,
+Y'\ :sub:`01`, Y'\ :sub:`10`, Y'\ :sub:`11`.
+If the Y plane has pad bytes after each row, then the CbCr plane has as
+many pad bytes after its rows.
+
+
+**Color Sample Location..**
+
+.. flat-table::
+:header-rows: 0
+:stub-columns: 0
+
+* -
+ - 0
+ -
+ - 1
+ - 2
+ -
+ - 3
+* - 0
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
+* -
+ -
+ - C
+ -
+ -
+ - C
+ -
+* - 1
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
+* -
+* - 2
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
+* -
+ -
+ - C
+ -
+ -
+ - C
+ -
+* - 3
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
diff --git a/Documentation/media/uapi/v4l/pixfmt-p010m.rst
b/Documentation/media/uapi/v4l/pixfmt-p010m.rst
new file mode 100644
index 000..80194a1
--- /dev/null
+++ b/Documentation/media/uapi/v4l/pixfmt-p010m.rst
@@ -0,0 +1,94 @@
+.. -*- coding: utf-8; mode: rst -*-
+
+.. _V4L2-PIX-FMT-P010M:
+
+***
+V4L2_PIX_FMT_P010 ('P010')
+***
+
+
+V4L2_PIX_FMT_P010M
+Variation of ``V4L2_PIX_FMT_P010`` with planes non contiguous in memory.
+
+
+Description
+===
+
+This is a multi-planar, two-plane version of the YUV 4:2:0 format. The
+three components are separated into two sub-images or planes.
+``V4L2_PIX_FMT_P010M`` differs from ``V4L2_PIX_FMT_P010`` in that the
+two planes are non-contiguous in memory, i.e. the chroma plane do not
+necessarily immediately follows the luma plane. The luminance data
+occupies the first plane. The Y plane has one byte per pixel. In the
+second plane there is a chrominance data with alternating chroma
+samples. The CbCr plane is the same width, in bytes, as the Y plane (and
+of the image), but is half as tall in pixels. Each CbCr pair belongs to
+four pixels. For example, Cb\ :sub:`0`/Cr\ :sub:`0` belongs to
+Y'\ :sub:`00`, Y'\ :sub:`01`, Y'\ :sub:`10`, Y'\ :sub:`11`.
+
+``V4L2_PIX_FMT_P010M`` is intended to be used only in drivers and
+applications that support the multi-planar API, described in
+:ref:`planar-apis`.
+
+If the Y plane has pad bytes after each row, then the CbCr plane has as
+many pad bytes after its rows.
+
+**Color Sample Location..**
+
+
+
+.. flat-table::
+:header-rows: 0
+:stub-columns: 0
+
+* -
+ - 0
+ -
+ - 1
+ - 2
+ -
+ - 3
+* - 0
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
+* -
+ -
+ - C
+ -
+ -
+ - C
+ -
+* - 1
+ - Y
+ -
+ - Y
+ - Y
+ -
+ - Y
+* -
+
