Fix those warnings:

	Documentation/media/uapi/cec/cec-ioc-dqevent.rst:124: WARNING: c:func reference target not found: clock_gettime(2)

By replacing it with the right function name, using this shell script:

	for i in `find Documentation/media -type f`; do sed 's,clock_gettime(2),clock_gettime,' <$i >a && mv a $i; done

Please notice that this will make the nitpick mode to shut up
complaining about that, becasue clock_gettime is on its exclude list,
but the cross reference will be undefined until someone documents
this function at the core documentation.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The :c:type: references point to the structure name, and not to
struct foo.

Fixed via this shell script:

	for i in `find Documentation/media -type f`; do perl -ne 'if (s/\:c\:type\:\`struct\s*(\S+)\`/struct :c:type:`$1`/) { s/struct\s+struct/struct/;  s/(struct\s+\:c\:type\:\`\S+\`)\s+structure/$1/;  } print $_' <$i >a && mv a $i; done
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Instead of using c:type:`struct foo <foo>`, use:
	struct c:type:`foo`

This patch was generated via this shell script:

	for i in `find Documentation/media -type f`; do perl -ne 'if (m/\:c\:type\:\`struct\s+(\S+)\s*\<(\S+)\>\`/) { $s=$1; $r=$2; if ($s eq $r) { s/\:c\:type\:\`struct\s+(\S+)\s*\<(\S+)\>\`/struct :c:type:`$2`/; s/struct\s+struct/struct/;  s/(struct\s+\:c\:type\:\`\S+\`)\s+structure/$1/;  }} print $_' <$i >a && mv a $i; done
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Change the parse-headers.pl and the corresponding files to use
the C domain for enum references.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The V4L version 1 structures had long gone from the Linux Kernel.
It doesn't make sense to use cross-references for them, as they
won't be found.

So, get rid of them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

instead of declaring the uAPI structs using usual refs, e. g.:
	.. _foo-struct:

Use the C domain way:
	.. c:type:: foo_struct

This way, the kAPI documentation can use cross-references to
point to the uAPI symbols.

That solves about ~100 undefined warnings like:
	WARNING: c:type reference target not found: foo_struct
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

/devel/v4l/patchwork/Documentation/media/uapi/v4l/extended-controls.rst:2116: WARNING: Inline literal start-string without end-string.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

This field was never documented, and neither was it mentioned that
it should be zeroed by the application.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

V4L2_CTRL_FLAG_VOLATILE behaviour when V4L2_CTRL_FLAG_EXECUTE_ON_WRITE
is set was not properly explained.

Also set some hyperlink to ease the Documentation browsing.

Credit-to: Hans Verkuil <hansverk@cisco.com>

[mchehab@s-opensource.com: fix a trivial merge conflict]
Reported-by: NDimitrios Katsaros <patcherwork@gmail.com>
Signed-off-by: NRicardo Ribalda Delgado <ricardo.ribalda@gmail.com>
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Document that the cropping ioctls can return ENODATA if the operation
isn't supported for the current input or output.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Instead of referring to Y', Cb and Cr, it referred to Yc', Cbc and
Crc, which were accidentally copied from the BT.2020 constant luminance
text.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The text of the note included text that shouldn't have been part
of the note. Move that out of the note into the proper place.

[mchehab@s-opensource.com: fix a trivial merge conflict]
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The V4L2_YCBCR_ENC_SYCC encoding is identical to V4L2_YCBCR_ENC_601.
Remove V4L2_YCBCR_ENC_SYCC from the documentation since it should not
be used.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The SYCC Y'CbCr encoding is identical to the 601 encoding. Since the
SYCC define is about to be removed for use in the kernel we need to
drop it in the TPG code as well.

This patch also adds a 4th decimal to the 601 conversion matrix.
That was specified by the sYCC spec and it makes sense to use this
across the board.

[mchehab@s-opensource.com: fix conflicts with LaTeX math expression patch]
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The default quantization range of the Y'CbCr encodings of sRGB
and AdobeRGB are full range instead of limited range according to
the corresponding standards.

Fix this in the V4L2_MAP_QUANTIZATION_DEFAULT macro.
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Document the new touch API.
Signed-off-by: NNick Dyer <nick@shmanahar.org>
Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
[hans.verkuil@cisco.com: fix up videodev2.h.rst.exceptions]
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
Acked-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>

On some places, either an space or the second ':' is missing.

Fix them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Name all ioctl references and make them match the ioctls that
are documented. That will improve the cross-reference index,
as it will have all ioctls and syscalls there.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Now that we have an override for the c domain that will do
the right thing for the Kernel, stop abusing on the cpp
domain.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Enrich math formulas by using the Sphinx math. That will allow
using those formulas on pdf documents as well.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

On some places, either an space or the second ':' is missing.

Fix them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

There are several minor issues that are seen when building
PDF on interactive mode.

Fix them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

There are two big tables here that are very hard to adjust its
size.

The first one would fit into one page, but the latex.py logic
at Sphinx auto-switches to longtable when there are more than 30
rows. There's no way to override without coding.

The second one is really big, and won't fit on a single page.
So, it has to use tiny font to fit.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

It is painful to put code/verbatim code in bold. It seems that
the only way is to arrange it like:
	``foo``
	    bar

At least on LaTeX output, when this happens, the "foo" string
is not hidentable/breakable. The entire string should fit into
a single line.

Add a workaround for this ReST limitation by splitting the
foo string into two strings, on separate lines. The output
is not the best, but it works.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

There are still a few tables with wrong columns at the uAPI
docs. Fix them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Sphinx is really pedantic with respect to the order where
table tags and references are created. Putting things at
the wrong order causes troubles.

The order that seems to work is:

	.. raw:: latex

	.. tabularcolumns::

	.. _foo_name:

	.. cssclass: longtable

	.. flat-table::

Reorder the tags to the above order, to avoid troubles, and
fix remaining warnings introduced by media recent patches.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Adjust the tables there to fit inside the page margins.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Several tables are missing column definitions and/or are too big
to fit into the page. Adjust them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The tuner type table misses descriptions for each type. While
most of stuff are obvious, the two SDR definitions aren't.

So, add descriptions to all of them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Adjust simple cases where the columns on some vidioc files
are overriding their neighbours.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The tables don't fit at the page on this file. As noticed
before, Sphinx (or LaTeX?) does a crap job on tables with
cell span, and some work has to be done to make it fit.

Move the see also reference to a footnote, break one paragraph
into two and adjust the table columns to make it visible.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

This table is too big for LaTeX output, and lacks columns
specs for LaTeX format.

Also, it has a hidden column, as there are some cell spans
with the wrong values.

Fix it, so it can be displayed properly on LaTeX/PDF.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Some tables are not properly displayed on LaTeX. Fix them.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

There are two tables with mangled columns. Fix it.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Better adjust the columns for LaTeX output
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

This table has several troubles:
	- a duplicated "struct" on its name;
	- a reference to a V4L version 1 struct that will never
	  point to something (as we got rid of V4L1 API a long
	  time ago);
	- misses hints for LaTeX output (column size and longtable
	  style).

Fix them.

It should be noticed that the first column of this table is
not aligned with the rest. I suspect that this is a bug at
the flat-table extension.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Fix mosto fo the tables there in order to make them fit at the
page size.

There are, however, two exceptions: RGB and YUV big tables,
where adding the raw latex adjustbox caused the tables to not
be properly formatted. I suspect that the problem is because
those are long tables, but not really sure.

The thing is that Sphinx lacks an "adjustbox" tag that would
avoid the raw latex hacks.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

The table there is too big and doesn't have format hints for
LaTeX output.

Fix it.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

One of the tables has wrong column dimentions. Fix it.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>

Better format the tables in a way that will fit inside the
page.
Signed-off-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>