Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit af7db4e9 authored by Sakari Ailus's avatar Sakari Ailus Committed by Mauro Carvalho Chehab
Browse files

media: staging: atomisp: Update TODO regarding sensors



There was no specific item regarding what should be done to sensor, lens
and flash drivers. Add one, to replace the vague item denoting support
only to particular sensor, lens and flash devices.

Signed-off-by: default avatarSakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
parent 90ebe55a
Loading
Loading
Loading
Loading
+15 −7
Original line number Diff line number Diff line
@@ -36,13 +36,21 @@
   there are any specific things that can be done to fold in support for
   multiple firmware versions.

8. Switch to V4L2 async API to set up sensor, lens and flash devices.
   Control those devices using V4L2 sub-device API without custom
   extensions.

Limitations:
9. Switch to standard V4L2 sub-device API for sensor and lens. In
   particular, the user space API needs to support V4L2 controls as
   defined in the V4L2 spec and references to atomisp must be removed from
   these drivers.

10. Use LED flash API for flash LED drivers such as LM3554 (which already
    has a LED class driver).

1. Currently the patch only support some camera sensors
   gc2235/gc0310/0v2680/ov2722/ov5693/mt9m114...
Limitations:

2. To test the patches, you also need the ISP firmware
1. To test the patches, you also need the ISP firmware

   for BYT:/lib/firmware/shisp_2400b0_v21.bin
   for CHT:/lib/firmware/shisp_2401a0_v21.bin
@@ -51,14 +59,14 @@ Limitations:
   device but can also be extracted from the upgrade kit if you've managed
   to lose them somehow.

3. Without a 3A libary the capture behaviour is not very good. To take a good
2. Without a 3A libary the capture behaviour is not very good. To take a good
   picture, you need tune ISP parameters by IOCTL functions or use a 3A libary
   such as libxcam.

4. The driver is intended to drive the PCI exposed versions of the device.
3. The driver is intended to drive the PCI exposed versions of the device.
   It will not detect those devices enumerated via ACPI as a field of the
   i915 GPU driver.

5. The driver supports only v2 of the IPU/Camera. It will not work with the
4. The driver supports only v2 of the IPU/Camera. It will not work with the
   versions of the hardware in other SoCs.