public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, laurent.pinchart@ideasonboard.com,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Kate Hsuan <hpa@redhat.com>,
	Alexander Shiyan <eagle.alexander923@gmail.com>,
	Mikhail Rudenko <mike.rudenko@gmail.com>,
	Dave Stevenson <dave.stevenson@raspberrypi.com>,
	Tommaso Merciai <tomm.merciai@gmail.com>,
	Umang Jain <umang.jain@ideasonboard.com>,
	Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
	Sylvain Petinot <sylvain.petinot@foss.st.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Julien Massot <julien.massot@collabora.com>,
	Naushir Patuck <naush@raspberrypi.com>
Subject: [RFC 2/4] media: Documentation: Reword split of sensor driver to two classes
Date: Fri, 11 Oct 2024 10:55:33 +0300	[thread overview]
Message-ID: <20241011075535.588140-3-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20241011075535.588140-1-sakari.ailus@linux.intel.com>

The sensor drivers do not configure the output size of the sensors but the
entire internal pipeline. Reflect this in the documentation.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
 .../userspace-api/media/drivers/camera-sensor.rst      | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst
index d82cd803e337..ad4049ff7eec 100644
--- a/Documentation/userspace-api/media/drivers/camera-sensor.rst
+++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst
@@ -10,11 +10,13 @@ used to control the camera sensor drivers.
 
 You may also find :ref:`media_writing_camera_sensor_drivers` useful.
 
-Frame size
-----------
+Sensor internal pipeline configuration
+--------------------------------------
 
-There are two distinct ways to configure the frame size produced by camera
-sensors.
+The camera sensors have an internal processing pipeline including cropping and
+binning functionality. The sensor drivers belong to two distinct classes, freely
+configurable and register list based drivers, depending on how the driver
+configures this functionality.
 
 Freely configurable camera sensor drivers
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
2.39.5


  parent reply	other threads:[~2024-10-11  7:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  7:55 [RFC 0/4] Sub-device configuration models Sakari Ailus
2024-10-11  7:55 ` [RFC 1/4] media: Documentation: Rework embedded data documentation Sakari Ailus
2024-10-22 15:08   ` Jacopo Mondi
2024-11-08 12:23     ` Sakari Ailus
2024-10-22 19:27   ` Laurent Pinchart
2024-10-11  7:55 ` Sakari Ailus [this message]
2024-10-22 15:12   ` [RFC 2/4] media: Documentation: Reword split of sensor driver to two classes Jacopo Mondi
2024-10-22 19:39     ` Laurent Pinchart
2024-11-08 12:39       ` Sakari Ailus
2024-11-08 12:57         ` Laurent Pinchart
2024-10-11  7:55 ` [RFC 3/4] media: Documentation: Add subdev configuration models, raw sensor model Sakari Ailus
2024-10-22 16:02   ` Jacopo Mondi
2024-10-22 22:10     ` Laurent Pinchart
2024-11-13  7:35       ` Sakari Ailus
2024-11-13  8:20         ` Jacopo Mondi
2024-11-13 10:18           ` Sakari Ailus
2024-10-11  7:55 ` [RFC 4/4] media: v4l: ctrl: Add V4L2_CID_CONFIG_MODEL control Sakari Ailus
2024-10-22 19:42   ` Laurent Pinchart
2024-11-13  7:37     ` Sakari Ailus
2024-11-13  8:03   ` Hans Verkuil
2024-11-13  8:35     ` Sakari Ailus
2024-11-13 12:26       ` Hans Verkuil
2024-11-18  2:40         ` Laurent Pinchart
2025-02-11  8:31           ` Sakari Ailus
2025-02-13 22:47             ` Laurent Pinchart
2024-10-21 14:29 ` [RFC 0/4] Sub-device configuration models Mikhail Rudenko
2024-10-22 16:05   ` Jacopo Mondi
2024-10-22 17:40     ` Mikhail Rudenko

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=20241011075535.588140-3-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=eagle.alexander923@gmail.com \
    --cc=hpa@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=julien.massot@collabora.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mike.rudenko@gmail.com \
    --cc=naush@raspberrypi.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=sylvain.petinot@foss.st.com \
    --cc=tomm.merciai@gmail.com \
    --cc=umang.jain@ideasonboard.com \
    /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