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: Tue Aug 20 05:00:10 CEST 2019
media-tree git hash:d4e0f82ac840bf3d16b25d60f261b429603138a9
media_build gi
Hi Eugen,
On Mon, Aug 19, 2019 at 03:24:26PM +, eugen.hris...@microchip.com wrote:
> On 19.08.2019 18:04, Laurent Pinchart wrote:
> > On Mon, Aug 19, 2019 at 11:43:56AM -0300, Ezequiel Garcia wrote:
> >> On Mon, 2019-08-19 at 09:44 +0200, Hans Verkuil wrote:
> >>> On 8/16/19 10:06 AM, Hans Ver
On 19.08.2019 18:04, Laurent Pinchart wrote:
> Hello,
>
> On Mon, Aug 19, 2019 at 11:43:56AM -0300, Ezequiel Garcia wrote:
>> On Mon, 2019-08-19 at 09:44 +0200, Hans Verkuil wrote:
>>> On 8/16/19 10:06 AM, Hans Verkuil wrote:
Rather then discussing topics for a meeting under the subject 'Li
Hello,
On Mon, Aug 19, 2019 at 11:43:56AM -0300, Ezequiel Garcia wrote:
> On Mon, 2019-08-19 at 09:44 +0200, Hans Verkuil wrote:
> > On 8/16/19 10:06 AM, Hans Verkuil wrote:
> > > Rather then discussing topics for a meeting under the subject 'Lisbon'
> > > let's start a new thread referring to the
On Mon, 2019-08-19 at 09:44 +0200, Hans Verkuil wrote:
> On 8/16/19 10:06 AM, Hans Verkuil wrote:
> > Rather then discussing topics for a meeting under the subject 'Lisbon'
> > let's start a new thread referring to the right place :-)
> >
> > I will try to organize a room, either during the ELCE o
On 8/19/19 11:32 AM, Hans Verkuil wrote:
> On 8/14/19 12:45 PM, Dariusz Marcinkiewicz wrote:
>> Use the new cec_notifier_conn_(un)register() functions to
>> (un)register the notifier for the HDMI connector, and fill in
>> the cec_connector_info.
>>
>> Changes since v6:
>> - move cec_notifie
Renesas media binding documentation files uses a naming schema of
'renesas,.txt'. Rename the SH Mobile CEU file to match this pattern.
Signed-off-by: Simon Horman
---
Based on v5.3-rc1
---
.../bindings/media/{sh_mobile_ceu.txt => renesas,sh-mobile-ceu.txt} | 0
1 file changed, 0 insertions
Probe error handling cleanups and fixes:
- Move mutex initialisation at a later time for easier error handling.
- Issue destroy_mutex on the sensor mutex on probe failure and driver
remove,
- Remove smiapp_cleanup and add its contents in probe / remove on right
locations.
Signed-off-by: Sak
The active field was used to track whether the sensor was powered when
settings its controls. This is no longer needed as runtime PM is used to
determine this instead.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 4
drivers/media/i2c/smiapp/smiapp-regs.c | 3 ---
Rely on the V4L2 sub-device framework to perform the locking for this
driver.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 140 +++--
1 file changed, 36 insertions(+), 104 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers
Remove switch fall-through cases in the driver.
Signed-off-by: Sakari Ailus
---
drivers/media/i2c/smiapp/smiapp-core.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/media/i2c/smiapp/smiapp-core.c
b/drivers/media/i2c/smiapp/smiapp-core.c
index 76d7d204ec
The subdev's video device node was only assigned after registering the
device node in the system. While it is unlikely that a driver needed to
use this field in handling system calls to its file handle, there remains
a slim chance the devnode field remains NULL while the driver expects to
find a vi
The V4L2 sub-device's operations are called both from other drivers as
well as through the IOCTL uAPI. Previously the sub-device drivers were
responsible for managing their own serialisation. This patch adds an
optional mutex the drivers may set, and it will be used to serialise
access to driver's
Hi folks,
While access to the V4L2 device nodes was conveniently serialised for
devices the drivers of which used the V4L2 framework, this was no the case
for sub-devices that also may be called from other drivers.
Instead acquire the lock to the v4l2_subdev_call macro.
This set adds the capabil
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/58279/
Build log: https://builder.linuxtv.org/job/patchwork/12083/
Build time: 00:18:08
Link:
https://lore.kernel.org/linux-media/20190819113126.fo3dvsux5eogc...@gofer.mess.org
Summary: 7 patches and/or PDF generation wit
Hi Mauro,
This PR includes A Sun's re-write of mceusb Tx, some new keymaps and some
of fixes.
Thanks,
Sean
The following changes since commit 31d5d15dfc3418a57cfab419a353d8dc5f5698b5:
media: MAINTAINERS: Add entry for the ov5670 driver (2019-08-15 08:17:04
-0300)
are available in the Git re
Hi Steve,
On Fri, 2019-08-16 at 16:17 -0700, Steve Longerbeam wrote:
> Hi Philipp,
>
> If you haven't already, can you please test rotation with this version,
> with both non-tiled and tiled scaling conversions. I found rotation was
> broken in v8.
>
> Steve
I've tested a few resolutions with
On 8/19/19 12:40 PM, Marco Felsch wrote:
> On 19-08-16 13:27, Hans Verkuil wrote:
>> On 8/15/19 1:57 PM, Marco Felsch wrote:
>>> Since commit 10d5509c8d50 ("[media] v4l2: remove g/s_crop from video ops")
>>> the 'which' field for set/get_selection must be FORMAT_ACTIVE. There is
>>> no way to try d
On 19-08-16 13:27, Hans Verkuil wrote:
> On 8/15/19 1:57 PM, Marco Felsch wrote:
> > Since commit 10d5509c8d50 ("[media] v4l2: remove g/s_crop from video ops")
> > the 'which' field for set/get_selection must be FORMAT_ACTIVE. There is
> > no way to try different selections. The patch adds a helper
On 19-08-16 12:59, Hans Verkuil wrote:
> On 8/15/19 1:57 PM, Marco Felsch wrote:
> > Currently every driver needs to parse the connector endpoints by it self.
> > This is the initial work to make this generic. A generic connector has
> > common members and connector specific members. The common mem
On 8/19/19 11:17 AM, Marco Felsch wrote:
> On 19-08-16 12:59, Hans Verkuil wrote:
>> On 8/15/19 1:57 PM, Marco Felsch wrote:
>>> Currently every driver needs to parse the connector endpoints by it self.
>>> This is the initial work to make this generic. A generic connector has
>>> common members an
On 8/19/19 11:01 AM, Marco Felsch wrote:
> On 19-08-19 10:39, Hans Verkuil wrote:
>> On 8/19/19 10:09 AM, Marco Felsch wrote:
>>> Hi Hans,
>>>
>>> On 19-08-16 13:11, Hans Verkuil wrote:
On 8/15/19 1:57 PM, Marco Felsch wrote:
> Some connectors no matter if in- or output supports only a lim
On 19-08-19 10:39, Hans Verkuil wrote:
> On 8/19/19 10:09 AM, Marco Felsch wrote:
> > Hi Hans,
> >
> > On 19-08-16 13:11, Hans Verkuil wrote:
> >> On 8/15/19 1:57 PM, Marco Felsch wrote:
> >>> Some connectors no matter if in- or output supports only a limited
> >>> range of tv norms. It doesn't ma
On 8/19/19 10:18 AM, Marco Felsch wrote:
> Hi,
>
> On 19-08-19 10:09, Marco Felsch wrote:
>> Hi Hans,
>>
>> On 19-08-16 13:11, Hans Verkuil wrote:
>>> On 8/15/19 1:57 PM, Marco Felsch wrote:
Some connectors no matter if in- or output supports only a limited
range of tv norms. It doesn't
On 8/19/19 10:09 AM, Marco Felsch wrote:
> Hi Hans,
>
> On 19-08-16 13:11, Hans Verkuil wrote:
>> On 8/15/19 1:57 PM, Marco Felsch wrote:
>>> Some connectors no matter if in- or output supports only a limited
>>> range of tv norms. It doesn't matter if the hardware behind that
>>> connector suppor
Hi Dongchun,
Thanks for the update.
On Mon, Aug 19, 2019 at 11:43:31AM +0800, dongchun@mediatek.com wrote:
> From: Dongchun Zhu
>
> This patch adds a V4L2 sub-device driver for OV02A10 image sensor.
> The OV02A10 is a 1/5" CMOS sensor from Omnivision,
> which supports output format: 10-bit
Hi,
On 19-08-19 10:09, Marco Felsch wrote:
> Hi Hans,
>
> On 19-08-16 13:11, Hans Verkuil wrote:
> > On 8/15/19 1:57 PM, Marco Felsch wrote:
> > > Some connectors no matter if in- or output supports only a limited
> > > range of tv norms. It doesn't matter if the hardware behind that
> > > connec
Hi Hans,
On 19-08-16 13:11, Hans Verkuil wrote:
> On 8/15/19 1:57 PM, Marco Felsch wrote:
> > Some connectors no matter if in- or output supports only a limited
> > range of tv norms. It doesn't matter if the hardware behind that
> > connector supports more than the listed formats since the users
Static structure en_templ, of type dvb_ca_en50221, is not used except to
be copied into a local variable. Hence make it const to prevent
unintended modification of the original fields.
Issue found with Coccinelle.
Signed-off-by: Nishka Dasgupta
---
drivers/media/dvb-frontends/cxd2099.c | 2 +-
1
On 8/16/19 10:06 AM, Hans Verkuil wrote:
> Rather then discussing topics for a meeting under the subject 'Lisbon'
> let's start a new thread referring to the right place :-)
>
> I will try to organize a room, either during the ELCE or (if that doesn't
> work) perhaps on the Thursday afterwards. If
On Wed, Jul 31, 2019 at 06:32:57PM +0200, Sébastien Szymanski wrote:
> Add csi node for i.MX6UL SoC.
>
> Reviewed-by: Fabio Estevam
> Signed-off-by: Sébastien Szymanski
Applied, thanks.
The static structure ec168_props, of type dvb_usb_device_properties, is
used only once, when it is assigned to field props of the constant
structure ec168_driver_info. As this means that ec168_props will never be
modified, make it const as well in order to prevent unintended
modification of its fie
Static structure fdtv_ca, of type dvb_device, is only used when it is
passed as the third argument to function dvb_register_device(). However,
in the definition of dvb_register_device, the third parameter is
declared as constant. Hence make fdtv_ca const as well.
Issue found with Coccinelle.
Signe
Static structure dst_config, of type dst_config, is not used except to
be assigned as the value of field state of a variable having type
dst_state *. In the definition of dst_state, field config is declared as
const. Hence dst_config, when assigned to config, cannot be modified.
Therefore, make dst
34 matches
Mail list logo
