Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp988633rwd; Wed, 31 May 2023 08:04:39 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ44ReTzy/j9IPAKUt1Mjk3KQ8pcPSXRR4oZHrS1JgtlKGreK0YsGGCh64JU93dDymp7nPEL X-Received: by 2002:a05:6a20:c702:b0:106:3b67:b5db with SMTP id hi2-20020a056a20c70200b001063b67b5dbmr4660305pzb.18.1685545478854; Wed, 31 May 2023 08:04:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685545478; cv=none; d=google.com; s=arc-20160816; b=jNowwtOlh5bVvBjBcv7IdJoK/uVxRzwPuz607BYkui+zYdDzsYbV9vNwyCWKSc/6iq VooWrithIgEoTwLxOsD7MYf8ghHaGkzCCZBRxsjx897gairlLgAFZ885mY4Voioey7yQ +cXiVlITgh6iEL5LvlQFieQ3PSsio/SibdpztssRyHys/4krDKTBPv4QcP7jhWjVcjJE UR8OQtPdmwVYCnLac5Ej2axDt2S41HrbjguzYk5LUIHjNXqxna8tYdV6D1n2rpjEJR8z voo4DgP7W2FcigG1g8IqJsDPXqGW0bnjXS/p+PJUy+icKldvkeiptOzq6oEJ5jPwHOk2 L7ZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=mwC8fnc33I/RvzYm1XgCQLmMqgI4DOojraHx1jQ/D/c=; b=jl+A0yy+ROVkLaLu+u0tYGOtSPlskTTXrmep+T+jAm/Uh0uLl/6FXzpGvt4dCS/dPy PUpp0JX3TgfaHbaNm6scIgny1m049e/dY+hR9vnHdKw9ASH5OU+ZjuGGfXCPRkQ0tho7 eErRwUSf7ZJTa/69FmWAmf3jjpGUQhsWBB7JlH7Rx2mSR6CQbD57XPS4u4EPsxxyYyvB XCdluDP1vEUHCApsgsaNQqM9dCIu3HSQeZe93KWteyefSrclRm5yMkOaJdLJ+EF7HVxC gtChS6v3mwamJqkxF6weBzaxcbb6knsM3xH0OOvadSnQ9WnvgQQyNV9IhbnwpWTTumqe GqSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b="WH6LTPe/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id t24-20020a639558000000b0053481d76f48si1144899pgn.288.2023.05.31.08.04.23; Wed, 31 May 2023 08:04:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20221208 header.b="WH6LTPe/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236541AbjEaOIA (ORCPT + 99 others); Wed, 31 May 2023 10:08:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47786 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237529AbjEaOHo (ORCPT ); Wed, 31 May 2023 10:07:44 -0400 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DCC7B19BB; Wed, 31 May 2023 07:03:16 -0700 (PDT) Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-51458187be1so9835836a12.2; Wed, 31 May 2023 07:03:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685541721; x=1688133721; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=mwC8fnc33I/RvzYm1XgCQLmMqgI4DOojraHx1jQ/D/c=; b=WH6LTPe/nEkW7HT5w0HNzuBSsKsTOhHQyI3MSAbV3OLw1+H9vjsv7CxCSu2QbV2qQi g91EYhidlo2zmXxMKxhlFK0ngiZ1XorT0pqZlUpKmtW4fj8rJrq528wlB3mT2VTo/izV R4clRt+bcKyvPDJr70ibt3tAuSLlqZfPJWtnSOuHf2jVqrVnqbiKI4hW4uiJX5WS4TvK iODiB4knjcnSyAChGbyvowuXCHANeZZO3koj7JFakZiKFWYhCV2ynOP5vOsmdebVUfyI jKriqnzbpcP1Nwq3337RhJSAa4pOYnZ/ymiAL6Fb3FC/Y4J+jCiaXPf95DttYfI65DSl pISA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685541721; x=1688133721; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mwC8fnc33I/RvzYm1XgCQLmMqgI4DOojraHx1jQ/D/c=; b=BAJwFzRdkRClgCxHn3CdyMf34bjWo5YfCTXz3v74jnvqkrJdpiY3xLswluf93tHfHy 0zC8oWikcm27vqMjO2Wb1JooT5oo5wyl7iaRR3PTxsNOHSrd9Dwc+k2y3SlIfr2dMpjI FGGPVqvM6ThlwSSu3TVwIjc2lwLMO/LzYTRVb+dINFZgC86SCELZoDTDkJrPHLVFWWfI Rav4+VyAn/QBV8EVP8xCJW0sb8W5PXPRn/qJjAO9zpvf0LEjch6fYzH4qz2lHzVtqASy RFho2Fx6acTG4lf8iBeyaTlfqlIyLsodVLe28Oa7hbG1Ita/VhQKCxJbm8kyFzdrgNwJ lAHg== X-Gm-Message-State: AC+VfDyw+e3K76YPx6u90jwSoWvh3LGbFkhhU7eimAt/Zdx8memMG4Yt rUyAC5FwUjlBwPQApyjxI1o= X-Received: by 2002:a17:906:db07:b0:96a:5bdd:7557 with SMTP id xj7-20020a170906db0700b0096a5bdd7557mr4691710ejb.70.1685541720547; Wed, 31 May 2023 07:02:00 -0700 (PDT) Received: from tom-HP-ZBook-Fury-15-G7-Mobile-Workstation (net-188-217-50-121.cust.vodafonedsl.it. [188.217.50.121]) by smtp.gmail.com with ESMTPSA id c7-20020a17090603c700b0096a68648329sm8985654eja.214.2023.05.31.07.01.59 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 31 May 2023 07:02:00 -0700 (PDT) Date: Wed, 31 May 2023 16:01:57 +0200 From: Tommaso Merciai To: Laurent Pinchart Cc: Sakari Ailus , jacopo.mondi@ideasonboard.com, martin.hecht@avnet.eu, linuxfancy@googlegroups.com, Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Hans Verkuil , Marco Felsch , Gerald Loacker , Krzysztof =?utf-8?Q?Ha=C5=82asa?= , Shawn Tu , Linus Walleij , Benjamin Mugnier , Mikhail Rudenko , Nicholas Roth , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] media: dt-bindings: alvium: add document YAML binding Message-ID: References: <20230526173955.797226-1-tomm.merciai@gmail.com> <20230526173955.797226-2-tomm.merciai@gmail.com> <20230529063907.GB25984@pendragon.ideasonboard.com> <20230529064326.GC25984@pendragon.ideasonboard.com> <20230531110600.GB27043@pendragon.ideasonboard.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230531110600.GB27043@pendragon.ideasonboard.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Laurent, On Wed, May 31, 2023 at 02:06:00PM +0300, Laurent Pinchart wrote: > Hi Tommaso, > > On Wed, May 31, 2023 at 12:20:47PM +0200, Tommaso Merciai wrote: > > On Mon, May 29, 2023 at 09:43:26AM +0300, Laurent Pinchart wrote: > > > On Mon, May 29, 2023 at 09:39:13AM +0300, Laurent Pinchart wrote: > > > > On Sun, May 28, 2023 at 09:16:05PM +0000, Sakari Ailus wrote: > > > > > On Fri, May 26, 2023 at 07:39:43PM +0200, Tommaso Merciai wrote: > > > > > > Add documentation of device tree in YAML schema for the ALVIUM > > > > > > Camera from Allied Vision Inc. > > > > > > > > > > > > References: > > > > > > - https://www.alliedvision.com/en/products/embedded-vision-solutions > > > > > > > > > > > > Signed-off-by: Tommaso Merciai > > > > > > --- > > > > > > Changes since v1: > > > > > > - Fixed build error as suggested by RHerring bot > > > > > > > > > > > > .../media/i2c/alliedvision,alvium.yaml | 115 ++++++++++++++++++ > > > > > > 1 file changed, 115 insertions(+) > > > > > > create mode 100644 Documentation/devicetree/bindings/media/i2c/alliedvision,alvium.yaml > > > > > > > > > > > > diff --git a/Documentation/devicetree/bindings/media/i2c/alliedvision,alvium.yaml b/Documentation/devicetree/bindings/media/i2c/alliedvision,alvium.yaml > > > > > > new file mode 100644 > > > > > > index 000000000000..81e9e560c99d > > > > > > --- /dev/null > > > > > > +++ b/Documentation/devicetree/bindings/media/i2c/alliedvision,alvium.yaml > > > > > > @@ -0,0 +1,115 @@ > > > > > > +# SPDX-License-Identifier: GPL-2.0 > > > > > > +%YAML 1.2 > > > > > > +--- > > > > > > +$id: http://devicetree.org/schemas/media/i2c/alliedvision,alvium.yaml# > > > > > > +$schema: http://devicetree.org/meta-schemas/core.yaml# > > > > > > + > > > > > > +title: Alliedvision Alvium Camera > > > > > > > > s/Alliedvision/Allied Vision/ > > > > > > > > > > + > > > > > > +maintainers: > > > > > > + - Tommaso Merciai > > > > > > + - Martin Hecht > > > > > > + > > > > > > +allOf: > > > > > > + - $ref: /schemas/media/video-interface-devices.yaml# > > > > > > + > > > > > > +properties: > > > > > > + compatible: > > > > > > + const: alliedvision,alvium > > > > > > > > The name is very generic. There are Alvium camera modules that have a > > > > GMSL or FPD-Link interface, and I'm pretty sure those will require a > > > > different driver. I would add module-specific compatible strings (e.g. > > > > "alliedvision,alvium-1500c", ...) here, with a generic fallback. > > > > "alliedvision,alvium" isn't good as it won't cover GMSL or FPD-Link, > > > > maybe "alliedvision,alvium-csi2" would be an option. > > > > > > Actually, "alvium-1500c" as a specific compatible string won't do. You > > > need the exact model in the compatible string, otherwise it won't be > > > possible for the driver to handle device-specific configuration (for > > > instance accessing registers of the camera sensor for fine-grained > > > configuration). I would thus recommend using "alliedvision,alvium-1500c" > > > and "alliedvision,alvium-1800c" as generic fallbacks, along compatible > > > strings that include the exact device model. > > > > Agree with alliedvision,alvium-csi2 and thanks for your suggestion. > > In my opinion we don’t need names for 1500c and > > others because the same driver can drive all the alvium models. > > Alvium is taking care of different sensor abstractions. > > > > I test with this driver with the following models: > > > > - 1800 C-1240c > > - 1800 C-040c > > - 1500 C-500 > > > > What do you think about? > > As far as I understand, the camera modules allow accessing sensors > registers from the host (through the ISP) for fine-grained > configuration. Even if that's not implemented in the driver at the > moment, I think it's an important feature to eventually support, and it > will require a way for the system to identify the camera module > precisely, to know which sensor the module uses. That's why I would like > that information to be available in DT, in the form of a compatible > string. For instance, > > compatible = "alliedvision,alvium-1500c-1240c", > "alliedvision,alvium-1500c"; > > The driver will only need DT match entries for > "alliedvision,alvium-1500c" and "alliedvision,alvium-1800c". Thanks for your feedback. Some clarification: The Alvium doesn't allow direct access on the sensor. Alvium hides the particular sensor totally. For this reason I would prefer to keep generic "alvium-csi2" name. What do you think? Thanks, Tommaso > > > > > > > + > > > > > > + reg: > > > > > > + maxItems: 1 > > > > > > + > > > > > > + clocks: > > > > > > + description: XCLK Input Clock > > > > > > + > > > > > > + clock-names: > > > > > > + const: xclk > > > > > > > > > > I'd also drop this as you have a single clock only: it's redundant. > > > > > > > > > > > + > > > > > > + powerdown-gpios: > > > > > > + maxItems: 1 > > > > > > + description: > > > > > > > + Reference to the GPIO connected to the powerdown pin, if any. > > > > > > + > > > > > > + reset-gpios: > > > > > > + maxItems: 1 > > > > > > + description: > > > > > > > + Reference to the GPIO connected to the reset pin, if any. > > > > > > > > Reading the Alvium CSI-2 Cameras User Guide, I don't see any powerdown > > > > or reset pin on the 22-pin connector. Am I missing something ? There are > > > > however two GPIOs (in addition to the I2C signals that are also > > > > documented as GPIOs), do you plan to support those ? > > > > > > > > > > + > > > > > > + streamon-delay: > > > > > > + maxItems: 1 > > > > > > + description: > > > > > > > + Delay before camera start capturing frames in us. > > > > > > > > Add "-us" to the property name to indicate the unit. > > > > > > > > This is a vendor-specific property, and should thus have a vendor > > > > prefix. > > > > > > > > A longer description is needed, from that single line I have no idea > > > > what the property does exactly. > > > > > > > > > > + > > > > > > + rotation: > > > > > > + enum: > > > > > > + - 0 > > > > > > + - 180 > > > > > > > > Why is the rotation restricted to 0 or 180 ? Someone could mount the > > > > module with 90 degrees rotation, shouldn't the DT bindings allow > > > > describing that ? > > > > > > > > You need a property for the vcc-ext-in supply. > > > > > > > > > > + > > > > > > + port: > > > > > > + description: Digital Output Port > > > > > > + $ref: /schemas/graph.yaml#/$defs/port-base > > > > > > + additionalProperties: false > > > > > > + > > > > > > + properties: > > > > > > + endpoint: > > > > > > + $ref: /schemas/media/video-interfaces.yaml# > > > > > > + unevaluatedProperties: false > > > > > > + > > > > > > + properties: > > > > > > + clock-lanes: > > > > > > + const: 0 > > > > > > > > > > The driver can know this, no need to have it in DT, i.e. please drop it. > > > > > > > > > > > + data-lanes: > > > > > > + minItems: 1 > > > > > > + maxItems: 4 > > > > > > + link-frequencies: true > > > > > > + > > > > > > + required: > > > > > > + - data-lanes > > > > > > + - link-frequencies > > > > > > + > > > > > > +required: > > > > > > + - compatible > > > > > > + - reg > > > > > > + - clocks > > > > > > + - clock-names > > > > > > + - port > > > > > > + > > > > > > +additionalProperties: false > > > > > > + > > > > > > +examples: > > > > > > + - | > > > > > > + #include > > > > > > + #include > > > > > > + > > > > > > + i2c { > > > > > > + #address-cells = <1>; > > > > > > + #size-cells = <0>; > > > > > > + > > > > > > + camera: alvium@3c { > > > > > > + compatible = "alliedvision,alvium"; > > > > > > > > The "alliedvision" prefix is missing from > > > > Documentation/devicetree/bindings/vendor-prefixes.yaml. > > > > > > > > > > + pinctrl-names = "default"; > > > > > > + pinctrl-0 = <&pinctrl_csi0_pwn>, <&pinctrl_csi0_rst>, <&pinctrl_csi_mclk>; > > > > > > > > I'd drop pinctrl, it makes the example longer without adding much value. > > > > > > > > > > + reg = <0x3c>; > > > > > > + clocks = <&clk IMX8MP_CLK_IPP_DO_CLKO2>; > > > > > > + clock-names = "xclk"; > > > > > > + assigned-clocks = <&clk IMX8MP_CLK_IPP_DO_CLKO2>; > > > > > > + assigned-clock-parents = <&clk IMX8MP_CLK_24M>; > > > > > > + assigned-clock-rates = <24000000>; > > > > > > + streamon-delay = <20>; > > > > > > + powerdown-gpios = <&gpio2 11 GPIO_ACTIVE_HIGH>; > > > > > > + reset-gpios = <&gpio1 6 GPIO_ACTIVE_LOW>; > > > > > > + status = "okay"; > > > > > > + > > > > > > + port { > > > > > > + alvium_out: endpoint { > > > > > > + remote-endpoint = <&mipi_csi_0_in>; > > > > > > + data-lanes = <1 2 3 4>; > > > > > > + link-frequencies = /bits/ 64 <681250000>; > > > > > > + clock-lanes = <0>; > > > > > > + }; > > > > > > + }; > > > > > > + }; > > > > > > + }; > > > > > > + > > > > > > +... > > -- > Regards, > > Laurent Pinchart