From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Vladimir Zapolskiy" <vladimir.zapolskiy@linaro.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Hans Verkuil" <hverkuil@kernel.org>,
"Hans de Goede" <hansg@kernel.org>
Cc: "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>
Subject: Re: [PATCH v3 1/2] dt-bindings: media: i2c: Add Samsung S5KJN1 image sensor
Date: Tue, 04 Nov 2025 11:20:58 +0100 [thread overview]
Message-ID: <DDZU2RL00UD8.39GS3LN0SW7YA@fairphone.com> (raw)
In-Reply-To: <20251023025356.2421327-2-vladimir.zapolskiy@linaro.org>
Hi Vladimir,
On Thu Oct 23, 2025 at 4:53 AM CEST, Vladimir Zapolskiy wrote:
> Add device tree bindings documentation for Samsung S5KJN1 image sensor.
Awesome that you're working on upstreaming support for this sensor!
This sensor is used for the front camera on the Fairphone 5 so I'll give
it a try sometime soon. So far I've been using my own version of the
driver in my tree.
Some comments below.
>
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> ---
> .../bindings/media/i2c/samsung,s5kjn1.yaml | 103 ++++++++++++++++++
> 1 file changed, 103 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/samsung,s5kjn1.yaml
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/samsung,s5kjn1.yaml b/Documentation/devicetree/bindings/media/i2c/samsung,s5kjn1.yaml
> new file mode 100644
> index 000000000000..f0cc0209b5f0
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/i2c/samsung,s5kjn1.yaml
> @@ -0,0 +1,103 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/media/i2c/samsung,s5kjn1.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Samsung S5KJN1 Image Sensor
> +
> +description:
> + Samsung S5KJN1 (ISOCELL JN1) image sensor is a 50MP image sensor.
> + The sensor is controlled over a serial camera control bus protocol,
> + the widest supported output image frame size is 8160x6144 at 10 frames
> + per second rate, data output format is RAW10 transferred over 4-lane
> + MIPI D-PHY interface.
> +
> +maintainers:
> + - Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
> +
> +allOf:
> + - $ref: /schemas/media/video-interface-devices.yaml#
> +
> +properties:
> + compatible:
> + const: samsung,s5kjn1
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + description: MCLK supply clock.
> + maxItems: 1
> +
> + reset-gpios:
> + description: Active low GPIO connected to RESET pad of the sensor.
> + maxItems: 1
> +
> + afvdd-supply:
> + description: Autofocus voltage supply, 2.8-3.0 volts.
This is not part of the S5KJN1 though? If you have a VCM for the lens of
the S5KJN1, this is a separate DT node?
> +
> + avdd-supply:
> + description: Analogue voltage supply, 2.8 volts.
The datasheet calls this VDDA
> +
> + dovdd-supply:
> + description: Digital I/O voltage supply, 1.8 volts.
The datasheet calls this VDDIO
> +
> + dvdd-supply:
> + description: Digital core voltage supply, 1.05 volts.
The datasheet calls this VDDD
Regards
Luca
> +
> + port:
> + $ref: /schemas/graph.yaml#/$defs/port-base
> + additionalProperties: false
> +
> + properties:
> + endpoint:
> + $ref: /schemas/media/video-interfaces.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + data-lanes:
> + items:
> + - const: 1
> + - const: 2
> + - const: 3
> + - const: 4
> +
> + required:
> + - link-frequencies
> +
> +required:
> + - compatible
> + - reg
> + - port
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> +
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + camera@56 {
> + compatible = "samsung,s5kjn1";
> + reg = <0x56>;
> + clocks = <&camera_mclk 0>;
> + assigned-clocks = <&camera_mclk 0>;
> + assigned-clock-rates = <24000000>;
> + reset-gpios = <&gpio1 10 GPIO_ACTIVE_LOW>;
> + avdd-supply = <&vreg_2p8>;
> + dovdd-supply = <&vreg_1p8>;
> + dvdd-supply = <&vreg_1p05>;
> +
> + port {
> + endpoint {
> + link-frequencies = /bits/ 64 <700000000>;
> + remote-endpoint = <&mipi_csi2_ep>;
> + };
> + };
> + };
> + };
> +...
next prev parent reply other threads:[~2025-11-04 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-23 2:53 [PATCH v3 0/2] media: i2c: add Samsung S5KJN1 image sensor device driver Vladimir Zapolskiy
2025-10-23 2:53 ` [PATCH v3 1/2] dt-bindings: media: i2c: Add Samsung S5KJN1 image sensor Vladimir Zapolskiy
2025-11-04 10:20 ` Luca Weiss [this message]
2025-11-07 13:02 ` Vladimir Zapolskiy
2025-10-23 2:53 ` [PATCH v3 2/2] media: i2c: add Samsung S5KJN1 image sensor device driver Vladimir Zapolskiy
2025-11-04 10:28 ` Luca Weiss
2025-11-07 13:08 ` Vladimir Zapolskiy
2025-11-04 15:53 ` Bryan O'Donoghue
2025-11-08 11:00 ` Vladimir Zapolskiy
2025-11-11 9:25 ` Sakari Ailus
2025-11-12 2:39 ` Vladimir Zapolskiy
2025-11-12 8:40 ` Sakari Ailus
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=DDZU2RL00UD8.39GS3LN0SW7YA@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hansg@kernel.org \
--cc=hverkuil@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=vladimir.zapolskiy@linaro.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