| Message ID | 20250203085853.1361401-3-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: > > Add a hyphen to list-based for uniform spelling in camera-sensor.rst. > > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com> > Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com> > Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> > --- > Documentation/userspace-api/media/drivers/camera-sensor.rst | 6 +++--- > 1 file changed, 3 insertions(+), 3 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 8e1083417ae1..9a1e8aa9fc77 100644 > --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst > +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst > @@ -26,10 +26,10 @@ of cropping and scaling operations from the device's pixel array's size. > > An example of such a driver is the CCS driver. > > -Register list based drivers > +Register list-based drivers > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > -Register list based drivers generally, instead of able to configure the device > +Register list-based drivers generally, instead of able to configure the device > they control based on user requests, are limited to a number of preset > configurations that combine a number of different parameters that on hardware > level are independent. How a driver picks such configuration is based on the > @@ -67,7 +67,7 @@ is pixels and the unit of the ``V4L2_CID_VBLANK`` is lines. The pixel rate in > the sensor's **pixel array** is specified by ``V4L2_CID_PIXEL_RATE`` in the same > sub-device. The unit of that control is pixels per second. > > -Register list based drivers need to implement read-only sub-device nodes for the > +Register list-based drivers need to implement read-only sub-device nodes for the > purpose. Devices that are not register list based need these to configure the > device's internal processing pipeline. > > -- > 2.39.5 >
diff --git a/Documentation/userspace-api/media/drivers/camera-sensor.rst b/Documentation/userspace-api/media/drivers/camera-sensor.rst index 8e1083417ae1..9a1e8aa9fc77 100644 --- a/Documentation/userspace-api/media/drivers/camera-sensor.rst +++ b/Documentation/userspace-api/media/drivers/camera-sensor.rst @@ -26,10 +26,10 @@ of cropping and scaling operations from the device's pixel array's size. An example of such a driver is the CCS driver. -Register list based drivers +Register list-based drivers ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Register list based drivers generally, instead of able to configure the device +Register list-based drivers generally, instead of able to configure the device they control based on user requests, are limited to a number of preset configurations that combine a number of different parameters that on hardware level are independent. How a driver picks such configuration is based on the @@ -67,7 +67,7 @@ is pixels and the unit of the ``V4L2_CID_VBLANK`` is lines. The pixel rate in the sensor's **pixel array** is specified by ``V4L2_CID_PIXEL_RATE`` in the same sub-device. The unit of that control is pixels per second. -Register list based drivers need to implement read-only sub-device nodes for the +Register list-based drivers need to implement read-only sub-device nodes for the purpose. Devices that are not register list based need these to configure the device's internal processing pipeline.