Merge tag 'media/v5.9-3' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media

* Sony 1/2.5-Inch 8.51Mp CMOS Digital Image Sensor

The Sony imx274 is a 1/2.5-inch CMOS active pixel digital image sensor with

an active array size of 3864H x 2202V. It is programmable through I2C

interface. The I2C address is fixed to 0x1a as per sensor data sheet.

Image data is sent through MIPI CSI-2, which is configured as 4 lanes

at 1440 Mbps.

Required Properties:

- compatible: value should be "sony,imx274" for imx274 sensor

- reg: I2C bus address of the device

Optional Properties:

- reset-gpios: Sensor reset GPIO

- clocks: Reference to the input clock.

- clock-names: Should be "inck".

- VANA-supply: Sensor 2.8v analog supply.

- VDIG-supply: Sensor 1.8v digital core supply.

- VDDL-supply: Sensor digital IO 1.2v supply.

The imx274 device node should contain one 'port' child node with

an 'endpoint' subnode. For further reading on port node refer to

Documentation/devicetree/bindings/media/video-interfaces.txt.

Example:

	sensor@1a {

		compatible = "sony,imx274";

		reg = <0x1a>;

		#address-cells = <1>;

		#size-cells = <0>;

		reset-gpios = <&gpio_sensor 0 0>;

		port {

			sensor_out: endpoint {

				remote-endpoint = <&csiss_in>;

			};

		};

	};

# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)

%YAML 1.2

---

$id: http://devicetree.org/schemas/media/i2c/sony,imx274.yaml#

$schema: http://devicetree.org/meta-schemas/core.yaml#

title: Sony 1/2.5-Inch 8.51MP CMOS Digital Image Sensor

maintainers:

  - Leon Luo <leonl@leopardimaging.com>

description: |

  The Sony IMX274 is a 1/2.5-inch CMOS active pixel digital image sensor with an

  active array size of 3864H x 2202V. It is programmable through I2C interface.

  Image data is sent through MIPI CSI-2, which is configured as 4 lanes at 1440

  Mbps.

properties:

  compatible:

    const: sony,imx274

  reg:

    const: 0x1a

  reset-gpios:

    maxItems: 1

  clocks:

    maxItems: 1

  clock-names:

    const: inck

  vana-supply:

    description: Sensor 2.8 V analog supply.

    maxItems: 1

  vdig-supply:

    description: Sensor 1.8 V digital core supply.

    maxItems: 1

  vddl-supply:

    description: Sensor digital IO 1.2 V supply.

    maxItems: 1

  port:

    type: object

    description: Output video port. See ../video-interfaces.txt.

required:

  - compatible

  - reg

  - port

additionalProperties: false

examples:

  - |

    i2c0 {

        #address-cells = <1>;

        #size-cells = <0>;

        imx274: camera-sensor@1a {

            compatible = "sony,imx274";

            reg = <0x1a>;

            reset-gpios = <&gpio_sensor 0 0>;

            port {

                sensor_out: endpoint {

                    remote-endpoint = <&csiss_in>;

                };

            };

        };

    };

...

    :stub-columns: 0

    :widths:       3 1 4

    * .. _`V4L2-FLAG-MEMORY-NON-CONSISTENT`:

      - ``V4L2_FLAG_MEMORY_NON_CONSISTENT``

      - 0x00000001

      - A buffer is allocated either in consistent (it will be automatically

	coherent between the CPU and the bus) or non-consistent memory. The

	latter can provide performance gains, for instance the CPU cache

	sync/flush operations can be avoided if the buffer is accessed by the

	corresponding device only and the CPU does not read/write to/from that

	buffer. However, this requires extra care from the driver -- it must

	guarantee memory consistency by issuing a cache flush/sync when

	consistency is needed. If this flag is set V4L2 will attempt to

	allocate the buffer in non-consistent memory. The flag takes effect

	only if the buffer is used for :ref:`memory mapping <mmap>` I/O and the

	queue reports the :ref:`V4L2_BUF_CAP_SUPPORTS_MMAP_CACHE_HINTS

	<V4L2-BUF-CAP-SUPPORTS-MMAP-CACHE-HINTS>` capability.

.. c:type:: v4l2_memory

enum v4l2_memory

	If you want to just query the capabilities without making any

	other changes, then set ``count`` to 0, ``memory`` to

	``V4L2_MEMORY_MMAP`` and ``format.type`` to the buffer type.

    * - __u32

      - ``flags``

      - Specifies additional buffer management attributes.

	See :ref:`memory-flags`.

    * - __u32

      - ``reserved``\ [6]

      - ``reserved``\ [7]

      - A place holder for future extensions. Drivers and applications

	must set the array to zero.

	``V4L2_MEMORY_MMAP`` and ``type`` set to the buffer type. This will

	free any previously allocated buffers, so this is typically something

	that will be done at the start of the application.

    * - union {

      - (anonymous)

    * - __u32

      - ``flags``

      - Specifies additional buffer management attributes.

	See :ref:`memory-flags`.

    * - __u32

      - ``reserved``\ [1]

      - Kept for backwards compatibility. Use ``flags`` instead.

    * - }

      -

      - A place holder for future extensions. Drivers and applications

	must set the array to zero.

.. tabularcolumns:: |p{6.1cm}|p{2.2cm}|p{8.7cm}|

      - This capability is set by the driver to indicate that the queue supports

        cache and memory management hints. However, it's only valid when the

        queue is used for :ref:`memory mapping <mmap>` streaming I/O. See

        :ref:`V4L2_FLAG_MEMORY_NON_CONSISTENT <V4L2-FLAG-MEMORY-NON-CONSISTENT>`,

        :ref:`V4L2_BUF_FLAG_NO_CACHE_INVALIDATE <V4L2-BUF-FLAG-NO-CACHE-INVALIDATE>` and

        :ref:`V4L2_BUF_FLAG_NO_CACHE_CLEAN <V4L2-BUF-FLAG-NO-CACHE-CLEAN>`.