linux-kernel - Re: [PATCH v2 1/4] dt-bindings: media: i2c: Add OX05B1S sensor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <oj3y3bx2ojah3meyc5ttnm2j2jjx4fq6xezbxkz265cygcilct@avdydgmfcltc>
Date: Wed, 27 Nov 2024 09:25:47 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Mirela Rabulea <mirela.rabulea@....com>
Cc: mchehab@...nel.org, sakari.ailus@...ux.intel.com, 
	hverkuil-cisco@...all.nl, laurent.pinchart+renesas@...asonboard.com, robh@...nel.org, 
	krzk+dt@...nel.org, bryan.odonoghue@...aro.org, laurentiu.palcu@....com, 
	robert.chiras@....com, linux-media@...r.kernel.org, linux-kernel@...r.kernel.org, 
	LnxRevLi@....com, kieran.bingham@...asonboard.com, hdegoede@...hat.com, 
	dave.stevenson@...pberrypi.com, mike.rudenko@...il.com, alain.volmat@...s.st.com, 
	devicetree@...r.kernel.org, conor+dt@...nel.org, alexander.stein@...tq-group.com, 
	umang.jain@...asonboard.com, zhi.mao@...iatek.com, festevam@...x.de, 
	julien.vuillaumier@....com, alice.yuan@....com
Subject: Re: [PATCH v2 1/4] dt-bindings: media: i2c: Add OX05B1S sensor

On Tue, Nov 26, 2024 at 05:50:57PM +0200, Mirela Rabulea wrote:
> Add bindings for Omnivision OX05B1S sensor.
> Also add compatible for Omnivision OS08A20 sensor.
> 
> Signed-off-by: Mirela Rabulea <mirela.rabulea@....com>
> ---
> 
> Changes in v2:
> 	Small updates on description
> 	Update subject, drop "bindings" and "driver"
> 	Just one binding patch (squash os08a20 bindings)
> 	Re-flow to 80 columns.
> 	Drop clock name (not needed in case of single clock)
> 	Make the clock required property, strictly from sensor module point of view, it is mandatory (will use a fixed clock for nxp board)
> 	Add regulators: avdd, dvdd, dovdd
> 	Add $ref: /schemas/media/video-interface-devices.yaml
> 	Drop assigned-clock* properties (defined in clocks.yaml)
> 	Keep "additionalProperties : false" and orientation/rotation (unevaluatedProperties: false was suggested, but only orientation/rotation are needed from video-interface-devices.yaml)

I don't understand why you did not follow that advice. Reasoning is not
really correct - if this is video interface device, then we expect
entire schema to be somehow applicable. You will now get the same review
comment.

> +allOf:
> +  - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> +  compatible:
> +    items:

You can drop items here, for simpler code.

> +      - enum:
> +          - ovti,ox05b1s
> +          - ovti,os08a20

Keep alphabetical order.

> +
> +  reg:
> +    maxItems: 1
> +
> +  clocks:
> +    description: Input clock (24 MHz)
> +    maxItems: 1
> +
> +  reset-gpios:
> +    description: Reference to the GPIO connected to XSHUTDOWN pin. Active low.

"Active low XSHUTDOWN pin". No need to repeat that GPIO phandle is a
reference to the GPIO.


> +    maxItems: 1
> +
> +  avdd-supply:
> +    description: Power for analog circuit (2.8V)
> +
> +  dovdd-supply:
> +    description: Power for I/O circuit (1.8V)
> +
> +  dvdd-supply:
> +    description: Power for digital circuit (1.2V)
> +
> +  orientation: true
> +
> +  rotation: true

Drop these two and use unevaluatedProperties: false at the end.

> +
> +  port:
> +    $ref: /schemas/graph.yaml#/$defs/port-base
> +    additionalProperties: false
> +    description: MIPI CSI-2 transmitter port
> +
> +    properties:
> +      endpoint:
> +        $ref: /schemas/media/video-interfaces.yaml#
> +        unevaluatedProperties: false
> +
> +        properties:
> +          data-lanes:
> +            anyOf:
> +              - items:
> +                  - const: 1
> +                  - const: 2
> +              - items:
> +                  - const: 1
> +                  - const: 2
> +                  - const: 3
> +                  - const: 4
> +        required:
> +          - data-lanes
> +
> +    required:
> +      - endpoint
> +
> +required:
> +  - compatible
> +  - reg
> +  - clocks
> +  - port

Supplies should be required. Devices rarely work without power.

> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    #include <dt-bindings/gpio/gpio.h>
> +
> +    i2c {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +
> +        ox05b1s@36 {

Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation

Best regards,
Krzysztof