From: Mirela Rabulea <mirela.rabulea@nxp.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl,
laurent.pinchart+renesas@ideasonboard.com, robh@kernel.org,
krzk+dt@kernel.org, bryan.odonoghue@linaro.org,
laurentiu.palcu@nxp.com, robert.chiras@nxp.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
LnxRevLi@nxp.com, kieran.bingham@ideasonboard.com,
hdegoede@redhat.com, dave.stevenson@raspberrypi.com,
mike.rudenko@gmail.com, alain.volmat@foss.st.com,
devicetree@vger.kernel.org, conor+dt@kernel.org,
alexander.stein@ew.tq-group.com, umang.jain@ideasonboard.com,
zhi.mao@mediatek.com, festevam@denx.de,
julien.vuillaumier@nxp.com
Subject: Re: [EXT] Re: [PATCH v4 1/4] dt-bindings: media: i2c: Add OX05B1S sensor
Date: Tue, 8 Jul 2025 20:02:00 +0300 [thread overview]
Message-ID: <d65191b2-0988-401f-ae6e-9e723650f64e@nxp.com> (raw)
In-Reply-To: <aGAz-TA7fjI-m76N@valkosipuli.retiisi.eu>
Hi Sakari,
On 6/28/25 21:27, Sakari Ailus wrote:
> Caution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, report the message using the 'Report this email' button
>
>
> Hi Mirela,
>
> On Wed, Mar 05, 2025 at 11:43:56AM +0200, Mirela Rabulea wrote:
>> Add bindings for Omnivision OX05B1S sensor.
>> Also add compatible for Omnivision OS08A20 sensor.
>>
>> Signed-off-by: Mirela Rabulea <mirela.rabulea@nxp.com>
>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>>
>> Changes in v4:
>> Collect Reviewed-by
>>
>> Changes in v3:
>> Use unevaluatedProperties: false and drop orientation/rotation
>> Drop items and keep alphabetical order in compatible property
>> Shorten the description for reset_gpio
>> Make the supplies required.
>> Use generic node name (camera instead of ox05b1s)
>>
>> 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)
>> Include assigned-clock* in the example, for completeness sake (although it was also suggested to omit them)
>>
>> .../bindings/media/i2c/ovti,ox05b1s.yaml | 119 ++++++++++++++++++
>> 1 file changed, 119 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/media/i2c/ovti,ox05b1s.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ox05b1s.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ox05b1s.yaml
>> new file mode 100644
>> index 000000000000..9f35b4e67bea
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ox05b1s.yaml
>> @@ -0,0 +1,119 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +# Copyright (C) 2024 NXP
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/media/i2c/ovti,ox05b1s.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Omnivision OX05B1S Image Sensor
>> +
>> +maintainers:
>> + - Mirela Rabulea <mirela.rabulea@nxp.com>
>> +
>> +description:
>> + The Omnivision OX05B1S is a 1/2.5-Inch CMOS image sensor with an active
>> + array size of 2592 x 1944. It is programmable through I2C interface.
>> + Image data is available via MIPI CSI-2 serial data output.
>> +
>> +allOf:
>> + - $ref: /schemas/media/video-interface-devices.yaml#
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - ovti,os08a20
>> + - ovti,ox05b1s
> The bindings only describe ox05b1s. How are the two different?
Indeed, thanks for pointing out. I will update the description in _v5
like this, to include also os08a20:
The Omnivision OX05B1S is a 1/2.5-Inch CMOS image sensor with an active
array size of 2592 x 1944 and raw RGB-Ir output. It is programmable
through
I2C interface. Image data is available via MIPI CSI-2 serial data output.
The Omnivision OS08A20 is a 1/1.8-Inch CMOS image sensor with an active
array size of 3840 x 2160, raw RGB output and 2-exposure staggered HDR
support.
>
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + clocks:
>> + description: Input clock (24 MHz)
>> + maxItems: 1
> Is this really a hardware limitation, or what the driver is currently
> limited to? In the former case, I'd include the range.
No, hardware is not limited to 24 MHz. I will include a range like this:
description: Input clock (6-64 MHz for OX05B1S, 6-27 MHz for OS08A20)
Thanks for feedback,
Mirela
>
>> +
>> + reset-gpios:
>> + description: Active low XSHUTDOWN pin
>> + 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)
>> +
>> + 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
>> + - avdd-supply
>> + - dovdd-supply
>> + - dvdd-supply
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/gpio/gpio.h>
>> +
>> + i2c {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + camera@36 {
>> + compatible = "ovti,ox05b1s";
>> + reg = <0x36>;
>> + clocks = <&ox05b1s_clk>;
>> +
>> + assigned-clocks = <&ox05b1s_clk>;
>> + assigned-clock-parents = <&ox05b1s_clk_parent>;
>> + assigned-clock-rates = <24000000>;
>> +
>> + reset-gpios = <&gpio1 6 GPIO_ACTIVE_LOW>;
>> +
>> + avdd-supply = <&camera_avdd_2v8>;
>> + dovdd-supply = <&camera_dovdd_1v8>;
>> + dvdd-supply = <&camera_dvdd_1v2>;
>> +
>> + orientation = <2>;
>> + rotation = <0>;
>> +
>> + port {
>> + ox05b1s_mipi_0_ep: endpoint {
>> + remote-endpoint = <&mipi_csi0_ep>;
>> + data-lanes = <1 2 3 4>;
>> + };
>> + };
>> + };
>> + };
>> +...
> --
> Kind regards,
>
> Sakari Ailus
next prev parent reply other threads:[~2025-07-08 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 9:43 [PATCH v4 0/4] media: i2c: Add OX05B1S camera sensor driver Mirela Rabulea
2025-03-05 9:43 ` [PATCH v4 1/4] dt-bindings: media: i2c: Add OX05B1S sensor Mirela Rabulea
2025-06-28 18:27 ` Sakari Ailus
2025-07-08 17:02 ` Mirela Rabulea [this message]
2025-03-05 9:43 ` [PATCH v4 2/4] media: ox05b1s: Add omnivision OX05B1S raw sensor driver Mirela Rabulea
2025-03-19 11:10 ` Jai Luthra
2025-03-24 15:32 ` Mirela Rabulea
2025-03-25 16:02 ` Jai Luthra
2025-03-26 15:32 ` Mirela Rabulea
2025-03-28 8:37 ` Jai Luthra
2025-03-31 15:42 ` [EXT] " Mirela Rabulea
2025-06-29 8:30 ` Sakari Ailus
2025-07-08 17:09 ` [EXT] " Mirela Rabulea
2025-07-08 23:43 ` Sakari Ailus
2025-07-09 11:07 ` Mirela Rabulea
2025-03-05 9:43 ` [PATCH v4 3/4] MAINTAINERS: Add entry for OX05B1S " Mirela Rabulea
2025-03-05 9:43 ` [PATCH v4 4/4] media: ox05b1s: Add support for Omnivision OS08A20 raw sensor Mirela Rabulea
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=d65191b2-0988-401f-ae6e-9e723650f64e@nxp.com \
--to=mirela.rabulea@nxp.com \
--cc=LnxRevLi@nxp.com \
--cc=alain.volmat@foss.st.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=hdegoede@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=julien.vuillaumier@nxp.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mike.rudenko@gmail.com \
--cc=robert.chiras@nxp.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sakari.ailus@linux.intel.com \
--cc=umang.jain@ideasonboard.com \
--cc=zhi.mao@mediatek.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
all inboxes | Powered by JetHome®