Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Alexander Koskovich <AKoskovich@pm.me>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 1/2] media: dt-bindings: ovti,ov8856: Allow props from video-interface-devices
Date: Mon, 9 Mar 2026 11:13:44 +0200	[thread overview]
Message-ID: <aa6PSHDjSRgIRR3t@kekkonen.localdomain> (raw)
In-Reply-To: <20260307-ov8856-v4l2-props-v1-1-7677b4c658e4@pm.me>

Hi Alexander,

Thanks for the patch.

On Sun, Mar 08, 2026 at 04:56:04AM +0000, Alexander Koskovich wrote:
> There is no reason to restrict the allowed rotation degrees to 0 and 180,
> as the sensor can be mounted with any rotation.
> 
> Also, as all the properties described by video-interface-devices.yaml are
> allowed for the image sensor, make them accepted by changing
> additionalProperties: false" to "unevaluatedProperties: false" at the
> schema top-level.

As the relevant properties depend on the device type, I believe we should
continue to document what is relevant for a given device.

Some of the properties such as the ones that get used in the 2nd patch
could well be put into another file so we could avoid documenting each
supported property separately for e.g. raw camera sensors.

Also cc Laurent.

> 
> Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
> ---
>  Documentation/devicetree/bindings/media/i2c/ovti,ov8856.yaml | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov8856.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov8856.yaml
> index fa71f24823f2..73a9d3288897 100644
> --- a/Documentation/devicetree/bindings/media/i2c/ovti,ov8856.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov8856.yaml
> @@ -18,6 +18,9 @@ description: |-
>    through I2C and two-wire SCCB. The sensor output is available via CSI-2
>    serial data output (up to 4-lane).
>  
> +allOf:
> +  - $ref: /schemas/media/video-interface-devices.yaml#
> +
>  properties:
>    compatible:
>      const: ovti,ov8856
> @@ -94,7 +97,7 @@ required:
>    - reset-gpios
>    - port
>  
> -additionalProperties: false
> +unevaluatedProperties: false
>  
>  examples:
>    - |
> 

-- 
Regards,

Sakari Ailus

  parent reply	other threads:[~2026-03-09  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08  4:55 [PATCH 0/2] ov8856: Add V4L2 device tree properties support Alexander Koskovich
2026-03-08  4:56 ` [PATCH 1/2] media: dt-bindings: ovti,ov8856: Allow props from video-interface-devices Alexander Koskovich
2026-03-09  7:48   ` Krzysztof Kozlowski
2026-03-09  9:13   ` Sakari Ailus [this message]
2026-03-08  4:56 ` [PATCH 2/2] media: i2c: ov8856: parse and register V4L2 device tree properties Alexander Koskovich
2026-03-09  9:38   ` 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=aa6PSHDjSRgIRR3t@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=AKoskovich@pm.me \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    /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