Hello!
On 07/06/2017 09:16 PM, Sergei Shtylyov wrote:
[...]
+=========================================
+
+This file documents some driver-specific aspects of the IMR driver, such as
+driver-specific ioctls.
+
+The ioctl reference
+~~~~~~~~~~~~~~~~~~~
+
+VIDIOC_IMR_MESH - Set mapping data
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Argument: struct imr_map_desc
+
+**Description**:
+
+ This ioctl sets up the mesh using which the input frames will be
s/using/through/
+ transformed into the output frames. The mesh can be strictly rectangular
+ (when IMR_MAP_MESH bit is set in imr_map_desc::type) or arbitrary (when
+ that bit is not set).
+
+ A rectangular mesh consists of the imr_mesh structure followed by M*N
+ vertex objects (where M is imr_mesh::rows and N is imr_mesh::columns).
+ In case either IMR_MAP_AUTOSG or IMR_MAP_AUTODG bits were set in
+ imr_map_desc::type, imr_mesh::{x|y}0 specify the coordinates of the top
+ left corner of the auto-generated mesh and imr_mesh::d{x|y} specify the
+ mesh's X/Y steps.
What if any of the other types are used like IMR_MAP_LUCE?
IMR_MAP_LUCE only affects the vertex object.
Is this documented in a Renesas datasheet?
Yes.
Well, not exactly. The different mesh types are a software concept, the
hardware only understands series of triangles.
[...]
Regards,
Hans
MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
