linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil-cisco@xs4all.nl>
To: Jacopo Mondi <jacopo@jmondi.org>,
	"open list:MEDIA INPUT INFRASTRUCTURE (V4L/DVB)" 
	<linux-media@vger.kernel.org>,
	libcamera-devel@lists.libcamera.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: tfiga@google.com, pavel@ucw.cz
Subject: Re: [PATCH v10 04/13] media: v4l2-ctrl: Document V4L2_CID_CAMERA_ORIENTATION
Date: Fri, 8 May 2020 13:02:27 +0200	[thread overview]
Message-ID: <eea16d6b-bc58-a78a-c4c8-6f857251a047@xs4all.nl> (raw)
In-Reply-To: <20200508100158.3437161-5-jacopo@jmondi.org>

On 08/05/2020 12:01, Jacopo Mondi wrote:
> Add documentation for the V4L2_CID_CAMERA_ORIENTATION camera
> control. The newly added read-only control reports the camera device
> orientation relative to the usage orientation of the system the camera
> is installed on.
> 
> Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
> ---
>  .../media/v4l/ext-ctrls-camera.rst            | 30 +++++++++++++++++++
>  1 file changed, 30 insertions(+)
> 
> diff --git a/Documentation/userspace-api/media/v4l/ext-ctrls-camera.rst b/Documentation/userspace-api/media/v4l/ext-ctrls-camera.rst
> index e39f84d2447f8..01e104bab6b3d 100644
> --- a/Documentation/userspace-api/media/v4l/ext-ctrls-camera.rst
> +++ b/Documentation/userspace-api/media/v4l/ext-ctrls-camera.rst
> @@ -510,6 +510,36 @@ enum v4l2_scene_mode -
>      value down. A value of zero stops the motion if one is in progress
>      and has no effect otherwise.
>  
> +``V4L2_CID_CAMERA_ORIENTATION (integer)``

integer -> menu

> +    This read-only control describes the camera orientation by reporting
> +    its mounting position on the device where the camera is installed. The
> +    control value is constant and not modifiable by software. This control is
> +    particularly meaningful for devices which have a well defined orientation,
> +    such as phones, laptops and portable devices since the control is expressed
> +    as a position relative to the device's intended usage orientation.
> +    For example, a camera installed on the user-facing side of a phone,
> +    a tablet or a laptop device is said to be have ``V4L2_ORIENTATION_FRONT``
> +    orientation, while a camera installed on the opposite side of the front one
> +    is said to be have ``V4L2_ORIENTATION_BACK`` orientation. Camera sensors not
> +    directly attached to the device, or attached in a way that allows them to
> +    move freely, such as webcams and digital cameras, are said to have the
> +    ``V4L2_ORIENTATION_EXTERNAL`` orientation.
> +
> +
> +
> +.. flat-table::
> +    :header-rows:  0
> +    :stub-columns: 0
> +
> +    * - ``V4L2_ORIENTATION_FRONT``

This really should be V4L2_CAMERA_ORIENTATION_FRONT. Yes, it is long, but just
'ORIENTATION' doesn't tell you which orientation is meant, that's too generic.

Regards,

	Hans

> +      - The camera is oriented towards the user facing side of the device.
> +    * - ``V4L2_ORIENTATION_BACK``
> +      - The camera is oriented towards the back facing side of the device.
> +    * - ``V4L2_ORIENTATION_EXTERNAL``
> +      - The camera is not directly attached to the device and is freely movable.
> +
> +
> +
>  .. [#f1]
>     This control may be changed to a menu control in the future, if more
>     options are required.
> 


  reply	other threads:[~2020-05-08 11:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 10:01 [PATCH v10 00/13] media: report camera properties Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 01/13] dt-bindings: video-interfaces: Document 'orientation' property Jacopo Mondi
2020-05-11 17:20   ` Rob Herring
2020-05-12  7:21     ` Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 02/13] dt-bindings: video-interface: Replace 'rotation' description Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 03/13] dt-bindings: Add media properties Jacopo Mondi
2020-05-08 11:04   ` Hans Verkuil
2020-05-09  8:21     ` Jacopo Mondi
2020-05-11  7:21       ` Sakari Ailus
2020-05-08 10:01 ` [PATCH v10 04/13] media: v4l2-ctrl: Document V4L2_CID_CAMERA_ORIENTATION Jacopo Mondi
2020-05-08 11:02   ` Hans Verkuil [this message]
2020-05-08 10:01 ` [PATCH v10 05/13] media: v4l2-ctrl: Document V4L2_CID_CAMERA_SENSOR_ROTATION Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 06/13] media: v4l2-ctrls: Add camera orientation and rotation Jacopo Mondi
2020-05-08 11:09   ` Hans Verkuil
2020-05-08 10:01 ` [PATCH v10 07/13] media: v4l2-fwnode: Add helper to parse device properties Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 08/13] include: v4l2-ctrl: Sort forward declarations Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 09/13] media: v4l2-ctrls: Sort includes alphabetically Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 10/13] media: v4l2-ctrls: Add helper to register properties Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 11/13] media: i2c: ov5670: Parse and " Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 12/13] media: i2c: ov13858: " Jacopo Mondi
2020-05-08 10:01 ` [PATCH v10 13/13] media: i2c: imx219: " Jacopo Mondi

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=eea16d6b-bc58-a78a-c4c8-6f857251a047@xs4all.nl \
    --to=hverkuil-cisco@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=libcamera-devel@lists.libcamera.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=sakari.ailus@linux.intel.com \
    --cc=tfiga@google.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;
as well as URLs for NNTP newsgroup(s).