<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/media/pci/intel, branch linux-4.20.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.20.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.20.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-11-06T12:11:59Z</updated>
<entry>
<title>media: ipu3-cio2: Use cio2_queues_exit</title>
<updated>2018-11-06T12:11:59Z</updated>
<author>
<name>Sakari Ailus</name>
</author>
<published>2018-10-10T08:04:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4e26f692e2e2aa4d7d6ddb3c4d3dec17f45d6495'/>
<id>urn:sha1:4e26f692e2e2aa4d7d6ddb3c4d3dec17f45d6495</id>
<content type='text'>
The ipu3-cio2 driver has a function to tear down video devices as well as
the associated video buffer queues. Use it.

Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Tested-by: Bingbu Cao &lt;bingbu.cao@intel.com&gt;
Reviewed-by: Bingbu Cao &lt;bingbu.cao@intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: ipu3-cio2: Unregister device nodes first, then release resources</title>
<updated>2018-11-06T12:11:36Z</updated>
<author>
<name>Sakari Ailus</name>
</author>
<published>2018-10-10T08:01:05Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=32388d6ef7cffc7d8291b67f8dfa26acd45217fd'/>
<id>urn:sha1:32388d6ef7cffc7d8291b67f8dfa26acd45217fd</id>
<content type='text'>
While there are issues related to object lifetime management, unregister
the media device first, followed immediately by other device nodes when
the driver is being unbound. Only then the resources needed by the driver
may be released. This is slightly safer.

Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Tested-by: Bingbu Cao &lt;bingbu.cao@intel.com&gt;
Reviewed-by: Bingbu Cao &lt;bingbu.cao@intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l: mediabus: Recognise CSI-2 D-PHY and C-PHY</title>
<updated>2018-10-04T20:06:15Z</updated>
<author>
<name>Sakari Ailus</name>
</author>
<published>2018-07-03T21:19:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d95e7ed07ed29715a801a3d33b2ad2a6fb26ee3'/>
<id>urn:sha1:2d95e7ed07ed29715a801a3d33b2ad2a6fb26ee3</id>
<content type='text'>
The CSI-2 bus may use either D-PHY or C-PHY. Make this visible in media
bus enum.

Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Tested-by: Steve Longerbeam &lt;steve_longerbeam@mentor.com&gt;
Tested-by: Jacopo Mondi &lt;jacopo+renesas@jmondi.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: platform: Switch to v4l2_async_notifier_add_subdev</title>
<updated>2018-10-04T19:55:38Z</updated>
<author>
<name>Steve Longerbeam</name>
</author>
<published>2018-09-29T19:54:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d079f94c90469f413920b9f2b201537fac2ceb06'/>
<id>urn:sha1:d079f94c90469f413920b9f2b201537fac2ceb06</id>
<content type='text'>
Switch all media platform drivers to call v4l2_async_notifier_add_subdev()
to add asd's to a notifier, in place of referencing the notifier-&gt;subdevs[]
array. These drivers also must now call v4l2_async_notifier_init() before
adding asd's to their notifiers.

There may still be cases where a platform driver maintains a list of
asd's that is a duplicate of the notifier asd_list, in which case its
possible the platform driver list can be removed, and can reference the
notifier asd_list instead. One example of where a duplicate list has
been removed in this patch is xilinx-vipp.c. If there are such cases
remaining, those drivers should be optimized to remove the duplicate
platform driver asd lists.

None of the changes to the platform drivers in this patch have been
tested. Verify that the async subdevices needed by the platform are
bound at load time, and that the driver unloads and reloads correctly
with no memory leaking of asd objects.

Suggested-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Steve Longerbeam &lt;slongerbeam@gmail.com&gt;
Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: v4l2-fwnode: Switch to v4l2_async_notifier_add_subdev</title>
<updated>2018-10-04T19:33:09Z</updated>
<author>
<name>Steve Longerbeam</name>
</author>
<published>2018-09-29T19:54:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eae2aed1eab9bf08146403ac702517d2e4fe932e'/>
<id>urn:sha1:eae2aed1eab9bf08146403ac702517d2e4fe932e</id>
<content type='text'>
The fwnode endpoint and reference parsing functions in v4l2-fwnode.c
are modified to make use of v4l2_async_notifier_add_subdev().
As a result the notifier-&gt;subdevs array is no longer allocated or
re-allocated, and by extension the max_subdevs value is also no
longer needed.

Callers of the fwnode endpoint and reference parsing functions must now
first initialize the notifier with a call to v4l2_async_notifier_init().
This includes the function v4l2_async_register_subdev_sensor_common(),
and the intel-ipu3, omap3isp, and rcar-vin drivers.

