| Message ID | 20250203085853.1361401-2-sakari.ailus@linux.intel.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | Sub-device configuration models | expand |
On Mon, Feb 3, 2025 at 8:59 AM Sakari Ailus <sakari.ailus@linux.intel.com> wrote: > > Rework embedded data documentation by removing the reference to the pixel > data stream. The specific documentation of the embedded data interface > will be elsewhere, in the near future either CCS or common raw camera > sensor model documentation. > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> > Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com> > Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> > --- > .../userspace-api/media/drivers/camera-sensor.rst | 13 ++++++------- > 1 file changed, 6 insertions(+), 7 deletions(-) > Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Cheers, Prabhakar > diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst > index dc415b8f6c8e..8e1083417ae1 100644 > --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst > +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst > @@ -111,13 +111,12 @@ the sensor configuration for the captured frame back to the host. While CSI-2 is > the most common data interface used by such sensors, embedded data can be > available on other interfaces as well. > > -Such sensors expose two internal sink pads (pads that have both the > -``MEDIA_PAD_FL_SINK <MEDIA-PAD-FL-SINK>`` and ``MEDIA_PAD_FL_INTERNAL > -<MEDIA-PAD-FL-INTERNAL>`` flags set) to model the source of the image and > -embedded data streams. Both of these pads produces a single stream, and the > -sub-device routes those streams to the external (source) pad. If the sub-device > -driver supports disabling embedded data, this can be done by disabling the > -embedded data route via the ``VIDIOC_SUBDEV_S_ROUTING`` IOCTL. > +Embedded data support is indicated by the precence of an internal sink pad (pad > +that has both the ``MEDIA_PAD_FL_SINK <MEDIA-PAD-FL-SINK>`` and > +``MEDIA_PAD_FL_INTERNAL <MEDIA-PAD-FL-INTERNAL>`` flags set) with a metadata > +format to model the embedded data stream. If the sub-device driver supports > +disabling embedded data, this can be done by disabling the embedded data route > +via the ``VIDIOC_SUBDEV_S_ROUTING`` IOCTL. > > In general, changing the embedded data format from the driver-configured values > is not supported. The height of the metadata is device-specific and the width > -- > 2.39.5 >
diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst index dc415b8f6c8e..8e1083417ae1 100644 --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst @@ -111,13 +111,12 @@ the sensor configuration for the captured frame back to the host. While CSI-2 is the most common data interface used by such sensors, embedded data can be available on other interfaces as well. -Such sensors expose two internal sink pads (pads that have both the -``MEDIA_PAD_FL_SINK <MEDIA-PAD-FL-SINK>`` and ``MEDIA_PAD_FL_INTERNAL -<MEDIA-PAD-FL-INTERNAL>`` flags set) to model the source of the image and -embedded data streams. Both of these pads produces a single stream, and the -sub-device routes those streams to the external (source) pad. If the sub-device -driver supports disabling embedded data, this can be done by disabling the -embedded data route via the ``VIDIOC_SUBDEV_S_ROUTING`` IOCTL. +Embedded data support is indicated by the precence of an internal sink pad (pad +that has both the ``MEDIA_PAD_FL_SINK <MEDIA-PAD-FL-SINK>`` and +``MEDIA_PAD_FL_INTERNAL <MEDIA-PAD-FL-INTERNAL>`` flags set) with a metadata +format to model the embedded data stream. If the sub-device driver supports +disabling embedded data, this can be done by disabling the embedded data route +via the ``VIDIOC_SUBDEV_S_ROUTING`` IOCTL. In general, changing the embedded data format from the driver-configured values is not supported. The height of the metadata is device-specific and the width