From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: Andy Shevchenko <andy@kernel.org>,
Hans de Goede <hansg@kernel.org>,
linux-staging@lists.linux.dev
Subject: [PATCH 1/1] staging: media: atomisp: Update TODO file
Date: Sat, 18 Apr 2026 12:34:20 +0300 [thread overview]
Message-ID: <20260418093420.2205-1-sakari.ailus@linux.intel.com> (raw)
Update the TODO file to match the current state of affairs. Add sensor
drivers and make adding ISP parameter support optional.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/staging/media/atomisp/TODO | 36 ++++++++++++++++++------------
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git a/drivers/staging/media/atomisp/TODO b/drivers/staging/media/atomisp/TODO
index 82be275b4a0a..22a579eace2c 100644
--- a/drivers/staging/media/atomisp/TODO
+++ b/drivers/staging/media/atomisp/TODO
@@ -1,9 +1,10 @@
TODO
====
-1. Items which MUST be fixed before the driver can be moved out of staging:
+atomisp
+-------
-* Remove/disable private IOCTLs
+1. Items which MUST be fixed before the driver can be moved out of staging:
* Remove/disable custom v4l2-ctrls
@@ -11,19 +12,13 @@ TODO
* Remove abuse of priv field in various v4l2 userspace API structs
-* Without a 3A library the capture behaviour is not very good. To take a good
- picture, the exposure/gain needs to be tuned using v4l2-ctl on the sensor
- subdev. To fix this, support for the atomisp needs to be added to libcamera.
-
- This MUST be done before moving the driver out of staging so that we can
- still make changes to e.g. the mediactl topology if necessary for
- libcamera integration. Since this would be a userspace API break, this
- means that at least proof-of-concept libcamera integration needs to be
- ready before moving the driver out of staging.
-
+* Refactor the codebase (random cleanups won't achieve this)
2. Items which SHOULD also be fixed eventually:
+* Support ISP parameter passing via parameter buffers (see
+ drivers/media/v4l2-core/v4l2-isp.c).
+
* 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 (only a problem on BYT).
@@ -33,10 +28,23 @@ TODO
* Ensure that the driver will pass v4l2-compliance tests
-* Fix not all v4l2 apps working, e.g. cheese does not work
+sensor drivers
+--------------
+
+* Use v4l2-cci for register access
+
+* Implement enable_streams and disable_streams pad ops (use s_stream
+ compat helper)
+
+* Implement Runtime PM support (see e.g. ov8856 driver)
-* The atomisp code still has a lot of cruft which needs cleaning up
+* Use sub-device state and remove state related fields from device context
+ structs
+* Implement modern V4L2 camera sensor controls (see
+ Documentation/userspace-api/media/drivers/camera-sensor.rst) or even
+ Common Raw Sensor Model (which isn't in upsteam yet though; see
+ <URL:https://gitlab.freedesktop.org/linux-media/users/sailus/-/tree/metadata?ref_type=heads>).
Testing
=======
--
2.47.3
reply other threads:[~2026-04-18 9:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260418093420.2205-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=andy@kernel.org \
--cc=hansg@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox