<feed xmlns='http://www.w3.org/2005/Atom'>
<title>blackbird-op-linux/Documentation/media/uapi/v4l, branch master</title>
<subtitle>Blackbird™ Linux sources for OpenPOWER</subtitle>
<id>https://git.raptorcs.com/git/blackbird-op-linux/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/blackbird-op-linux/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/'/>
<updated>2020-01-08T13:25:13+00:00</updated>
<entry>
<title>media: v4l2: Fix fourcc names for 12b and 14b packed bayer</title>
<updated>2020-01-08T13:25:13+00:00</updated>
<author>
<name>Daniel Gomez</name>
<email>daniel@qtec.com</email>
</author>
<published>2019-12-06T09:18:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=ef9534c585e0ff8f88fd17d198cfb483d9f86b33'/>
<id>urn:sha1:ef9534c585e0ff8f88fd17d198cfb483d9f86b33</id>
<content type='text'>
Fix documentation fourcc names for the 12-bit and 14-bit packed Bayer formats.

Signed-off-by: Daniel Gomez &lt;daniel@qtec.com&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: Revert "media: v4l2: Fix fourcc names for BAYER12P"</title>
<updated>2020-01-08T13:23:08+00:00</updated>
<author>
<name>Hans Verkuil</name>
<email>hverkuil-cisco@xs4all.nl</email>
</author>
<published>2020-01-06T08:38:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=bed7bdb6ae3c5d44f62a984471b1d161d06d7810'/>
<id>urn:sha1:bed7bdb6ae3c5d44f62a984471b1d161d06d7810</id>
<content type='text'>
This reverts commit 2b016c47f48f3d144816645822a09995063313a1.

Wrong patch was merged, revert this first before applying the right
patch.

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: vidioc-enum-fmt.rst: clarify format preference</title>
<updated>2019-12-16T09:24:55+00:00</updated>
<author>
<name>Ezequiel Garcia</name>
<email>ezequiel@collabora.com</email>
</author>
<published>2019-12-05T14:24:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=0fb36893c6c129d48965332a23fa4ea6b075ad0c'/>
<id>urn:sha1:0fb36893c6c129d48965332a23fa4ea6b075ad0c</id>
<content type='text'>
It has been decided to use the ENUM_FMT index value
as a hint for driver preference. This is defined purposedly
in a very liberal way, letting drivers define what "preference"
means.

For instance, the Hantro VPU driver indicates additional
processing to output a given format, and thus implicates
more CPU usage, which is enumerated after native (non-processed)
formats.

Signed-off-by: Ezequiel Garcia &lt;ezequiel@collabora.com&gt;
Reviewed-by: Boris Brezillon &lt;boris.brezillon@collabora.com&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: pixfmt-tch-td16/tu16.rst: document that this is little endian</title>
<updated>2019-12-16T09:21:14+00:00</updated>
<author>
<name>Hans Verkuil</name>
<email>hverkuil-cisco@xs4all.nl</email>
</author>
<published>2019-11-19T10:51:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=94010145a58f169e73e6c7e88b57017112814955'/>
<id>urn:sha1:94010145a58f169e73e6c7e88b57017112814955</id>
<content type='text'>
Testing with the rmi_f54 driver on the Lenovo X1 Carbon 6th gen
laptop showed that the data is in little endian format. Update
the documentation accordingly.

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: ivtv/cx18: remove ivtvdriver.org references</title>
<updated>2019-12-13T08:27:09+00:00</updated>
<author>
<name>Hans Verkuil</name>
<email>hverkuil-cisco@xs4all.nl</email>
</author>
<published>2019-12-04T11:57:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=55f240a21eb13717da2872ebef2eb0af4007a5bd'/>
<id>urn:sha1:55f240a21eb13717da2872ebef2eb0af4007a5bd</id>
<content type='text'>
That URL is no longer valid, so either remove references to it or
replace it with linuxtv.org.

Rather than updating the URL I've just dropped the cx18.rst driver
documentation since it was really out of date.

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Acked-by: awalls@md.metrocast.net
Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l2: Fix fourcc names for BAYER12P</title>
<updated>2019-12-13T08:24:01+00:00</updated>
<author>
<name>Daniel Gomez</name>
<email>daniel@qtec.com</email>
</author>
<published>2019-12-03T15:12:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=2b016c47f48f3d144816645822a09995063313a1'/>
<id>urn:sha1:2b016c47f48f3d144816645822a09995063313a1</id>
<content type='text'>
Fix documentation fourcc names for the 12-bit packed Bayer formats.

