<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/platform/xilinx, branch linux-5.12.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.12.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.12.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2021-02-06T08:18:53Z</updated>
<entry>
<title>media: v4l2-async: Improve v4l2_async_notifier_add_*_subdev() API</title>
<updated>2021-02-06T08:18:53Z</updated>
<author>
<name>Laurent Pinchart</name>
</author>
<published>2021-01-18T01:52:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b01edcbd409cf713ff4516c6e1e057834b4b43d6'/>
<id>urn:sha1:b01edcbd409cf713ff4516c6e1e057834b4b43d6</id>
<content type='text'>
The functions that add an async subdev to an async subdev notifier take
as an argument the size of the container structure they need to
allocate. This is error prone, as passing an invalid size will not be
caught by the compiler. Wrap those functions in macros that take a
container type instead of a size, and cast the returned pointer to the
desired type. The compiler will catch mistakes if the incorrect type is
passed to the macro, as the assignment types won't match.

Signed-off-by: Laurent Pinchart &lt;laurent.pinchart+renesas@ideasonboard.com&gt;
Reviewed-by: Niklas Söderlund &lt;niklas.soderlund+renesas@ragnatech.se&gt;
Reviewed-by: Jacopo Mondi &lt;jacopo+renesas@jmondi.org&gt;
Signed-off-by: Ezequiel Garcia &lt;ezequiel@collabora.com&gt;
Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Reviewed-by: Helen Koike &lt;helen.koike@collabora.com&gt;
Reviewed-by: Tomi Valkeinen &lt;tomi.valkeinen@ideasonboard.com&gt; (core+ti-cal)
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l: xilinx: Add Xilinx MIPI CSI-2 Rx Subsystem driver</title>
<updated>2020-06-23T11:11:46Z</updated>
<author>
<name>Vishal Sagar</name>
</author>
<published>2020-05-27T13:57:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ba5bf51acf0075b193878a56ea3741982391da9c'/>
<id>urn:sha1:ba5bf51acf0075b193878a56ea3741982391da9c</id>
<content type='text'>
The Xilinx MIPI CSI-2 Rx Subsystem soft IP is used to capture images
from MIPI CSI-2 camera sensors and output AXI4-Stream video data ready
for image processing. Please refer to PG232 for details.

The CSI2 Rx controller filters out all packets except for the packets
with data type fixed in hardware. RAW8 packets are always allowed to
pass through.

It is also used to setup and handle interrupts and enable the core. It
logs all the events in respective counters between streaming on and off.

The driver supports only the video format bridge enabled configuration.
Some data types like YUV 422 10bpc, RAW16, RAW20 are supported when the
CSI v2.0 feature is enabled in design. When the VCX feature is enabled,
the maximum number of virtual channels becomes 16 from 4.

Signed-off-by: Vishal Sagar &lt;vishal.sagar@xilinx.com&gt;
Reviewed-by: Hyun Kwon &lt;hyun.kwon@xilinx.com&gt;
Reviewed-by: Luca Ceresoli &lt;luca@lucaceresoli.net&gt;
Signed-off-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: Kconfig files: use select for V4L2 subdevs and MC</title>
<updated>2020-04-14T08:29:05Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2020-03-25T14:36:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=32a363d0b0b142f35512848dc646ee53e0926723'/>
<id>urn:sha1:32a363d0b0b142f35512848dc646ee53e0926723</id>
<content type='text'>
There are lots of drivers that only work when the media controller
and/or the V4L2 subdev APIs are present.

Right now, someone need to first enable those APIs before
using those drivers.

Well, ideally, drivers, should, instead *optionally*
depend on it, in order for PC camera drivers to be able to use
them, but nowadays most drivers are UVC cameras, with don't
require a sensor driver.

So, be it.

Let's instead make them select the MEDIA_CONTROLLER and the
SUBDEV API, in order to make easier for people to be able
of enabling them.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: media/platform: rename VFL_TYPE_GRABBER to _VIDEO</title>
<updated>2020-02-24T15:54:14Z</updated>
<author>
<name>Hans Verkuil</name>
</author>
<published>2020-02-03T11:41:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=70cad4495a7438b07d806b8795ab6c6ef083b737'/>
<id>urn:sha1:70cad4495a7438b07d806b8795ab6c6ef083b737</id>
<content type='text'>
'GRABBER' is a weird name, all other types map to the /dev
device names. Rename to 'VIDEO' to be consistent with the
other types.

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: xilinx: Use dma_request_chan() instead dma_request_slave_channel()</title>
<updated>2020-02-24T15:17:00Z</updated>
<author>
<name>Peter Ujfalusi</name>
</author>
<published>2020-01-10T07:16:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dea0ab3782e302ed2c19522f753bbe2ccf40cbbb'/>
<id>urn:sha1:dea0ab3782e302ed2c19522f753bbe2ccf40cbbb</id>
<content type='text'>
dma_request_slave_channel() is a wrapper on top of dma_request_chan()
eating up the error code.

By using dma_request_chan() directly the driver can support deferred
probing against DMA.

