On 06/08/2020 12:08, Jacopo Mondi wrote:
> Hi Hans,
>
> On Thu, Aug 06, 2020 at 10:45:17AM +0200, Hans Verkuil wrote:
>> On 05/08/2020 12:57, Jacopo Mondi wrote:
>>> Provide a table to describe how the V4L2 selection targets can be used
>>> to access an image sensor pixel array properties.
>>>
>>> Reference the table in the sub-device documentation.
>>>
>>> Signed-off-by: Jacopo Mondi <jacopo@xxxxxxxxxx>
>>> ---
>>> .../userspace-api/media/v4l/dev-subdev.rst | 4 ++
>>> .../media/v4l/v4l2-selection-targets.rst | 49 +++++++++++++++++++
>>> 2 files changed, 53 insertions(+)
>>>
>>> diff --git a/Documentation/userspace-api/media/v4l/dev-subdev.rst b/Documentation/userspace-api/media/v4l/dev-subdev.rst
>>> index c47861dff9b9b..2f7da3832f458 100644
>>> --- a/Documentation/userspace-api/media/v4l/dev-subdev.rst
>>> +++ b/Documentation/userspace-api/media/v4l/dev-subdev.rst
>>> @@ -467,6 +467,10 @@ desired image resolution. If the sub-device driver supports that, userspace
>>> can set the analog crop rectangle to select which portion of the pixel array
>>> to read out.
>>>
>>> +A description of each of the above mentioned targets when used to access the
>>> +image sensor pixel array properties is provided by
>>> +:ref:`v4l2-selection-targets-image-sensor-table`
>>> +
>>>
>>> Types of selection targets
>>> --------------------------
>>> diff --git a/Documentation/userspace-api/media/v4l/v4l2-selection-targets.rst b/Documentation/userspace-api/media/v4l/v4l2-selection-targets.rst
>>> index 69f500093aa2a..632e6448b784e 100644
>>> --- a/Documentation/userspace-api/media/v4l/v4l2-selection-targets.rst
>>> +++ b/Documentation/userspace-api/media/v4l/v4l2-selection-targets.rst
>>> @@ -76,3 +76,52 @@ of the two interfaces they are used.
>>> modified by hardware.
>>> - Yes
>>> - No
>>> +
>>> +
>>> +.. _v4l2-selection-targets-image-sensor-table:
>>> +
>>> +********************************************
>>> +Selection Targets For Pixel Array Properties
>>> +********************************************
>>> +
>>> +The V4L2 selection API can be used to retrieve the size and disposition of the
>>> +pixel units that compose and image sensor pixel matrix when applied to a video
>>> +sub-device that represents an image sensor.
>>> +
>>> +A description of the properties associated with each of the sensor pixel array
>>> +areas is provided by the :ref:`v4l2-subdev-pixel-array-properties` section.
>>> +
>>> +.. tabularcolumns:: |p{6.0cm}|p{1.4cm}|p{7.4cm}|p(1.4cm)|
>>> +
>>> +.. flat-table:: Selection target definitions
>>> + :header-rows: 1
>>> + :stub-columns: 0
>>> +
>>> + * - Target name
>>> + - id
>>> + - Definition
>>> + - Read/Write
>>> + * - ``V4L2_SEL_TGT_CROP``
>>> + - 0x0000
>>> + - The analog crop rectangle. Represents the portion of the active pixel
>>> + array which is processed to produce images.
>>> + - RW
>>> + * - ``V4L2_SEL_TGT_CROP_DEFAULT``
>>> + - 0x0001
>>> + - The active pixel array rectangle. It includes only active pixels and
>>> + excludes other ones such as optical black pixels. Its width and height
>>> + represent the maximum image resolution an image sensor can produce.
>>> + - RO
>>> + * - ``V4L2_SEL_TGT_CROP_BOUNDS``
>>> + - 0x0002
>>> + - The readable portion of the physical pixel array matrix. It includes
>>> + pixels that contains valid image data and calibration pixels such as the
>>> + optical black ones.
>>> + - RO
>>> + * - ``V4L2_SEL_TGT_NATIVE_SIZE``
>>> + - 0x0003
>>> + - The physical pixel array size, including readable and not readable
>>> + pixels. As pixels that cannot be read from application processor are not
>>> + relevant for calibration purposes, this rectangle is useful to calculate
>>> + the physical properties of the image sensor.
>>> + - RO
>>>
>>
>> Hmm, this basically just duplicates the previous patch.
>>
>> I think you are documenting things at the wrong place. What you documented in the
>> previous patch really belongs here since it is shared between the subdev API and the
>> regular V4L2 API. And in dev-subdev.rst you then refer to here.
>
> I originally had it here, but then I moved to dev-subdev as an image
> sensor will always be represented as a video sub-device, doen't it ?
No. Some camera drivers are V4L2 only, most notably uvc. Also there are several simple
platform drivers that don't use the subdev API.
>
>>
>> Frankly, the selection API documentation is a mess. It's spread out over various sections:
>
> I know :(
>
>> The VIDIOC_G/S_SELECTION and VIDIOC_SUBDEV_G/S_SELECTION descriptions in the Function Reference,
>> section 8 ("Common definitions for V4L2 and V4L2 subdev interfaces"), 1.25 "Cropping, composing
>> and scaling – the SELECTION API" and 4.13.3.2-4.13.3.3 "Selections: cropping, scaling and composition".
>>
>> In my view section 8 should be moved to section 1.25.2. Ideally 1.25 should be rewritten for both
>> the V4L2 and V4L2 subdev APIs, but that's a lot of work.
>
> That's a lot of work indeed. But it could be split as
>
> 1) Augment the 1.25.1 section with a mention of subdev, maybe using
> pieces of 4.13.3.2
> 2) Move what's in section 8 to be 1.25.x
> Actually merging 1.25.2 and 8.1.1, splitting 1.25.2 in a device and
> sub-device section
>>
>> I would suggest that you add a first patch that moves section 8 to 1.25.2. Note that I don't like
>> the tables for the selection targets and flags: the 'Valid for V4L2/V4L2 subdevs' columns should
>> be removed and it should either be mentioned in the definition if a target/flag is invalid for
>> an API, or it should be put in a separate table.
>
> Two tables seems about right
>
>>
>> And in 1.25.2 perhaps a new picture can be created for the specific sensor use-case that includes
>> the NATIVE_SIZE target.
>
> I know 'image sensor' is not an API concept like device and subdevice,
> but if we split 1.25.2 in 'video device' and 'subdevice' parts, a
> section for 'image sensors' with what I've now put in section 4.13.3.3
> (the description of the sensor array areas) could fit there ?
I think so.
>
> Seems like a long re-work. Can the imx219 patch be broke out and
> fast-tracked ?
Yes.
Regards,
Hans
>
> Thanks
> j
>
>>
>> Another pet peeve of mine is that section 8 splits the selection targets and flags into separate
>> subsections. I'd just keep it in one section.
>>
>> Regards,
>>
>> Hans
