The module is still called 'hva'. I suggest calling it sti-hva instead.
> Format ioctls:
> test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: OK
> warn:
> /local/home/frq08988/views/opensdk-2.1.4.1/sources/v4l-utils/utils/v4l2-compliance/v4l2-test-formats.cpp(1187):
> S_PARM is supported for buftype 1, but not ENUM_FRAMEINTERVALS
> warn:
> /local/home/frq08988/views/opensdk-2.1.4.1/sources/v4l-utils/utils/v4l2-compliance/v4l2-test-formats.cpp(1187):
> S_PARM is supported for buftype 2, but not ENUM_FRAMEINTERVALS
So why is S_PARM supported? I asked about that in my review, but I got no
answer.
I've never seen that for m2m devices, and it really makes no sense IMHO.
The 'framerate' is typically driven by how often new frames are submitted by the
user. It's not up to the driver to mess with that.
Regards,
Hans
--
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
