tree: git://linuxtv.org/media_tree.git master
head: 4a9fbcbbf069a54e4ceaf36689846400e408640f
commit: c0e284ccfedafb646c2af33bdd07985231f71916 [82/107] media: venus: Update
clock scaling
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
g
From: Bingbu Cao
This patch add more details for the resolution change blocks
It can help the developer to understand the main resolution
change blocks in ImgU.
Signed-off-by: Bingbu Cao
---
Changes from v1:
- remove diagram item in TODO file
---
Documentation/media/v4l-drivers/ipu3.rs
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 Oct 8 05:00:12 CEST 2019
media-tree git hash:4a9fbcbbf069a54e4ceaf36689846400e408640f
media_build gi
On Mon, Oct 7, 2019 at 10:07 PM Fabio Estevam wrote:
>
> On Mon, Oct 7, 2019 at 9:51 PM Steve Longerbeam wrote:
>
> > Ah progress. Try:
> >
> > v4l2-ctl -d0 --set-fmt-video=field=interlaced
>
> Yes, with this hint I can run:
>
> # v4l2-ctl -d0 --set-fmt-video=field=interlaced
> # v4l2-ctl --devic
On Mon, Oct 7, 2019 at 9:51 PM Steve Longerbeam wrote:
> Ah progress. Try:
>
> v4l2-ctl -d0 --set-fmt-video=field=interlaced
Yes, with this hint I can run:
# v4l2-ctl -d0 --set-fmt-video=field=interlaced
# v4l2-ctl --device /dev/video0 --stream-mmap --stream-to=x.raw --stream-count=1
And it se
On 10/7/19 5:46 PM, Fabio Estevam wrote:
Hi Steve,
On Mon, Oct 7, 2019 at 9:37 PM Steve Longerbeam wrote:
The adv7180 driver in 5.3.x doesn't support seq-bt, only alternate. So
pad format should be "[fmt:UYVY2X8/720x240 field:alternate]".
Thanks for the suggestion. After changing to field
Hi Steve,
On Mon, Oct 7, 2019 at 9:37 PM Steve Longerbeam wrote:
> The adv7180 driver in 5.3.x doesn't support seq-bt, only alternate. So
> pad format should be "[fmt:UYVY2X8/720x240 field:alternate]".
Thanks for the suggestion. After changing to field:alternate I get:
# gst-launch-1.0 v4l2src
Hi Fabio,
On 10/7/19 5:15 PM, Fabio Estevam wrote:
Hi Steve,
Are you still able to capture from the camera on the imx53-smd board
with kernel 5.3.x?
I haven't tried the SMD board in a while, it's possible something broke,
but see below...
I have a custom board with a ADV7180 and it gets
Hi Steve,
Are you still able to capture from the camera on the imx53-smd board
with kernel 5.3.x?
I have a custom board with a ADV7180 and it gets detected like this:
[2.970246] ipu1_csi0: Registered ipu1_csi0 capture as /dev/video0
[2.979741] ipu1_ic_prpenc: Registered ipu1_ic_prpenc ca
Le lundi 07 octobre 2019 à 13:44 +0200, Ricardo Ribalda Delgado a
écrit :
> HI Tomasz
>
> On Mon, Oct 7, 2019 at 11:43 AM Tomasz Figa wrote:
> > Hi Ricardo,
> >
> > On Mon, Oct 7, 2019 at 6:22 PM Ricardo Ribalda Delgado
> > wrote:
> > > HI Nicolas
> > >
> > > Sorry to hijack the thread. Do you
Greetings
My name is Barrister Hans Erich.
I have a client who is interested to invest in your country, she is a well
known politician in her country and deserve a lucrative investment partnership
with you outside her country without any delay Please can you manage such
investment please Kin
Hi,
> Am 07.10.2019 um 18:56 schrieb Michael Allwright :
>
> On Mon, 7 Oct 2019 at 18:34, Tony Lindgren wrote:
>>
>> Hi,
>>
>> * Sakari Ailus [190628 11:05]:
>>> Hi Michael,
>>>
>>> On Mon, Aug 10, 2015 at 05:16:30PM +0200, Michael Allwright wrote:
Hi All,
The following PRELI
Em Mon, 7 Oct 2019 11:55:51 -0300
Mauro Carvalho Chehab escreveu:
> Em Mon, 7 Oct 2019 17:38:53 +0300
> Stanimir Varbanov escreveu:
>
> > Hi Mauro,
> >
> > Thanks for the fix!
> >
> > On 10/7/19 4:37 PM, Mauro Carvalho Chehab wrote:
> > > As reported by jenk...@linuxtv.org, the build with i
On Mon, 7 Oct 2019 at 18:34, Tony Lindgren wrote:
>
> Hi,
>
> * Sakari Ailus [190628 11:05]:
> > Hi Michael,
> >
> > On Mon, Aug 10, 2015 at 05:16:30PM +0200, Michael Allwright wrote:
> > > Hi All,
> > >
> > > The following PRELIMINARY patch adds DT support to the OMAP4 ISS. It
> > > also fixes s
* H. Nikolaus Schaller [191004 16:27]:
> Hi Tony,
>
> > Am 04.10.2019 um 18:11 schrieb Tony Lindgren :
> >
> > * H. Nikolaus Schaller [191004 07:25]:
> >> Hi Tony,
> >> is there a similar node for omap5 comparable to this for omap4:
> >>
> >> https://git.kernel.org/pub/scm/linux/kernel/git/tor
Hi,
* Sakari Ailus [190628 11:05]:
> Hi Michael,
>
> On Mon, Aug 10, 2015 at 05:16:30PM +0200, Michael Allwright wrote:
> > Hi All,
> >
> > The following PRELIMINARY patch adds DT support to the OMAP4 ISS. It
> > also fixes some problems a have found along the way. It is tightly
> > modelled af
Parse device properties and register controls for them using the newly
introduced helpers.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/ov13858.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/media/i2c/ov13858.c b/drivers/media/i2c/ov13858.c
index aac6f77afa0f..2e
Before adding a new forward declaration to the v4l2-ctrls.h header file,
sort the existing ones alphabetically.
Signed-off-by: Jacopo Mondi
---
include/media/v4l2-ctrls.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/media/v4l2-ctrls.h b/include/media/v4l2-c
Add an helper function to v4l2-ctrls to register controls associated
with a device property.
Signed-off-by: Jacopo Mondi
---
drivers/media/v4l2-core/v4l2-ctrls.c | 40
include/media/v4l2-ctrls.h | 26 ++
2 files changed, 66 insertions(+)
di
Hello, fourth iteration following:
"media: v4l2-ctrls: Add camera sensor location"
https://patchwork.kernel.org/project/linux-media/list/?series=160901
"[v2,00/10] media: Report camera sensor properties
https://patchwork.kernel.org/cover/6443/
"[PATCH v3 00/11] media: Report camera sensor prop
Add an helper function to parse common device properties in the same
way as v4l2_fwnode_endpoint_parse() parses common endpoint properties.
Parse the 'rotation' and 'location' properties from the firmware
interface.
Signed-off-by: Jacopo Mondi
---
drivers/media/v4l2-core/v4l2-fwnode.c | 42
Add support for the newly defined V4L2_CID_CAMERA_SENSOR_LOCATION
and V4L2_CID_CAMERA_SENSOR_ROTATION read-only controls used to report
the camera device mounting position and orientation respectively.
Reviewed-by: Laurent Pinchart
Signed-off-by: Jacopo Mondi
---
drivers/media/v4l2-core/v4l2-ct
Before adding a new include directive, sort the existing ones in
alphabetical order.
Signed-off-by: Jacopo Mondi
---
drivers/media/v4l2-core/v4l2-ctrls.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
b/drivers/media/v4l2-core/v4
Parse device properties and register controls for them using the newly
introduced helpers.
Signed-off-by: Jacopo Mondi
---
drivers/media/i2c/ov5670.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/media/i2c/ov5670.c b/drivers/media/i2c/ov5670.c
index 041fcbb4eebd..f118
Add the 'location' device property, used to specify a device mounting
position. The property is particularly meaningful for mobile devices
with a well defined usage orientation.
Signed-off-by: Jacopo Mondi
---
.../devicetree/bindings/media/video-interfaces.txt| 11 +++
1 file changed
Add documentation for the V4L2_CID_CAMERA_SENSOR_LOCATION camera
control. The newly added read-only control reports the camera device
mounting position.
Signed-off-by: Jacopo Mondi
---
.../media/uapi/v4l/ext-ctrls-camera.rst | 32 +++
1 file changed, 32 insertions(+)
diff
Expand the 'rotation' property description to define the direction and
orientation of the axis around which the device mounting rotation is
expressed.
Signed-off-by: Jacopo Mondi
---
.../devicetree/bindings/media/video-interfaces.txt| 8 +---
1 file changed, 5 insertions(+), 3 deleti
Add documentation for the V4L2_CID_CAMERA_SENSOR_ROTATION camera
control. The newly added read-only control reports the camera device
mounting rotation.
Signed-off-by: Jacopo Mondi
---
.../media/uapi/v4l/ext-ctrls-camera.rst | 116 ++
1 file changed, 116 insertions(+)
diff
Visual inspection of the usbvision driver shows that it suffers from
three races between its open, close, and disconnect handlers. In
particular, the driver is careful to update its usbvision->user and
usbvision->remove_pending flags while holding the private mutex, but:
usbvision_v4l2_cl
Hi Tomasz,
On Montag, 7. Oktober 2019 16:14:13 CEST Tomasz Figa wrote:
> Hi Dmitry,
>
> On Mon, Oct 7, 2019 at 11:01 PM Dmitry Morozov
>
> wrote:
> > Hello,
> >
> > We at OpenSynergy are also working on an abstract paravirtualized video
> > streaming device that operates input and/or output da
When TI CAL was introduce as another driver under platform/ti-vpe
adding a second entry into the ti-vpe directory in the platform
Makefile caused issues during parallel build.
Signed-off-by: Benoit Parrot
Signed-off-by: Jyri Sarha
---
drivers/media/platform/Makefile | 4 +---
1 file changed, 1
Instead of saving a pointer to the 'fh' member of struct vpe_ctx to
later have to use container_of to retrieve the actual pointer to the
context structure, which seems to confuse static code analysis tool
anyways, just save the pointer to the actual structure and then retrieve
it directly.
Signed-
A few NULL pointer checks were missing.
Add check with appropriate return code.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-
This a collection of backlog patches I have been carrying for the VPE
driver.
It adds supports for SEQ_BT as well as NV21.
And fixes a number of issues both through v4l2-compliance and normal
usage.
Changes since v2:
- Fix a type causing a compile error
- Address Hans' comment on the v4l2_common
v4l2-compliance warns with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
warn: v4l2-test-formats.cpp(718): \
This may or may not be a problem. For more information see:
warn: v4l2-test-formats.cpp(719): \
http://www
v4l2-compliance fails with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
test VIDIOC_TRY_FMT: FAIL
This causes the following kernel panic:
Unable to handle kernel paging request at virtual address 56595561
pgd = ecd80e00
*pgd=00
v4l2-compliance fails with this message:
fail: v4l2-test-formats.cpp(672): \
Video Capture Multiplanar: TRY_FMT(G_FMT) != G_FMT
fail: v4l2-test-formats.cpp(672): \
Video Output Multiplanar: TRY_FMT(G_FMT) != G_FMT
...
test VIDIOC_TRY_FMT: FAIL
Fixes: 94ed726e8e01
The syzbot fuzzer found two invalid-access bugs in the usbvision
driver. These bugs occur when userspace keeps the device file open
after the device has been disconnected and usbvision_disconnect() has
set usbvision->dev to NULL:
When the device file is closed, usbvision_radio_close() tri
Em Mon, 7 Oct 2019 17:38:53 +0300
Stanimir Varbanov escreveu:
> Hi Mauro,
>
> Thanks for the fix!
>
> On 10/7/19 4:37 PM, Mauro Carvalho Chehab wrote:
> > As reported by jenk...@linuxtv.org, the build with i386 fails
> > with:
> >
> > ld: drivers/media/platform/qcom/venus/helpers.o: in fun
Hi Mauro,
Thanks for the fix!
On 10/7/19 4:37 PM, Mauro Carvalho Chehab wrote:
> As reported by jenk...@linuxtv.org, the build with i386 fails
> with:
>
> ld: drivers/media/platform/qcom/venus/helpers.o: in function
> `venus_helper_load_scale_clocks':
> (.text+0x1d77): undefined ref
On 10/4/19 12:24 PM, Vandana BN wrote:
> +void vivid_meta_cap_fillbuff(struct vivid_dev *dev,
> + struct vivid_buffer *buf, u32 soe)
soe should have been a u64 since f_time is a u64.
> +{
> + struct vivid_uvc_meta_buf *meta = vb2_plane_vaddr(&buf->vb.vb2_buf, 0);
> +
On 10/4/19 2:08 PM, Vandana BN wrote:
> Support metadata output in vivid driver.
> Metadata output is used to set brightness, contrast, saturation
> and hue.
> Adds new files for metadata output.
>
> Signed-off-by: Vandana BN
> ---
> drivers/media/platform/vivid/Makefile | 2 +-
> driv
On Fri, Sep 27, 2019 at 3:55 AM Jacopo Mondi wrote:
>
> Hi Hans, thanks for the lenghty reply
>
> On Thu, Sep 26, 2019 at 10:11:51AM +0200, Hans Verkuil wrote:
> > On 9/3/19 6:49 PM, Jacopo Mondi wrote:
> > > Hi Sakari, Hans,
> > >
> > > On Tue, Sep 03, 2019 at 04:06:26PM +0300, Sakari Ailus wrote
Hi Dmitry,
On Mon, Oct 7, 2019 at 11:01 PM Dmitry Morozov
wrote:
>
> Hello,
>
> We at OpenSynergy are also working on an abstract paravirtualized video
> streaming device that operates input and/or output data buffers and can be
> used
> as a generic video decoder/encoder/input/output device.
>
Hello,
We at OpenSynergy are also working on an abstract paravirtualized video
streaming device that operates input and/or output data buffers and can be used
as a generic video decoder/encoder/input/output device.
We would be glad to share our thoughts and contribute to the discussion.
Please
cleanup and buf fixing patches for vimc
Changes from v2:
The head of the thirds patch is chaned to start with "media vimc: sen:"
Dafna Hirschfeld (5):
media: vimc: initialize vim entity pointers to NULL
media: vimc: cleanup code that assigns entity in entities array
media: vimc: sen: regist
since NULL value for vimc entity pointer indicates
that entity creation failed and this is tested, the
pointers should be initialized to NULL.
Signed-off-by: Dafna Hirschfeld
Acked-by: Helen Koike
---
drivers/media/platform/vimc/vimc-core.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletion
Since the add callback returns NULL on failure and the array
is initialized to NULLs, there is no need for the intermediate
assignment to local var.
Signed-off-by: Dafna Hirschfeld
Acked-by: Helen Koike
---
drivers/media/platform/vimc/vimc-core.c | 6 ++
1 file changed, 2 insertions(+), 4 d
according to the docs, this function must be called during
the cleanup phase after unregistering the entity.
Signed-off-by: Dafna Hirschfeld
Acked-by: Helen Koike
---
drivers/media/platform/vimc/vimc-capture.c | 2 +-
drivers/media/platform/vimc/vimc-common.c | 1 -
drivers/media/platform/vimc
vimc_sen_add function first registers the subdevice and then
calls tpg_alloc. If tpg_alloc fails it unregisters the subdevice
and then frees vsen, this cause double free since the release
callback that follows subdevice unregistration also frees vsen.
Signed-off-by: Dafna Hirschfeld
Acked-by: Hel
since this function only calls v4l2_device_unregister_subdev,
it is pointless.
Signed-off-by: Dafna Hirschfeld
Acked-by: Helen Koike
---
drivers/media/platform/vimc/vimc-common.c | 5 -
drivers/media/platform/vimc/vimc-common.h | 12
drivers/media/platform/vimc/vimc-debayer.
As reported by jenk...@linuxtv.org, the build with i386 fails
with:
ld: drivers/media/platform/qcom/venus/helpers.o: in function
`venus_helper_load_scale_clocks':
(.text+0x1d77): undefined reference to `__udivdi3'
ld: (.text+0x1dce): undefined reference to `__udivdi3'
On Mon, Oct 07, 2019 at 07:11:03PM +0800, Chen-Yu Tsai wrote:
> On Mon, Oct 7, 2019 at 7:09 PM Maxime Ripard wrote:
> >
> > Hi,
> >
> > On Fri, Oct 04, 2019 at 02:33:41PM +0800, Chen-Yu Tsai wrote:
> > > On Fri, Oct 4, 2019 at 12:37 AM Maxime Ripard wrote:
> > > > On Thu, Oct 03, 2019 at 11:51:05
HI Tomasz
On Mon, Oct 7, 2019 at 11:43 AM Tomasz Figa wrote:
>
> Hi Ricardo,
>
> On Mon, Oct 7, 2019 at 6:22 PM Ricardo Ribalda Delgado
> wrote:
> >
> > HI Nicolas
> >
> > Sorry to hijack the thread. Do you know if anyone at AMD is working on
> > making a v4l driver for the encoder? Or they want
On Mon, Oct 7, 2019 at 7:09 PM Maxime Ripard wrote:
>
> Hi,
>
> On Fri, Oct 04, 2019 at 02:33:41PM +0800, Chen-Yu Tsai wrote:
> > On Fri, Oct 4, 2019 at 12:37 AM Maxime Ripard wrote:
> > > On Thu, Oct 03, 2019 at 11:51:05PM +0800, Chen-Yu Tsai wrote:
> > > > On Thu, Oct 3, 2019 at 11:48 PM Maxime
Hi,
On Fri, Oct 04, 2019 at 02:33:41PM +0800, Chen-Yu Tsai wrote:
> On Fri, Oct 4, 2019 at 12:37 AM Maxime Ripard wrote:
> > On Thu, Oct 03, 2019 at 11:51:05PM +0800, Chen-Yu Tsai wrote:
> > > On Thu, Oct 3, 2019 at 11:48 PM Maxime Ripard wrote:
> > > >
> > > > It turns out that what was thought
The code for pulse and space is the same so remove duplication.
Signed-off-by: Sean Young
---
drivers/media/rc/imon_raw.c | 22 --
1 file changed, 4 insertions(+), 18 deletions(-)
diff --git a/drivers/media/rc/imon_raw.c b/drivers/media/rc/imon_raw.c
index d4aedcf76418..aae0
Hi Ricardo,
On Mon, Oct 7, 2019 at 6:22 PM Ricardo Ribalda Delgado
wrote:
>
> HI Nicolas
>
> Sorry to hijack the thread. Do you know if anyone at AMD is working on
> making a v4l driver for the encoder? Or they want to continue with
> their mesa approach?
>
> Converting a mesa-vappi to v4l is som
HI Nicolas
Sorry to hijack the thread. Do you know if anyone at AMD is working on
making a v4l driver for the encoder? Or they want to continue with
their mesa approach?
Converting a mesa-vappi to v4l is something doable by the mortals?
Just changing the API or is a complete rewrite of the code?
From: buil...@linuxtv.org
Pull request: https://patchwork.linuxtv.org/patch/59240/
Build log: https://builder.linuxtv.org/job/patchwork/19353/
Build time: 00:02:30
Link:
https://lore.kernel.org/linux-media/19c02424-d128-2f56-8e4e-04f11e9e3...@xs4all.nl
gpg: Signature made Mon 07 Oct 2019 07:41:5
The following changes since commit 503e59365dd134b2c63864f14e2de0476284b003:
media: i2c: ov2659: Switch to SPDX Licensing (2019-10-01 17:39:16 -0300)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/fix-v5.4a
for you to fetch changes up to 9b99475a1b930
61 matches
Mail list logo
