From: Petko Manolov <petko.manolov@konsulko.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, sakari.ailus@iki.fi
Subject: Re: [PATCH v1 1/5] DT bindings for imx492
Date: Mon, 28 Nov 2022 15:07:22 +0200 [thread overview]
Message-ID: <Y4SyiutWc2r52KVt@bender.k.g> (raw)
In-Reply-To: <Y4Q7JiJlhUL96yBW@pendragon.ideasonboard.com>
On 22-11-28 06:37:58, Laurent Pinchart wrote:
> Hi Petko,
>
> Thank you for the patch.
>
> The subject line should start with the proper prefix. Look at the git
> log in the directory to see what is customary. Furthermore,
> s/imx492/Sony IMX492/.
>
> On Fri, Nov 25, 2022 at 05:31:16PM +0200, Petko Manolov wrote:
> > Here goes the DT bindings file.
>
> This is also a peculiar commit message :-)
Short and to the point, isn't it? :)
Honestly, i'm not sure what else i should put as subject line, apart from "Sony
IMX492".
> > Signed-off-by: Petko Manolov <petko.manolov@konsulko.com>
> > ---
> > .../bindings/media/i2c/sony,imx492.yaml | 101 ++++++++++++++++++
> > 1 file changed, 101 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx492.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/media/i2c/sony,imx492.yaml b/Documentation/devicetree/bindings/media/i2c/sony,imx492.yaml
> > new file mode 100644
> > index 000000000000..f4feef17c677
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/media/i2c/sony,imx492.yaml
> > @@ -0,0 +1,101 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/media/i2c/sony,imx492.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Sony imx492 Sensor
>
> s/imx492/IMX492/. Same below. When referring to the hardware, it's
> customary to use uppercase.
OK.
> > +
> > +maintainers:
> > + - Petko Manolov <petko.manolov@konsulko.com>
> > +
> > +description:
> > +
> > + imx492 is a diagonal 23.1 mm (Type 1.4) CMOS image sensor with color or
> > + monochrome square pixel array and approximately 47.08 M effective pixels.
> > + 12-bit digital output makes it possible to output the signals with high
> > + definition for moving pictures. It is programmable through I2C interface. The
> > + I2C client address can be either 0x10 or 0x1a depending on SLASEL pin. Image
> > + data is sent through MIPI CSI-2.
> > +
> > +properties:
> > + compatible:
> > + const: sony,imx492
>
> Missing blank line.
OK.
> > + reg:
> > + description: I2C address
>
> You can drop the description.
>
> > + maxItems: 1
> > +
> > + assigned-clocks: true
> > + assigned-clock-parents: true
> > + assigned-clock-rates: true
>
> This shouldn't be needed.
OK.
> > +
> > + clocks:
> > + description: Clock frequency 6MHz, 12MHz, 18MHz and 24MHz
>
> If you know the name of the clock pin, I would include it here.
OK.
> > + maxItems: 1
> > +
> > + dovdd-supply:
> > + description: Interface power supply.
>
> I would list the voltage. Same below.
OK.
> > +
> > + avdd-supply:
> > + description: Analog power supply.
> > +
> > + dvdd-supply:
> > + description: Digital power supply.
> > +
> > + reset-gpios:
> > + description: Reference to the GPIO connected to the XCLR pin, if any.
> > + maxItems: 1
> > +
> > + port:
> > + additionalProperties: false
> > + $ref: /schemas/graph.yaml#/$defs/port-base
> > +
> > + properties:
> > + endpoint:
> > + $ref: /schemas/media/video-interfaces.yaml#
> > + unevaluatedProperties: false
> > +
> > + properties:
> > + data-lanes: true
> > + link-frequencies: true
> > +
> > + required:
> > + - data-lanes
> > + - link-frequencies
> > +
> > + required:
> > + - endpoint
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - clocks
> > + - port
> > +
> > +additionalProperties: false
> > +
> > +examples:
> > + - |
> > + i2c0 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + camera@10 {
> > + compatible = "sony,imx492";
> > + reg = <0x10>;
> > + clocks = <&imx492_clk>;
> > +
> > + assigned-clocks = <&imx492_clk>;
> > + assigned-clock-parents = <&imx492_clk_parent>;
> > + assigned-clock-rates = <24000000>;
>
> You can drop this from the example, it doesn't showcase the DT bindings for
> the IMX492.
OK.
> > +
> > + port {
> > + imx492: endpoint {
>
> s/imx492/imx492_out/
>
> > + remote-endpoint = <&cam>;
>
> s/cam/cam_in/
OK to both of the above.
> > + data-lanes = <1 2 3 4>;
> > + link-frequencies = /bits/ 64 <600000000>;
> > + };
> > + };
> > + };
> > + };
> > +...
>
> --
> Regards,
>
> Laurent Pinchart
cheers,
Petko
next prev parent reply other threads:[~2022-11-28 13:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 15:31 [PATCH v1 0/5] Adds media driver for Sony IMX492 sensor Petko Manolov
2022-11-25 15:31 ` [PATCH v1 1/5] DT bindings for imx492 Petko Manolov
2022-11-28 4:37 ` Laurent Pinchart
2022-11-28 13:07 ` Petko Manolov [this message]
2022-11-28 13:28 ` Laurent Pinchart
2022-11-25 15:31 ` [PATCH v1 2/5] media: i2c: imx492: driver's header Petko Manolov
2022-11-28 4:40 ` Laurent Pinchart
2022-11-28 13:12 ` Petko Manolov
2022-11-28 12:47 ` Kieran Bingham
2022-11-28 13:14 ` Petko Manolov
2022-11-28 13:30 ` Laurent Pinchart
2022-11-28 13:53 ` Petko Manolov
2022-11-25 15:31 ` [PATCH v1 3/5] media: i2c: imx492: driver's source Petko Manolov
2022-11-28 5:16 ` Laurent Pinchart
2022-11-28 13:42 ` Petko Manolov
2022-11-28 14:08 ` Laurent Pinchart
2022-11-28 14:18 ` Dave Stevenson
2022-11-28 12:58 ` Kieran Bingham
2022-11-28 13:48 ` Petko Manolov
2022-11-25 15:31 ` [PATCH v1 4/5] media: i2c: add imx492 config entry Petko Manolov
2022-11-25 15:31 ` [PATCH v1 5/5] media: i2c: add imx492 entry for make Petko Manolov
2022-11-25 19:48 ` kernel test robot
2022-11-28 12:45 ` [PATCH v1 0/5] Adds media driver for Sony IMX492 sensor Kieran Bingham
2022-11-28 13:11 ` Petko Manolov
2022-11-28 13:38 ` Kieran Bingham
2022-11-28 13:46 ` Laurent Pinchart
2022-11-28 14:07 ` Petko Manolov
2022-11-28 15:04 ` Kieran Bingham
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=Y4SyiutWc2r52KVt@bender.k.g \
--to=petko.manolov@konsulko.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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