These patches add support for calculating CVT and GTF timings in v4l2-ctl.
vl2-ctl already has a support setting up of fully specified timings. In
this case user needs to specify all values like pixel clock, sync, front
and back porches etc in v4l2_bt_timings structure. Hans had suggested
that it
Added support to parse cvt/gtf suboptions- width, height, refresh
rate, reduced blanking, interlaced.
The cvt/gtf modeline calculations are implemented v4l2-ctl-modes.cpp.
Calling those APIs to update v4l2_bt_timings structure.
Cc: Hans Verkuil
Signed-off-by: Prashant Laddha
---
utils/v4l2-ctl
This patch adds support for calculating v4l2_bt_timings based on
CVT and GTF standards. The timings are calculated for a given
standard, CVT or GTF using a set of parameters- width, height,
refresh rate and flags like whether it is an interlaced format,
and whether to use reduced blanking.
CVT Mod
This change is in preparation towards extending suboptions to include
options to set cvt/gtf timings. One of the suboption for cvt/gtf is
without value. The existing function parse_subopt() does not support
parsing of suboption without value.
Replacing parse_subopt() with new function parse_timing
Currently vivid supports V4L2_DV_BT_STD_DMT and V4L2_DV_BT_STD_CEA861
discrete video standards. Extending the capability set to allow for
setting CVT and GTF standards. This change, along with adding the
support for calculating CVT, GTF timings in v4l2-ctl would extend
the number of resolutions sup
In addition to v4l2_find_dv_timings_cap(), where timings are serached
against the list of preset timings, the incoming timing from v4l2-ctl
is checked against CVT and GTF standards. If it confirms to be CVT or
GTF, it is treated as valid timing and vivid format is updated with
new timings.
Cc: Han
These patches add support for setting CVT and GTF timings in vivid.
Currently vivid supports V4L2_DV_BT_STD_DMT and V4L2_DV_BT_STD_CEA861
digital video standards which are all discrete monitor timings. So,
there is no support for standards outside of that set. Hans has been
thinking about extendin
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: Fri Mar 20 04:00:16 CET 2015
git branch: test
git hash: 3d945be05ac1e806af075e9315bc1b3409adae2b
gcc versio
Hi,
After upgrading my DVB recording PC I started observing the error shown below
every couple of days (I've only shown the first instance but I usually get a
pair of identical errors). Unfortunately I upgraded hardware and OS at the same
time so it is hard to be certain exactly what the trigge
Hello Haneen Mohammed,
The patch 2c9356d115c9: "Staging: media: replace pr_* with dev_*"
from Mar 18, 2015, leads to the following static checker warning:
drivers/staging/media/lirc/lirc_sasem.c:176 delete_context()
error: dereferencing freed memory 'context'
drivers/staging/medi
Provide simple tools for displaying raw IR and received scancodes, and
sending them.
Todo:
- ir-rec cannot enable protocol decoders
- ir-send should accept scancode on commandline
- long options
Signed-off-by: Sean Young
---
configure.ac | 3 +
utils/Makefile.am | 1 +
utils
The lirc interface only passes raw IR. Teach the lirc bridge how to pass
scancodes (along with their IR information) to userspace. This introduces
a new LIRC_MODE_SCANCODE mode where decoded IR is represented as two
u32. The first one signifies LIRC_MODE_SCANCODE, the IR protocol, repeat
and toggle
Since the lirc bridge is not a decoder we can remove its protocol. The
keymap existed only to select the protocol.
Signed-off-by: Sean Young
---
drivers/media/rc/keymaps/Makefile | 1 -
drivers/media/rc/keymaps/rc-lirc.c | 42 --
drivers/media/rc/rc-main.c
If the device cannot transmit then -ENOSYS should be returned. Also clarify
that the ioctl should return modes, not features. The values happen to be
identical.
Signed-off-by: Sean Young
---
drivers/media/rc/ir-lirc-codec.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff
The LIRC_GET_FEATURES ioctl returns an int which represents features as
bitwise flags. Two features use duplicate values so they are unusable.
These are also features which have never been implemented in drivers
according to kernel/lirc git history, so noone ever noticed that they're
half-baked.
L
The lirc bridge exists as a raw decoder. We would like to make the bridge
to also work for scancode drivers in further commits, so it cannot be
a raw decoder.
Note that rc-code, lirc_dev, ir-lirc-codec are now calling functions of
each other, so they've been merged into one module rc-core to avoid
The send mode has to be switched to LIRC_MODE_SCANCODE and then you can
send one scancode with a write. The encoding is the same as for receiving
scancodes.
FIXME: Currently only the nec encoder can encode IR.
FIXME: The "decoders" should be renamed (codec?)
Signed-off-by: Sean Young
---
.../Do
This patch series tries to fix the lirc interface and extend it so it can
be used to send/recv scancodes in addition to raw IR:
- Make it possible to receive scancodes from hardware that generates
scancodes (with rc protocol information)
- Make it possible to receive decoded scancodes from r
Hi Laurent,
I took the first option ;)
http://pastebin.com/7YUgS2Zt
Regards, Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Oliver,
On Thursday 19 March 2015 19:17:48 Oliver Lehmann wrote:
> Hi Laurent,
>
> Laurent Pinchart wrote:
> > Could you please post the output of "lsusb -v" for your camera (running as
> > root if possible) ?
>
> No lsusb on FreeBSD but usbconfig - I hope the results are similar or are at
>
Hi Laurent,
Laurent Pinchart wrote:
Could you please post the output of "lsusb -v" for your camera (running as
root if possible) ?
No lsusb on FreeBSD but usbconfig - I hope the results are similar or are at
least close to what you are seeking for.
http://pastebin.com/s3ndu63h
Regards, Oli
* Sakari Ailus [150318 16:51]:
> Hi folks,
>
> Since v1, I've rebased the set on Tero Kristo's PRCM / SCM cleanup patchset
> here:
>
> http://www.spinics.net/lists/linux-omap/msg116949.html>
>
> v1 can be found here:
>
> http://www.spinics.net/lists/linux-omap/msg116753.html>
>
> Changes sinc
Hi Guennadi,
On Wednesday 18 March 2015 22:49:07 Guennadi Liakhovetski wrote:
> On Tue, 17 Mar 2015, Oliver Lehmann wrote:
> > Hi,
> >
> > I'm using v4l2 on FreeBSD but I hope this doesn't matter that much.
> > I got a new MS LifeCam Studio HD which makes quite good pictures
> > because of its fo
Hi Oliver,
On Thursday 19 March 2015 06:57:24 Oliver Lehmann wrote:
> Hi Guennadi,
>
> Guennadi Liakhovetski wrote:
> > As for the actual question, I have no idea how they implement still
> > images: the UVC standard defines two methods for higher-resolution still
> > image capture: either using
Document new flag V4L2_CTRL_FLAG_EXECUTE_ON_WRITE, and the new behavior
of CH_VALUE event on VOLATILE controls.
Signed-off-by: Ricardo Ribalda Delgado
---
Documentation/DocBook/media/v4l/vidioc-dqevent.xml | 7 ---
Documentation/DocBook/media/v4l/vidioc-queryctrl.xml | 15 +--
Create a new flag that represent controls that represent controls that
its value needs to be passed to the driver even if it has not changed.
They typically represent actions, like triggering a flash or clearing an
error flag.
Signed-off-by: Ricardo Ribalda Delgado
---
include/uapi/linux/videod
Any control that sets FLAG_WRITE_ONLY should OR it with FLAG_ACTION.
So we can keep the current meaning of WRITE_ONLY.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/media/v4l2
Volatile controls should not generate CH_VALUE events.
Set has_changed to false to prevent this happening.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/media/v4l2-core/v4l2-ctrls.c
b/drivers
Any control with V4L2_CTRL_FLAG_EXECUTE_ON_WRITE set should return
changed == true in cluster_changed.
This forces the value to be passed to the driver even if it has not
changed.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/media/v4l2-core/v4l2-ctrls.c | 4
1 file changed, 4 inserti
This new set of patches overrides the old patchset
media/v4l2-ctrls: Always run s_ctrl on volatile ctrls
with the comments from Hans and Laurent.
Ricardo Ribalda Delgado (5):
media/v4l2-ctrls: volatiles should not generate CH_VALUE
media: New flag V4L2_CTRL_FLAG_EXECUTE_ON_WRITE
media/v4l2
Bad news. It does lock for DVB-C now, but DVB-T nor DVB-T2 does not lock.
regards
Antti
On 03/18/2015 11:37 PM, Benjamin Larsson wrote:
Signed-off-by: Benjamin Larsson
---
drivers/staging/media/mn88473/mn88473.c | 50 +++--
1 file changed, 48 insertions(+), 2 del
One number was wrong (0.6789 -> 0.6780) and Y' should have been Yc'.
Signed-off-by: Hans Verkuil
diff --git a/Documentation/DocBook/media/v4l/pixfmt.xml
b/Documentation/DocBook/media/v4l/pixfmt.xml
index 13540fa..05b595c 100644
--- a/Documentation/DocBook/media/v4l/pixfmt.xml
+++ b/Documentatio
w_scan complains about missing symbol rate limits:
This dvb driver is *buggy*: the symbol rate limits are undefined - please
report to linuxtv.org
Lets add some reasonable limits in order to keep w_scan happy :)
Signed-off-by: Antti Palosaari
---
drivers/staging/media/mn88472/mn88472.c | 2 ++
w_scan complains about missing symbol rate limits:
This dvb driver is *buggy*: the symbol rate limits are undefined - please
report to linuxtv.org
Lets add some reasonable limits in order to keep w_scan happy :)
Signed-off-by: Antti Palosaari
---
drivers/staging/media/mn88473/mn88473.c | 2 ++
When utilizing userptr buffers for output from the CCDC, the
DMA subsystem maps buffers into the virtual address space.
However, the DMA subsystem also has a configurable parameter
for what the largest segment to allocate is out of the virtual
address space as well.
Since we need contiguous buffer
Hi Sakari,
Thanks for the review.
On Wed, Mar 18, 2015 at 10:13 PM, Sakari Ailus
wrote:
> Hi Prabhakar,
>
> Lad Prabhakar wrote:
> ...
>>
>> +static int ov2659_g_volatile_ctrl(struct v4l2_ctrl *ctrl)
>> +{
>> + struct ov2659 *ov2659 =
>> + container_of(ctrl->handler,
On 03/16/15 02:26, Sakari Ailus wrote:
> Make omap3isp configuration data structures more suitable for consumption by
> the DT by separating the I2C bus information of all the sub-devices in a
> group and the ISP bus information from each other. The ISP bus information
> is made a pointer instead o
37 matches
Mail list logo
