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 Apr 13 05:00:11 CEST 2019
media-tree git hash:1c3ec30bb23023d738b538e64ac3028902d53692
media_build gi
On Fri, Apr 12, 2019 at 05:33:38PM +0200, Jacopo Mondi wrote:
> Hi Sakari,
>
> On Fri, Apr 05, 2019 at 12:41:17PM +0300, Sakari Ailus wrote:
> > Hi folks,
> >
> > This patchset reworks V4L2 fwnode endpoint parsing. It enables the use of
> > endpoint configuration defaults that is available sensors
On Mon, 2019-04-01 at 12:14 +0900, Tomasz Figa wrote:
> On Tue, Mar 5, 2019 at 4:27 AM Ezequiel Garcia wrote:
> > Rework the way controls are registered by the driver,
> > so it can support non-standard controls, such as those
> > used by stateless codecs.
> >
> > Signed-off-by: Ezequiel Garcia
When register the capture media device it is assumed that the device
data is the media device. In the imx6 case is but in the imx7 is not
case. The device data is the csi structure.
Add the explicit argument of the media device that we want to
associate with the capture device.
Reported-by: Laure
On 4/12/2019 7:33 AM, Eddie James wrote:
On 4/12/19 7:17 AM, Herrenschmidt, Benjamin wrote:
On Fri, 2019-04-12 at 13:00 +0200, Hans Verkuil wrote:
Eddie, can you review this?
Yes, this looks good.
Thanks,
Reviewed-by: Eddie James
Thanks Eddie!
I'll submit a new patch on top of your up
On 4/12/2019 5:17 AM, Herrenschmidt, Benjamin wrote:
On Fri, 2019-04-12 at 13:00 +0200, Hans Verkuil wrote:
Eddie, can you review this?
Jae Hyun Yoo, for future reference: please add the driver name in the
subject.
I.e. something like this: [PATCH v2] media: aspeed: fix a kernel
warning on clk
On 4/12/2019 4:00 AM, Hans Verkuil wrote:
Eddie, can you review this?
Jae Hyun Yoo, for future reference: please add the driver name in the subject.
I.e. something like this: [PATCH v2] media: aspeed: fix a kernel warning on clk
control
That helps maintainers figuring out who should look at wh
The header report return value from decoder sequence initialization is
available on CodaHx4 and CODA7541 already. Use the profile and level
identification values reported by the firmware to update codec specific
profile and level controls after sequence initialization has succeeded.
Signed-off-by:
Add a function to translate from V4L2 buffer flags to 'I'/'P'/'B'
characters for debug output.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-bit.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/coda/coda-bit.c
b/drive
Add MPEG-2 CID definitions for profiles and levels defined in ITU-T Rec.
H.262.
Signed-off-by: Philipp Zabel
---
.../media/uapi/v4l/ext-ctrls-codec.rst| 56 +++
drivers/media/v4l2-core/v4l2-ctrls.c | 23
include/uapi/linux/v4l2-controls.h| 16
Use v4l2_m2m2_buf_copy_metadata to let BIT encoder contexts copy buffer
field, timestamp, timestamp flags, and optionally timecode.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-bit.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/media/plat
v4l2-compliance likes to queue a buffer with field set to V4L2_FIELD_ANY
and expects it to be returned corrected to a valid field.
Follow vicodec in handling this in the buf_prepare callback.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 10 ++
1 file chan
When a menu control is updated via s_ctrl, print the corresponding menu
entry string in addition to the numerical value it is set to.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/me
The MPEG-2 decoder firmware reports profile and level indication that
can be used to set V4L2 MPEG-2 profile and level controls
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/Makefile | 2 +-
drivers/media/platform/coda/coda-common.c | 25 +
drivers/media/platform
This allows to use coda_debug level 2 for verbose but not quite as
verbose debug logging. Register access level logging is of limited
use anyway, as this includes busy polling of status bits.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 4 ++--
1 file changed, 2 i
Use the newly freed verbose debug level 2 for job ready debug messages.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/coda/coda-common.c
b/drivers/media/platform/coda/coda-com
The MPEG-4 decoder firmware reports profile and level indication values
that can be used to update V4L2 MPEG-4 profile and level controls.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/Makefile | 2 +-
drivers/media/platform/coda/coda-common.c | 23 +++
drivers/media
coda_command_sync, coda_hw_reset, and __coda_start_decoding
all expect to be called under the coda_mutex device lock.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-bit.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/media/platform/coda/coda-bit.c
b/driver
Otherwise the default initialization would always swamp the debug log.
Signed-off-by: Philipp Zabel
---
drivers/media/platform/coda/coda-common.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/coda/coda-common.c
b/drivers/media/platform/coda/coda-comm
Print a single line containing the following information:
- which frame was decoded, including its type,
- if no frame was decoded, the reason (code) why
- which decoded frame was returned, copied out by either rotator or VODA,
- if no frame was returned, the reason (code) why, and
- the outpu
Hi Sakari,
On Fri, Apr 05, 2019 at 12:41:17PM +0300, Sakari Ailus wrote:
> Hi folks,
>
> This patchset reworks V4L2 fwnode endpoint parsing. It enables the use of
> endpoint configuration defaults that is available sensors and other
> drivers that only use a single endpoint. Well, the functionalit
On 4/12/19 7:17 AM, Herrenschmidt, Benjamin wrote:
On Fri, 2019-04-12 at 13:00 +0200, Hans Verkuil wrote:
Eddie, can you review this?
Yes, this looks good.
Thanks,
Reviewed-by: Eddie James
Jae Hyun Yoo, for future reference: please add the driver name in the
subject.
I.e. something l
Hi Hans,
On 19-04-12 14:17, Hans Verkuil wrote:
> On 4/5/19 8:03 AM, Marco Felsch wrote:
> > Currently every driver needs to parse the connector endpoints by it self.
> > This is the initial work to make this generic. The generic connector has
> > some common fields and some connector specific par
Hi Hans,
On 19-04-12 14:14, Hans Verkuil wrote:
> On 4/5/19 8:03 AM, 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 a
On Fri, 2019-04-12 at 13:00 +0200, Hans Verkuil wrote:
> Eddie, can you review this?
>
> Jae Hyun Yoo, for future reference: please add the driver name in the
> subject.
> I.e. something like this: [PATCH v2] media: aspeed: fix a kernel
> warning on clk control
>
> That helps maintainers figuring
On 4/5/19 8:03 AM, Marco Felsch wrote:
> Currently every driver needs to parse the connector endpoints by it self.
> This is the initial work to make this generic. The generic connector has
> some common fields and some connector specific parts. The generic one
> includes:
> - type
> - label
>
On 4/5/19 8:03 AM, 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 are
> restriced by a label e.g. to plug only a camera into
The following changes since commit 1c3ec30bb23023d738b538e64ac3028902d53692:
media: index.rst: exclude Indexes section from latex/pdf output (2019-03-30
09:42:35 -0400)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-cedrus-h264
for you to fetch ch
On 4/12/19 12:32, Hans Verkuil wrote:
> On 4/12/19 12:16 PM, Sylwester Nawrocki wrote:
>> On 4/12/19 11:20, Boris Brezillon wrote:
>>> The fimc-isp-video.c and fimc-lite.c were missing the
>>> V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
>>
>> Th omission was intentional, as these
Eddie, can you review this?
Jae Hyun Yoo, for future reference: please add the driver name in the subject.
I.e. something like this: [PATCH v2] media: aspeed: fix a kernel warning on clk
control
That helps maintainers figuring out who should look at which patch.
Regards,
Hans
On 3/29/
Fixes to prevent incrementing but never decrementing the hdmi device
refcount, and the series for the new Meson CEC driver is sitting on top
of those.
Regards,
Hans
The following changes since commit 1c3ec30bb23023d738b538e64ac3028902d53692:
media: index.rst: exclude Indexes section f
On 4/12/19 12:16 PM, Sylwester Nawrocki wrote:
> Hi,
>
> On 4/12/19 11:20, Boris Brezillon wrote:
>> The fimc-isp-video.c and fimc-lite.c were missing the
>> V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
>
> Th omission was intentional, as these video nodes cannot be used
> by "s
On Fri, 12 Apr 2019 12:16:42 +0200
Sylwester Nawrocki wrote:
> Hi,
>
> On 4/12/19 11:20, Boris Brezillon wrote:
> > The fimc-isp-video.c and fimc-lite.c were missing the
> > V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
>
> Th omission was intentional, as these video nodes ca
Hi,
On 4/12/19 11:20, Boris Brezillon wrote:
> The fimc-isp-video.c and fimc-lite.c were missing the
> V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
Th omission was intentional, as these video nodes cannot be used
by "standard" V4L2 capture applications. Some sub-devices need to
On 4/12/19 10:25 AM, Boris Brezillon wrote:
> On Thu, 11 Apr 2019 12:38:06 +0200
> Hans Verkuil wrote:
>
> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
> b/drivers/media/v4l2-core/v4l2-ioctl.c
> index f6d663934648..97ba365218fb 100644
> --- a/drivers/media/v4l2-core/v4l2-ioc
On 4/12/19 11:20 AM, Boris Brezillon wrote:
> The fimc-isp-video.c and fimc-lite.c were missing the
> V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
>
> Signed-off-by: Boris Brezillon
> ---
> Changes in v3:
> - New patch
> ---
> drivers/media/platform/exynos4-is/fimc-isp-video.c
Support for multiplanar and singleplanar formats is mutually exclusive,
at least in practice. In our attempt to unify support for support for
mplane and !mplane in v4l, let's get rid of the
->vidioc_enum_fmt_{vid,out}_cap_mplane() hooks and call
->vidioc_enum_fmt_{vid,out}_cap() instead.
Signed-of
The fimc-isp-video.c and fimc-lite.c were missing the
V4L2_CAP_VIDEO_CAPTURE_MPLANE flag when reporting device caps.
Signed-off-by: Boris Brezillon
---
Changes in v3:
- New patch
---
drivers/media/platform/exynos4-is/fimc-isp-video.c | 4 +++-
drivers/media/platform/exynos4-is/fimc-lite.c |
On Thu, 4 Apr 2019 10:16:56 +0200
Boris Brezillon wrote:
> +/**
> + * struct v4l2_ext_buffer - extended video buffer info
> + * @index: id number of the buffer
> + * @type: enum v4l2_buf_type; buffer type. _MPLANE and _OVERLAY formats are
> + * invalid
> + * @flags: buffer informational fla
On Fri, 12 Apr 2019 10:25:26 +0200
Boris Brezillon wrote:
> On Thu, 11 Apr 2019 12:38:06 +0200
> Hans Verkuil wrote:
>
> > >>> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
> > >>> b/drivers/media/v4l2-core/v4l2-ioctl.c
> > >>> index f6d663934648..97ba365218fb 100644
> > >>> --- a/drivers/
On Thu, 11 Apr 2019 12:38:06 +0200
Hans Verkuil wrote:
> >>> diff --git a/drivers/media/v4l2-core/v4l2-ioctl.c
> >>> b/drivers/media/v4l2-core/v4l2-ioctl.c
> >>> index f6d663934648..97ba365218fb 100644
> >>> --- a/drivers/media/v4l2-core/v4l2-ioctl.c
> >>> +++ b/drivers/media/v4l2-core/v4l2-ioct
41 matches
Mail list logo