Signed-off-by: Daniel Gomez &lt;daniel@qtec.com&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: vidioc-g-dv-timings.rst: fix wrong porch</title>
<updated>2019-12-13T08:23:09+00:00</updated>
<author>
<name>Hans Verkuil</name>
<email>hverkuil-cisco@xs4all.nl</email>
</author>
<published>2019-12-02T11:46:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=7b575b6d8de03ca6b6ab85fa1dd53d2ce921a4a0'/>
<id>urn:sha1:7b575b6d8de03ca6b6ab85fa1dd53d2ce921a4a0</id>
<content type='text'>
It is the vfrontporch of field 1 that is one half-line longer,
not the backporch.

The order of the vertical signals in an interlaced system is:

Field 1:

vsync
vbackporch
active video of field 1
vfrontporch + 0.5

Field 2:

il_vsync
il_vbackporch - 0.5
active video of field 2
il_vfrontporch

Interlaced systems that use HALF_LINE set the il_ fields as follows:

il_vfrontporch = vfrontporch
il_vsync = vsync
il_vbackporch = vbackporch + 1

So the total vertical blanking for field 1 is:

	vsync + vbackporch + vfrontporch + 0.5

and for field 2:

	vsync + vbackporch + 1 + vfrontporch - 0.5 ==
	vsync + vbackporch + vfrontporch + 0.5

So each field has the same number of half-lines.

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: Documentation: media: *_DEFAULT targets for subdevs</title>
<updated>2019-11-10T16:49:27+00:00</updated>
<author>
<name>Ricardo Ribalda Delgado</name>
<email>ribalda@kernel.org</email>
</author>
<published>2019-10-25T09:47:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=4edead77fa16ac4ec880ebceed83da2415401d18'/>
<id>urn:sha1:4edead77fa16ac4ec880ebceed83da2415401d18</id>
<content type='text'>
Some sensors have optical blanking areas, this is, pixels that are
painted and do not account for light, only noise.

These special pixels are very useful for calibrating the sensor, but
should not be displayed on a DEFAULT target.

Signed-off-by: Ricardo Ribalda Delgado &lt;ribalda@kernel.org&gt;
Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: uapi: h264: clarify expected scaling_list_4x4/8x8 order</title>
<updated>2019-11-09T07:46:07+00:00</updated>
<author>
<name>Jonas Karlman</name>
<email>jonas@kwiboo.se</email>
</author>
<published>2019-10-29T00:00:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=0b0393d59eb4a58456d128a782c42f924eedab16'/>
<id>urn:sha1:0b0393d59eb4a58456d128a782c42f924eedab16</id>
<content type='text'>
Clarify that the expected order of scaling lists should follow the order
they are listed in the H264 standard.

The expected scaling list order,
for 4x4: Intra Y, Intra Cb, Intra Cr, Inter Y, Inter Cb, Inter Cr,
for 8x8: Intra Y, Inter Y, Intra Cb, Inter Cb, Intra Cr, Inter Cr.

Also clarify that the values in a scaling list should be in matrix order,
the same value order that vaapi, vdpau and nvdec use.

Signed-off-by: Jonas Karlman &lt;jonas@kwiboo.se&gt;
Reviewed-by: Philipp Zabel &lt;p.zabel@pengutronix.de&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: Documentation: v42l_core: v4l2_ext_control</title>
<updated>2019-11-08T06:42:58+00:00</updated>
<author>
<name>Ricardo Ribalda Delgado</name>
<email>ribalda@kernel.org</email>
</author>
<published>2019-11-04T13:09:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/blackbird-op-linux/commit/?id=8508a2d519ed190a77061c5159b000f1035b3522'/>
<id>urn:sha1:8508a2d519ed190a77061c5159b000f1035b3522</id>
<content type='text'>
Describe p_area field from v4l2_ext_ctrl

Signed-off-by: Ricardo Ribalda Delgado &lt;ribalda@kernel.org&gt;
Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@kernel.org&gt;
</content>
</entry>
</feed>