Since the notifier-&gt;subdevs array is no longer allocated in the
fwnode endpoint and reference parsing functions, the callers of
those functions must never reference that array, since it is now
NULL. Of the drivers that make use of the fwnode/ref parsing,
only the intel-ipu3 driver references the -&gt;subdevs[] array,
(in the notifier completion callback), so that driver has been
modified to iterate through the notifier-&gt;asd_list instead.

Signed-off-by: Steve Longerbeam &lt;slongerbeam@gmail.com&gt;
Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: use strscpy() instead of strlcpy()</title>
<updated>2018-09-11T17:32:17Z</updated>
<author>
<name>Mauro Carvalho Chehab</name>
</author>
<published>2018-09-10T12:19:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c0decac19da3906d9b66291e57b7759489e1170f'/>
<id>urn:sha1:c0decac19da3906d9b66291e57b7759489e1170f</id>
<content type='text'>
The implementation of strscpy() is more robust and safer.

That's now the recommended way to copy NUL terminated strings.

Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
Reviewed-by: Kees Cook &lt;keescook@chromium.org&gt;
Acked-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: ipu3-cio2: Use dma_zalloc_coherent to replace dma_alloc_coherent + memset</title>
<updated>2018-08-31T13:24:33Z</updated>
<author>
<name>zhong jiang</name>
</author>
<published>2018-08-18T15:16:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1526dbeb54f202e9fa2de660fd18030ebaa99f49'/>
<id>urn:sha1:1526dbeb54f202e9fa2de660fd18030ebaa99f49</id>
<content type='text'>
dma_zalloc_coherent has implemented the dma_alloc_coherent() + memset(),
We prefer to dma_zalloc_coherent instead of open-codeing.

Signed-off-by: zhong jiang &lt;zhongjiang@huawei.com&gt;
Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: Remove depends on HAS_DMA in case of platform dependency</title>
<updated>2018-05-28T20:17:08Z</updated>
<author>
<name>Geert Uytterhoeven</name>
</author>
<published>2018-05-17T17:18:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4cff79e933265e2fb9f00cefefaf5af85d9147f7'/>
<id>urn:sha1:4cff79e933265e2fb9f00cefefaf5af85d9147f7</id>
<content type='text'>
Remove dependencies on HAS_DMA where a Kconfig symbol depends on another
symbol that implies HAS_DMA, and, optionally, on "|| COMPILE_TEST".
In most cases this other symbol is an architecture or platform specific
symbol, or PCI.

Generic symbols and drivers without platform dependencies keep their
dependencies on HAS_DMA, to prevent compiling subsystems or drivers that
cannot work anyway.

This simplifies the dependencies, and allows to improve compile-testing.

Note:
  - The various VIDEOBUF*DMA* symbols had to loose their dependencies on
    HAS_DMA, as they are selected by several individual drivers.

Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Reviewed-by: Mark Brown &lt;broonie@kernel.org&gt;
Acked-by: Robin Murphy &lt;robin.murphy@arm.com&gt;
Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: intel-ipu3: Kconfig coding style issue</title>
<updated>2018-05-09T20:26:23Z</updated>
<author>
<name>Brad Love</name>
</author>
<published>2018-05-02T23:19:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9115df47d15f713285f292dc58b2275d10dc1977'/>
<id>urn:sha1:9115df47d15f713285f292dc58b2275d10dc1977</id>
<content type='text'>
Kconfig Help statements are two-spaced after a single tab.

The incorrect spacing breaks menuconfig on older kernels.

Signed-off-by: Brad Love &lt;brad@nextdimension.cc&gt;
Acked-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Hans Verkuil &lt;hans.verkuil@cisco.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
<entry>
<title>media: intel-ipu3: cio2: Handle IRQs until INT_STS is cleared</title>
<updated>2018-05-09T19:45:08Z</updated>
<author>
<name>Bingbu Cao</name>
</author>
<published>2018-04-30T14:30:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=09f20f2bca914e6f89b78237fd938152dfe9da0f'/>
<id>urn:sha1:09f20f2bca914e6f89b78237fd938152dfe9da0f</id>
<content type='text'>
Interrupt behavior shows that some time the frame end and frame start of
next frame is unstable and can range from several to hundreds of
micro-sec. In the case of ~10us, isr may not clear next sof interrupt
status in single handling, which prevents new interrupts from coming.

Fix this by handling all pending IRQs before exiting isr, so any abnormal
behavior results from very short interrupt status changes is protected.

Signed-off-by: Bingbu Cao &lt;bingbu.cao@intel.com&gt;
Signed-off-by: Andy Yeh &lt;andy.yeh@intel.com&gt;
Signed-off-by: Yong Zhi &lt;yong.zhi@intel.com&gt;
Signed-off-by: Sakari Ailus &lt;sakari.ailus@linux.intel.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+samsung@kernel.org&gt;
</content>
</entry>
</feed>
