linux-kernel - VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL: continuous frame interval

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAH1Ww+RT=W9zhbv8A-gQscCPq5jWHOX3SFFeU07cXBngKH4C3Q@mail.gmail.com>
Date:   Fri, 4 Oct 2019 09:59:05 +0200
From:   Daniel Gomez <daniel@...c.com>
To:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Hans Verkuil <hverkuil@...all.nl>, sakari.ailus@...ux.intel.com
Cc:     Linux Media Mailing List <linux-media@...r.kernel.org>,
        linux-kernel@...r.kernel.org
Subject: VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL: continuous frame interval

Hi all,

We are developing a v4l2 subdevice driver to be able to support the imx378
sensor and upstream it. But we would like to have a continuous frame
interval and the
current VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL ioctl implementation doesn't
support it.

How can we proceed here? Can we maybe add the limits by using the reserved area
of v4l2_subdev_frame_interval_enum struct? Something similar to
v4l2_subdev_frame_size_enum is doing with continuous frame size.

I guess it would also need to adapt v4l2-ctl, v4l2-compliance and so on but not
really sure about the whole impact in linuxtv/linux-media of this need.

Thanks in advance,
Daniel