Signed-off-by: Peter Ujfalusi &lt;peter.ujfalusi@ti.com&gt;
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.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: xilinx: Use the correct style for SPDX License Identifier</title>
<updated>2019-11-05T11:30:51Z</updated>
<author>
<name>Nishad Kamdar</name>
</author>
<published>2019-09-07T14:21:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5c2a99480eb8d0fd8775847e31651740b56ba64b'/>
<id>urn:sha1:5c2a99480eb8d0fd8775847e31651740b56ba64b</id>
<content type='text'>
This patch corrects the SPDX License Identifier style
in header files related to Video drivers for Xilinx devices.
For C header files Documentation/process/license-rules.rst
mandates C-like comments (opposed to C source files where
C++ style should be used)

Changes made by using a script provided by Joe Perches here:
https://lkml.org/lkml/2019/2/7/46.

Suggested-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: Nishad Kamdar &lt;nishadkamdar@gmail.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: use the BIT() macro</title>
<updated>2019-08-26T17:08:50Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2019-08-22T14:06:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cce8ccca80d8388982133192d0a6d9dc2e8ed712'/>
<id>urn:sha1:cce8ccca80d8388982133192d0a6d9dc2e8ed712</id>
<content type='text'>
As warned by cppcheck:

	[drivers/media/dvb-frontends/cx24123.c:434]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
	[drivers/media/pci/bt8xx/bttv-input.c:87]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
	[drivers/media/pci/bt8xx/bttv-input.c:98]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour
			...
	[drivers/media/v4l2-core/v4l2-ioctl.c:1391]: (error) Shifting signed 32-bit value by 31 bits is undefined behaviour

There are lots of places where we're doing 1 &lt;&lt; 31. That's bad,
as, depending on the architecture, this has an undefined behavior.

The BIT() macro is already prepared to handle this, so, let's
just switch all "1 &lt;&lt; number" macros by BIT(number) at the header files
with has 1 &lt;&lt; 31.

Reviewed-by: Sylwester Nawrocki &lt;s.nawrocki@samsung.com&gt; # exynos4-is and s3c-camif
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt; # omap3isp, vsp1, xilinx, wl128x and ipu3
Reviewed-by: Benoit Parrot &lt;bparrot@ti.com&gt; # am437x and ti-vpe
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l2-async: Get fwnode reference when putting it to the notifier's list</title>
<updated>2019-07-25T12:01:43Z</updated>
<author>
<name>Sakari Ailus</name>
</author>
<published>2019-04-04T23:43:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=016413d967061fc2eb6798a487b3022bef7698a6'/>
<id>urn:sha1:016413d967061fc2eb6798a487b3022bef7698a6</id>
<content type='text'>
The v4l2_async_notifier_add_fwnode_subdev() did not take a reference of
the added fwnode, relying on the caller to handle that instead, in essence
putting the fwnode to be added if there was an error.

As the reference is eventually released during the notifier cleanup, this
is not intuitive nor logical. Improve this by always getting a reference
when the function succeeds, and the caller releasing the reference when it
does not *itself* need it anymore.

Luckily, perhaps, there were just a handful of callers using the function.

Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Reviewed-by: Jacopo Mondi &lt;jacopo+renesas@jmondi.org&gt;
Tested-by: Niklas Söderlund &lt;niklas.soderlund+renesas@ragnatech.se&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: xilinx: set device_caps in struct video_device</title>
<updated>2019-07-22T19:08:47Z</updated>
<author>
<name>Hans Verkuil</name>
</author>
<published>2019-06-26T07:15:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b1df3129b71979b1196935a1e29bfe9ac7f28ab6'/>
<id>urn:sha1:b1df3129b71979b1196935a1e29bfe9ac7f28ab6</id>
<content type='text'>
Instead of filling in the struct v4l2_capability device_caps
field, fill in the struct video_device device_caps field.

That way the V4L2 core knows what the capabilities of the
video device are.

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: media/platform: don't set description in ENUM_FMT</title>
<updated>2019-07-22T18:43:59Z</updated>
<author>
<name>Hans Verkuil</name>
</author>
<published>2019-06-11T14:25:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=59fe916c84f891aab35019adc45377a10f5690b1'/>
<id>urn:sha1:59fe916c84f891aab35019adc45377a10f5690b1</id>
<content type='text'>
The V4L2 core sets the format description and flags for the driver in order
to ensure consistent naming.

So drop the strscpy of the description in drivers. Also remove any
description strings in driver-internal structures since those are
no longer needed.

And in am437x-vpfe.c drop an unnecessary f-&gt;type assignment in
vpfe_enum_fmt().

Signed-off-by: Hans Verkuil &lt;hverkuil-cisco@xs4all.nl&gt;
Acked-by: Benoit Parrot &lt;bparrot@ti.com&gt;
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
[hverkuil-cisco@xs4all.nl: addressed some small suggestions from Laurent]
Acked-by: Lad, Prabhakar &lt;prabhakar.csengg@gmail.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
</feed>
