Adding support for those two ioctls are trivial, and allow testing different resolutions with the driver. Together with some improvements I made at camorama, it is now possible to change the atomisp sensor's resolution at the GUI. Talking about camorama, I also added there an option to disable the Gtk cairo_scale() calls. On my tests here, placing ov2680 on its maximum resolution, I'm getting a framerate of 26 fps, which sounds reasonable, as the maximum would be 30fps, and I'm not using daylight. When letting cairo_scale() to run, the rate reduces to 8 fps, meaning that Gtk is not using GPU acceleration. Funny enough, when resolution is lower, atomisp is giving a very bad framerate (around 3fps, even with the scaler disabled). This is a very weird result, probably indicating some problems inside the driver. That requires further investigation. Mauro Carvalho Chehab (3): media: atomisp-ov2680: implement enum frame intervals media: atomisp-ov2680: adjust the maximum frame rate media: atomisp: implement enum framesize/frameinterval .../media/atomisp/i2c/atomisp-ov2680.c | 21 ++++++++ drivers/staging/media/atomisp/i2c/ov2680.h | 14 ++--- .../staging/media/atomisp/pci/atomisp_ioctl.c | 53 +++++++++++++++++++ 3 files changed, 81 insertions(+), 7 deletions(-) -- 2.33.1
