This message is generated daily by a cron job that builds media_tree for
the kernels and architectures in the list below.
Results of the daily build of media_tree:
date: Sat Oct 7 05:00:07 CEST 2017
media-tree git hash:c1301077213d4dca34f01fc372b64d3c4a49a437
media_build gi
The CIO2 driver exposes V4L2, V4L2 sub-device and Media controller interfaces
to the user space.
This series was tested on Kaby Lake based platform with 2 sensor configurations,
media topology was pasted at end for reference.
===
= history =
===
Version 5:
- cio2_vb2_start_stream
Add IPU3 specific formats:
V4L2_PIX_FMT_IPU3_SBGGR10
V4L2_PIX_FMT_IPU3_SGBRG10
V4L2_PIX_FMT_IPU3_SGRBG10
V4L2_PIX_FMT_IPU3_SRGGB10
Signed-off-by: Yong Zhi
---
drivers/media/v4l2-core/v4l2-ioctl.c | 4
include/uapi/linux/videodev2.h | 6 ++
2 files
This patch adds CIO2 CSI-2 device driver for
Intel's IPU3 camera sub-system support.
Signed-off-by: Yong Zhi
Signed-off-by: Hyungwoo Yang
Signed-off-by: Rajmohan Mani
Signed-off-by: Vijaykumar Ramya
---
drivers/media/pci/Kconfig|2 +
drivers/media/pci/Makefile
The formats added by this patch are:
V4L2_PIX_FMT_IPU3_SBGGR10
V4L2_PIX_FMT_IPU3_SGBRG10
V4L2_PIX_FMT_IPU3_SGRBG10
V4L2_PIX_FMT_IPU3_SRGGB10
Signed-off-by: Yong Zhi
Signed-off-by: Hyungwoo Yang
---
Documentation/media/uapi/v4l/pixfmt-rgb.rst| 1 +
.../media/uapi/v4l/p
Check if firmware is allocated before requesting firmware instead of
requesting firmware only to release it if firmware is not allocated.
Signed-off-by: Shuah Khan
---
drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/dri
This patch series fixes inefficiencies and lock contention in the request
firmware paths.
Shuah Khan (2):
media: s5p-mfc: check for firmware allocation before requesting
firmware
media: s5p-mfc: fix lock confection - request_firmware() once and keep
state
drivers/media/platform/s5p-m
Driver calls request_firmware() whenever the device is opened for the
first time. As the device gets opened and closed, dev->num_inst == 1
is true several times. This is not necessary since the firmware is saved
in the fw_buf. s5p_mfc_load_firmware() copies the buffer returned by
the request_firmwa
Hi, Tomasz,
Sorry for the late reply. I will omit the points that have been fixed in v4 or
discussed earlier by either Tuukka or Sakari
(https://patchwork.linuxtv.org/patch/41665)
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org
On Fri, Sep 29, 2017 at 11:23:40AM +0300, Sakari Ailus wrote:
> Port and endpoint numbering has been omitted in DT binding documentation
> for a large number of devices. Also common properties the device uses have
> been missed in binding documentation. Make it explicit that these things
> need to
Hi, Sakari,
Thanks for the review.
> -Original Message-
> From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
> ow...@vger.kernel.org] On Behalf Of Sakari Ailus
> Sent: Tuesday, July 11, 2017 3:34 AM
> To: Zhi, Yong
> Cc: linux-media@vger.kernel.org; sakari.ai...@linux.intel.com
On Fri, Oct 06, 2017 at 12:14:01PM +0200, Philipp Zabel wrote:
> On Fri, 2017-10-06 at 10:49 +0300, Sakari Ailus wrote:
> > On Thu, Oct 05, 2017 at 10:21:16AM -0700, Tim Harvey wrote:
> > > Greetings,
> > >
> > > I'm working on a HDMI receiver driver for the TDA1997x
> > > (https://lwn.net/Article
Hi Devid,
On Wed, Oct 04, 2017 at 01:23:36AM +0200, Devid Antonio Filoni wrote:
> I was not able to properly test this patch on my Lenovo Miix 310 due to other
> issues with atomisp, the output is the same as ov2680 driver (OVTI2680) which
> is very similar to ov5648. As reported by dmesg, atomisp
Hi Mauro,
On Wed, Sep 27, 2017 at 07:23:47PM -0300, Mauro Carvalho Chehab wrote:
> As we now have a glossary, some terms used on open.rst
> require adjustments.
>
> Acked-by: Hans Verkuil
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media/uapi/v4l/open.rst | 12 ++--
>
Add DT binding for the HW IR decoder embedded in SMP86xx/SMP87xx.
Signed-off-by: Marc Gonzalez
---
.../devicetree/bindings/media/tango-ir.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/tango-ir.txt
diff --git
From: Mans Rullgard
The tango HW IR decoder supports NEC, RC-5, RC-6 protocols.
Signed-off-by: Mans Rullgard
Signed-off-by: Marc Gonzalez
---
Changes between v7 and v8
* RC_MAP_TANGO as default keymap
* Define and use NEC_ANY macro
---
drivers/media/rc/Kconfig| 10 ++
drivers/media/rc/Ma
Add a keymap for the Sigma Designs Vantage (dev board) remote control.
Signed-off-by: Marc Gonzalez
---
Changes between v7 and v8
* Add legalese boiler plate
* Define RC_PROTO_NECX
* Move RC_MAP_TANGO to alphabetical order
---
drivers/media/rc/keymaps/Makefile | 1 +
drivers/media/rc/keymaps/
Hi Mauro,
On Wed, Sep 27, 2017 at 07:23:46PM -0300, Mauro Carvalho Chehab wrote:
> When we added support for omap3, back in 2010, we added a new
> type of V4L2 devices that aren't fully controlled via the V4L2
> device node.
>
> Yet, we have never clearly documented in the V4L2 specification
> th
Hi Mauro,
On Fri, Oct 06, 2017 at 01:22:29PM +0300, Sakari Ailus wrote:
> > +V4L2 device node
> > + A device node that is associated to a V4L2 main driver,
> > + as specified in :ref:`v4l2_device_naming`.
I think we need to name the interface, not so much their instances.
How about addin
On Thu 2017-10-05 00:50:48, Sakari Ailus wrote:
> Parse async sub-devices related to the sensor by switching the async
> sub-device registration function.
>
> Signed-off-by: Sakari Ailus
> Acked-by: Hans Verkuil
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(ces
On Thu 2017-10-05 00:50:47, Sakari Ailus wrote:
> Parse async sub-devices related to the sensor by switching the async
> sub-device registration function.
>
> These types devices aren't directly related to the sensor, but are
> nevertheless handled by the smiapp driver due to the relationship of t
On 06/10/2017 12:47, Måns Rullgård wrote:
> Sean Young writes:
>
>> Looks great, just some minor nitpicks.
>>
>> I think you need a header with copyright statement and GPL version(s).
>
> Is this even copyrightable?
My thoughts, exactly.
I don't mind *not* providing a copyright statement and G
Sean Young writes:
> Hi Marc,
>
> Looks great, just some minor nitpicks.
>
> On Thu, Oct 05, 2017 at 04:54:11PM +0200, Marc Gonzalez wrote:
>> Add a keymap for the Sigma Designs Vantage (dev board) remote control.
>>
>> Signed-off-by: Marc Gonzalez
>> ---
>> drivers/media/rc/keymaps/Makefile
to
> help improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Dmitry-Osipenko/staging-Introduce-NVIDIA-Tegra20-video-decoder-driver/20171006-101015
> config: ia64-allmodconfig (attached as .config)
> compiler: ia64-linux-gcc (GCC) 6.2.0
Hi Kieran,
> Rather than forward declaring the function ... Could you put the function
> higher
> in the module please?
Will do. Patch will come as a reply shortly.
>>> + if (data == NULL)
>>> + return -ENOMEM;
>>
>> This will set the callers 'flags' to -ENOMEM ? Is that desired?
>
Use flags the device exposes for UVC controls.
This allows the device to define which property flags are set.
Since some cameras offer auto-adjustments for properties (e.g. auto-gain),
the values of other properties (e.g. gain) can change in the camera.
Examining the flags ensures that the driver
On Tue, Aug 29, 2017 at 10:17:51AM -0300, Mauro Carvalho Chehab wrote:
> Right now, only kAPI documentation describes the device naming.
> However, such description is needed at the uAPI too. Add it,
> and describe how to get an unique identify for a given device.
>
> Acked-by: Hans Verkuil
> Sig
Hi Mauro,
Thanks for continuing the work on this!
On Wed, Sep 27, 2017 at 07:23:43PM -0300, Mauro Carvalho Chehab wrote:
> Add a glossary of terms for V4L2, as several concepts are complex
> enough to cause misunderstandings.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/media
On Fri, 2017-10-06 at 10:49 +0300, Sakari Ailus wrote:
> On Thu, Oct 05, 2017 at 10:21:16AM -0700, Tim Harvey wrote:
> > Greetings,
> >
> > I'm working on a HDMI receiver driver for the TDA1997x
> > (https://lwn.net/Articles/734692/) and wanted to throw an error if
> > the
> > detected input resol
Hi Mauro,
On Thu, Oct 05, 2017 at 09:26:51AM -0300, Mauro Carvalho Chehab wrote:
> > > > > +
> > > > > + See :ref:`media_controller`.
> > > > > +
> > > > > +MC-centric
> > > > > + V4L2 hardware that requires a Media controller.
> > > > > +
> > > > > + See :ref:`v4l2_hardware_contro
On 06/10/17 06:26, Archit Taneja wrote:
> Hi Hans,
>
> On 09/19/2017 01:03 PM, Hans Verkuil wrote:
>> From: Hans Verkuil
>>
>> Add support for HDMI CEC to the drm adv7511/adv7533 drivers.
>>
>> The CEC registers that we need to use are identical for both drivers,
>> but they appear at different o
On Thu, Oct 05, 2017 at 03:39:29PM -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 5 Oct 2017 11:21:07 +0300
> Sakari Ailus escreveu:
>
> > Hi Mauro,
> >
> > My apologies for the late reply.
> >
> > On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > > Em Tue, 29 Aug 2017 1
On Thu, Oct 05, 2017 at 10:21:16AM -0700, Tim Harvey wrote:
> Greetings,
>
> I'm working on a HDMI receiver driver for the TDA1997x
> (https://lwn.net/Articles/734692/) and wanted to throw an error if the
> detected input resolution/vidout-output-bus-format exceeded the max
> pixel rate of the SoC
33 matches
Mail list logo
