Message ID | 20230206-ov2685-dtschema-v1-1-9e4da3474c10@z3ntu.xyz |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:eb09:0:0:0:0:0 with SMTP id s9csp2448698wrn; Mon, 6 Feb 2023 12:36:52 -0800 (PST) X-Google-Smtp-Source: AK7set95tXJP7S4E3gJ9LuPFwTjros6ZCiHyV5wSKEBx4CL/luPCpL0eiQU6b8/pCb9Hxf4UhnJF X-Received: by 2002:a50:8e56:0:b0:4aa:a35c:b715 with SMTP id 22-20020a508e56000000b004aaa35cb715mr1011845edx.22.1675715812261; Mon, 06 Feb 2023 12:36:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1675715812; cv=none; d=google.com; s=arc-20160816; b=fBidQ8qs5dNwX1+X5NIpyDf78jCcXUmqSsDhuj9gzDMGiL04gA2NB2QEq4umM5dCeW VWFOAG7psN//gdh6H0eZ6sSPXWcbvKE4YECa/jGQYfr2qrJfWpOSZ0QVc7mtC48ixDMs lbRm33idcbpK+hZU+EPriz9kEIWO4KYQccsve4zX2Cskwf5Jcz6zfa5wIG4khjp21Buq rRpXVvjOqipfnvGealeXvFqZKcSgZmQ/DN0V9sD9erKz1aL49hc76z2Fy8g0+b5auzLy tvPST/QnhETO20ZBAXKn9/Tof48avPt3ia+0ULQq/RptUS4iUUZNm/PwDI7obSCF1OoU 9N/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:message-id:content-transfer-encoding :mime-version:subject:date:from:dkim-signature; bh=+eVnqoI9A7ElpOcXKpvwQVvmxYIo9RsH7PxotG6DHt0=; b=DDD+6zzQj5jF28tS6mRL4uFUzPdECaW9nCrxQ/BPOV/CvwkOaFVDRT/OrpABHPYE1H 6tIZz3PuTecrfruUxJpGFNWnAq3HvGjrSySkEz1NVsXErPgtFKX4aToUQZVRGzOBTXnk L7RcaAh0fHOYTU4k1M5SK89aAQ41G8e+vTmbO0t5abzB9h1mObK0pUwwyFpUUdEO8P5H q+tNY3311lc79fLfeLiFjZP5VGqsiyab0bnN0hEGG5GwLKSRhgD1Jy5v/JH8VN3cUQzz HEDeCyER32OpUxw653aef12uPzgEfkvCQP3a17QE3Yc9sUrE88yIm2FEVJ6C68k6enxO KAyg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@z3ntu.xyz header.s=z3ntu header.b=x7Dk5i5T; 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=NONE dis=NONE) header.from=z3ntu.xyz Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z14-20020a05640235ce00b004a2188582a7si15064723edc.466.2023.02.06.12.36.28; Mon, 06 Feb 2023 12:36:52 -0800 (PST) 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=@z3ntu.xyz header.s=z3ntu header.b=x7Dk5i5T; 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=NONE dis=NONE) header.from=z3ntu.xyz Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230223AbjBFUXf (ORCPT <rfc822;kmanaouilinux@gmail.com> + 99 others); Mon, 6 Feb 2023 15:23:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60782 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230149AbjBFUXd (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 6 Feb 2023 15:23:33 -0500 Received: from mail.z3ntu.xyz (mail.z3ntu.xyz [128.199.32.197]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9534917CFF; Mon, 6 Feb 2023 12:23:32 -0800 (PST) Received: from [192.168.178.23] (unknown [62.108.10.64]) by mail.z3ntu.xyz (Postfix) with ESMTPSA id E4978CD5E5; Mon, 6 Feb 2023 20:23:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=z3ntu.xyz; s=z3ntu; t=1675715011; bh=y9+LNvytHx45ZXahQcbCuN9gP03/f6UYg1OC+YD/nWo=; h=From:Date:Subject:To:Cc; b=x7Dk5i5TGfQhCYi0Anj3N9ZZnbKcJTlnRVS8XP3e9POLw6cxBDYVrqIwiA2CX3xPZ qLe+TT98rml8EkfBx1fWnrO7S+ujoVM/EqREm5VJw5kJEAZmiRy4CBQ/6D/7GaLeC5 ezzGxA2tZ2nG3AEqPxft0oNSP9iaBSjT3cO3Ii9E= From: Luca Weiss <luca@z3ntu.xyz> Date: Mon, 06 Feb 2023 21:23:16 +0100 Subject: [PATCH] media: dt-bindings: ov2685: convert to dtschema MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <20230206-ov2685-dtschema-v1-1-9e4da3474c10@z3ntu.xyz> X-B4-Tracking: v=1; b=H4sIALNh4WMC/x2NQQ6CMBAAv0L27JJSSkW/Yjws29X20CKtIRrC3 y0eJ5nJbFAkBylwbTbIsoYS5lShOzXAntJTMLjKoJXulVYW51XbcUD3LuwlErqeDWl2huwAtZq oCE6ZEvujW3iOGEscL2eDtu3aLzJFyaQP+ZXlET7//e2+7z/UqpIXjgAAAA== To: ~postmarketos/upstreaming@lists.sr.ht, phone-devel@vger.kernel.org, Mauro Carvalho Chehab <mchehab@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Shunqian Zheng <zhengsq@rock-chips.com> Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Luca Weiss <luca@z3ntu.xyz> X-Mailer: b4 0.12.1 X-Developer-Signature: v=1; a=openpgp-sha256; l=5267; i=luca@z3ntu.xyz; h=from:subject:message-id; bh=y9+LNvytHx45ZXahQcbCuN9gP03/f6UYg1OC+YD/nWo=; b=owEBbQKS/ZANAwAIAXLYQ7idTddWAcsmYgBj4WHBOThzVFER8dVB+XZ5hbF84+Q+UR9522PcO ky41GWtPkOJAjMEAAEIAB0WIQQ5utIvCCzakboVj/py2EO4nU3XVgUCY+FhwQAKCRBy2EO4nU3X VpN7EADD5U6Wmq1auJAFvNa6mmjmc4YyNQOsfExSNwteHmVjipfHIEUyAkAPJ98tEvpARCqgXxU T5t3vWu/SmumqrXH1lduv27ZQsUXmwJyB/1y1IdxQaCU1lzJ7xv3T9j9s7k71+R2g4WkojA+aGC GOBzzo4M5Yl9JlH8rXBqzVX/f5G04c0+5sHcXiS4K3N3VykyZamvKcQhM7kTN/Lo0bcDLRJ6KfE vGBvdWgYnRnVq6HV2Cc5AyS890rfXT8aEwsU3IXNEgrARhr53t2KcGEz8RarQxWkEK6RlClkqfG YnFxegNumh0oab6mCTDau/Bd+HmtTz82TsQUoL8V3LTj4GbS03b020wbZKWHZiODSpTXwPZEQ0m QwxhPhxxLLNmatbtQWS4ut3MTsdMfHru9QCQ7cYMQid1cbkFbNgDrE8ooTK8oFAk5AnKl1rPp92 vdZwjf2i/8cB+7MtN4F5KE/E3uxzOapo1LNG3tt7/IlRe81TUNY56TPsyDBch2r3Ap9ZiHNErGT lTq2GxHxRU8Awbh45HI6ktBKs7y4BA7z6YsWyGnTKvwi/2UdTePOYS4C/528CkoREdqQ8vZTQNG lZugR/bHIHBH0aKfZo9/SP7IimGP0i3f5AUg9E6A9x87THf+Mz25hs9WSFxKHe0GuRbp+AYlfBw AbXSiVZsa+QBH1Q== X-Developer-Key: i=luca@z3ntu.xyz; a=openpgp; fpr=BD04DA24C971B8D587B2B8D7FAF69CF6CD2D02CD X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1757115383212657558?= X-GMAIL-MSGID: =?utf-8?q?1757115383212657558?= |
Series |
media: dt-bindings: ov2685: convert to dtschema
|
|
Commit Message
Luca Weiss
Feb. 6, 2023, 8:23 p.m. UTC
Convert the text-based dt-bindings to yaml.
Changes from original txt:
* Take wording for various properties from other yaml bindings, this
removes e.g. volt amount from schema since it isn't really relevant
and the datasheet is a better source.
* Don't make reset-gpios a required property since it can be tied to
DOVDD instead.
Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
---
.../devicetree/bindings/media/i2c/ov2685.txt | 41 ---------
.../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 +++++++++++++++++++++
MAINTAINERS | 1 +
3 files changed, 102 insertions(+), 41 deletions(-)
---
base-commit: 129af770823407ee115a56c69a04b440fd2fbe61
change-id: 20230206-ov2685-dtschema-d3c4a2cd4a65
Best regards,
Comments
On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: > Convert the text-based dt-bindings to yaml. > > Changes from original txt: > * Take wording for various properties from other yaml bindings, this > removes e.g. volt amount from schema since it isn't really relevant > and the datasheet is a better source. > * Don't make reset-gpios a required property since it can be tied to > DOVDD instead. > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz> > --- > .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- > .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 +++++++++++++++++++++ > MAINTAINERS | 1 + > 3 files changed, 102 insertions(+), 41 deletions(-) > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13): yamllint warnings/errors: dtschema/dtc warnings/errors: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required property From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required property From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required property From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required property From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required property From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230206-ov2685-dtschema-v1-1-9e4da3474c10@z3ntu.xyz The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
+CC Helen Koike On Montag, 6. Februar 2023 22:50:08 CET Rob Herring wrote: > On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: > > Convert the text-based dt-bindings to yaml. > > > > Changes from original txt: > > * Take wording for various properties from other yaml bindings, this > > > > removes e.g. volt amount from schema since it isn't really relevant > > and the datasheet is a better source. > > > > * Don't make reset-gpios a required property since it can be tied to > > > > DOVDD instead. > > > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz> > > --- > > > > .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- > > .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 > > +++++++++++++++++++++ MAINTAINERS > > | 1 + > > 3 files changed, 102 insertions(+), 41 deletions(-) > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/medi > a/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required property From > schema: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required > property From schema: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required > property From schema: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required > property From schema: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required > property From schema: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > ia/i2c/ovti,ov2685.yaml Looks like rockchip-isp1.yaml uses very incomplete sensor examples in their binding example, which sort of makes sense since those bindings are showing the rockchip isp bindings and contain the bare minimum to show how a sensor is connected in dt. Not sure how to solve this - ov2685 is also one of three sensors that are used very abbreviated there. Regards Luca > > doc reference errors (make refcheckdocs): > > See > https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20230206-ov2 > 685-dtschema-v1-1-9e4da3474c10@z3ntu.xyz > > The base for the series is generally the latest rc1. A different dependency > should be noted in *this* patch. > > If you already ran 'make dt_binding_check' and didn't see the above > error(s), then make sure 'yamllint' is installed and dt-schema is up to > date: > > pip3 install dtschema --upgrade > > Please check and re-submit after running the above command yourself. Note > that DT_SCHEMA_FILES can be set to your schema file to speed up checking > your schema. However, it must be unset to test all examples with your > schema.
Hi Luca, On Thu, Feb 09, 2023 at 05:46:48PM +0100, Luca Weiss wrote: > +CC Helen Koike > > On Montag, 6. Februar 2023 22:50:08 CET Rob Herring wrote: > > On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: > > > Convert the text-based dt-bindings to yaml. > > > > > > Changes from original txt: > > > * Take wording for various properties from other yaml bindings, this > > > > > > removes e.g. volt amount from schema since it isn't really relevant > > > and the datasheet is a better source. > > > > > > * Don't make reset-gpios a required property since it can be tied to > > > > > > DOVDD instead. > > > > > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz> > > > --- > > > > > > .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- > > > .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 > > > +++++++++++++++++++++ MAINTAINERS > > > | 1 + > > > 3 files changed, 102 insertions(+), 41 deletions(-) > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > > > yamllint warnings/errors: > > > > dtschema/dtc warnings/errors: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/medi > > a/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required property From > > schema: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/i2c/ovti,ov2685.yaml > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required > > property From schema: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/i2c/ovti,ov2685.yaml > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required > > property From schema: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/i2c/ovti,ov2685.yaml > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required > > property From schema: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/i2c/ovti,ov2685.yaml > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required > > property From schema: > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/med > > ia/i2c/ovti,ov2685.yaml > > Looks like rockchip-isp1.yaml uses very incomplete sensor examples in their > binding example, which sort of makes sense since those bindings are showing > the rockchip isp bindings and contain the bare minimum to show how a sensor is > connected in dt. > > Not sure how to solve this - ov2685 is also one of three sensors that are used > very abbreviated there. Could these regulators be simply made optional?
On Dienstag, 14. März 2023 13:00:52 CET Sakari Ailus wrote: > Hi Luca, > > On Thu, Feb 09, 2023 at 05:46:48PM +0100, Luca Weiss wrote: > > +CC Helen Koike > > > > On Montag, 6. Februar 2023 22:50:08 CET Rob Herring wrote: > > > On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: > > > > Convert the text-based dt-bindings to yaml. > > > > > > > > Changes from original txt: > > > > * Take wording for various properties from other yaml bindings, this > > > > > > > > removes e.g. volt amount from schema since it isn't really relevant > > > > and the datasheet is a better source. > > > > > > > > * Don't make reset-gpios a required property since it can be tied to > > > > > > > > DOVDD instead. > > > > > > > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz> > > > > --- > > > > > > > > .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- > > > > .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 > > > > +++++++++++++++++++++ MAINTAINERS > > > > > > > > | 1 + > > > > > > > > 3 files changed, 102 insertions(+), 41 deletions(-) > > > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > > > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > > > > > yamllint warnings/errors: > > > > > > dtschema/dtc warnings/errors: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > medi a/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required > > > property From schema: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/i2c/ovti,ov2685.yaml > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required > > > property From schema: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/i2c/ovti,ov2685.yaml > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required > > > property From schema: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/i2c/ovti,ov2685.yaml > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required > > > property From schema: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/i2c/ovti,ov2685.yaml > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required > > > property From schema: > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > med > > > ia/i2c/ovti,ov2685.yaml > > > > Looks like rockchip-isp1.yaml uses very incomplete sensor examples in > > their > > binding example, which sort of makes sense since those bindings are > > showing > > the rockchip isp bindings and contain the bare minimum to show how a > > sensor is connected in dt. > > > > Not sure how to solve this - ov2685 is also one of three sensors that are > > used very abbreviated there. > > Could these regulators be simply made optional? Sure, from driver side it would just get dummy regulators instead. Still the clocks are also missing in this rockchip example. Any suggestion what to do about those? Honestly I don't want to spend too much time on some ISP docs that I don't really care about, would be nice if the maintainers of that could do that... Regards Luca
On 14/03/2023 19:33, Luca Weiss wrote: >>>> ia/i2c/ovti,ov2685.yaml >>> >>> Looks like rockchip-isp1.yaml uses very incomplete sensor examples in >>> their >>> binding example, which sort of makes sense since those bindings are >>> showing >>> the rockchip isp bindings and contain the bare minimum to show how a >>> sensor is connected in dt. >>> >>> Not sure how to solve this - ov2685 is also one of three sensors that are >>> used very abbreviated there. >> >> Could these regulators be simply made optional? > > Sure, from driver side it would just get dummy regulators instead. > > Still the clocks are also missing in this rockchip example. Any suggestion > what to do about those? > > Honestly I don't want to spend too much time on some ISP docs that I don't > really care about, would be nice if the maintainers of that could do that... In perfect world, the bindings describe the hardware and if hardware requires supply or clock to operate, then it should be required in the binding. If some other DTS do not validate - their problem... In practice, we make tradeoffs. But is it the case here? The binding was always requiring supplies and clocks, so there is no reason to make supplies optional. Unless you know the device and they are really optional. Best regards, Krzysztof
On 06/02/2023 22:50, Rob Herring wrote: > > On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: >> Convert the text-based dt-bindings to yaml. >> >> Changes from original txt: >> * Take wording for various properties from other yaml bindings, this >> removes e.g. volt amount from schema since it isn't really relevant >> and the datasheet is a better source. >> * Don't make reset-gpios a required property since it can be tied to >> DOVDD instead. >> >> Signed-off-by: Luca Weiss <luca@z3ntu.xyz> >> --- >> .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- >> .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 +++++++++++++++++++++ >> MAINTAINERS | 1 + >> 3 files changed, 102 insertions(+), 41 deletions(-) >> > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required property > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required property > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required property > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required property > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required property > From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml These are errors from the bindings, so they must be fixed. If you do not want to fix the rockchip bindings, just drop or replace the sensor in them. Best regards, Krzysztof
On 14/03/2023 19:37, Krzysztof Kozlowski wrote: > On 06/02/2023 22:50, Rob Herring wrote: >> >> On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: >>> Convert the text-based dt-bindings to yaml. >>> >>> Changes from original txt: >>> * Take wording for various properties from other yaml bindings, this >>> removes e.g. volt amount from schema since it isn't really relevant >>> and the datasheet is a better source. >>> * Don't make reset-gpios a required property since it can be tied to >>> DOVDD instead. >>> >>> Signed-off-by: Luca Weiss <luca@z3ntu.xyz> >>> --- >>> .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- >>> .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 +++++++++++++++++++++ >>> MAINTAINERS | 1 + >>> 3 files changed, 102 insertions(+), 41 deletions(-) >>> >> >> My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' >> on your patch (DT_CHECKER_FLAGS is new in v5.13): >> >> yamllint warnings/errors: >> >> dtschema/dtc warnings/errors: >> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required property >> From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml >> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required property >> From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml >> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required property >> From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml >> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required property >> From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml >> /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required property >> From schema: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml > > These are errors from the bindings, so they must be fixed. If you do not > want to fix the rockchip bindings, just drop or replace the sensor in them. Or one more: add some fake stubs. They do not matter anyway... Best regards, Krzysztof
On Tue, Mar 14, 2023 at 07:33:06PM +0100, Luca Weiss wrote: > On Dienstag, 14. März 2023 13:00:52 CET Sakari Ailus wrote: > > Hi Luca, > > > > On Thu, Feb 09, 2023 at 05:46:48PM +0100, Luca Weiss wrote: > > > +CC Helen Koike > > > > > > On Montag, 6. Februar 2023 22:50:08 CET Rob Herring wrote: > > > > On Mon, 06 Feb 2023 21:23:16 +0100, Luca Weiss wrote: > > > > > Convert the text-based dt-bindings to yaml. > > > > > > > > > > Changes from original txt: > > > > > * Take wording for various properties from other yaml bindings, this > > > > > > > > > > removes e.g. volt amount from schema since it isn't really relevant > > > > > and the datasheet is a better source. > > > > > > > > > > * Don't make reset-gpios a required property since it can be tied to > > > > > > > > > > DOVDD instead. > > > > > > > > > > Signed-off-by: Luca Weiss <luca@z3ntu.xyz> > > > > > --- > > > > > > > > > > .../devicetree/bindings/media/i2c/ov2685.txt | 41 --------- > > > > > .../devicetree/bindings/media/i2c/ovti,ov2685.yaml | 101 > > > > > +++++++++++++++++++++ MAINTAINERS > > > > > > > > > > | 1 + > > > > > > > > > > 3 files changed, 102 insertions(+), 41 deletions(-) > > > > > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > > > > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > > > > > > > yamllint warnings/errors: > > > > > > > > dtschema/dtc warnings/errors: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > medi a/rockchip-isp1.example.dtb: camera@3c: 'clocks' is a required > > > > property From schema: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/i2c/ovti,ov2685.yaml > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/rockchip-isp1.example.dtb: camera@3c: 'clock-names' is a required > > > > property From schema: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/i2c/ovti,ov2685.yaml > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/rockchip-isp1.example.dtb: camera@3c: 'dvdd-supply' is a required > > > > property From schema: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/i2c/ovti,ov2685.yaml > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/rockchip-isp1.example.dtb: camera@3c: 'avdd-supply' is a required > > > > property From schema: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/i2c/ovti,ov2685.yaml > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/rockchip-isp1.example.dtb: camera@3c: 'dovdd-supply' is a required > > > > property From schema: > > > > /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/ > > > > med > > > > ia/i2c/ovti,ov2685.yaml > > > > > > Looks like rockchip-isp1.yaml uses very incomplete sensor examples in > > > their > > > binding example, which sort of makes sense since those bindings are > > > showing > > > the rockchip isp bindings and contain the bare minimum to show how a > > > sensor is connected in dt. > > > > > > Not sure how to solve this - ov2685 is also one of three sensors that are > > > used very abbreviated there. > > > > Could these regulators be simply made optional? > > Sure, from driver side it would just get dummy regulators instead. > > Still the clocks are also missing in this rockchip example. Any suggestion > what to do about those? > > Honestly I don't want to spend too much time on some ISP docs that I don't > really care about, would be nice if the maintainers of that could do that... Ah, I think I missed this was about examples only, not actual DT source. I guess you could just make up some clocks in that case? :-)
diff --git a/Documentation/devicetree/bindings/media/i2c/ov2685.txt b/Documentation/devicetree/bindings/media/i2c/ov2685.txt deleted file mode 100644 index 625c4a8c0d53..000000000000 --- a/Documentation/devicetree/bindings/media/i2c/ov2685.txt +++ /dev/null @@ -1,41 +0,0 @@ -* Omnivision OV2685 MIPI CSI-2 sensor - -Required Properties: -- compatible: shall be "ovti,ov2685" -- clocks: reference to the xvclk input clock -- clock-names: shall be "xvclk" -- avdd-supply: Analog voltage supply, 2.8 volts -- dovdd-supply: Digital I/O voltage supply, 1.8 volts -- dvdd-supply: Digital core voltage supply, 1.8 volts -- reset-gpios: Low active reset gpio - -The device node shall contain one 'port' child node with an -'endpoint' subnode for its digital output video port, -in accordance with the video interface bindings defined in -Documentation/devicetree/bindings/media/video-interfaces.txt. -The endpoint optional property 'data-lanes' shall be "<1>". - -Example: -&i2c7 { - ov2685: camera-sensor@3c { - compatible = "ovti,ov2685"; - reg = <0x3c>; - pinctrl-names = "default"; - pinctrl-0 = <&clk_24m_cam>; - - clocks = <&cru SCLK_TESTCLKOUT1>; - clock-names = "xvclk"; - - avdd-supply = <&pp2800_cam>; - dovdd-supply = <&pp1800>; - dvdd-supply = <&pp1800>; - reset-gpios = <&gpio2 3 GPIO_ACTIVE_LOW>; - - port { - ucam_out: endpoint { - remote-endpoint = <&mipi_in_ucam>; - data-lanes = <1>; - }; - }; - }; -}; diff --git a/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml b/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml new file mode 100644 index 000000000000..c53bee4a1025 --- /dev/null +++ b/Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml @@ -0,0 +1,101 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/media/i2c/ovti,ov2685.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: OmniVision OV2685 Image Sensor + +maintainers: + - Shunqian Zheng <zhengsq@rock-chips.com> + +properties: + compatible: + const: ovti,ov2685 + + reg: + maxItems: 1 + + clocks: + items: + - description: XVCLK clock + + clock-names: + items: + - const: xvclk + + dvdd-supply: + description: Digital Domain Power Supply + + avdd-supply: + description: Analog Domain Power Supply + + dovdd-supply: + description: I/O Domain Power Supply + + reset-gpios: + maxItems: 1 + description: Reset Pin GPIO Control (active low) + + port: + description: MIPI CSI-2 transmitter port + $ref: /schemas/graph.yaml#/$defs/port-base + additionalProperties: false + + properties: + endpoint: + $ref: /schemas/media/video-interfaces.yaml# + unevaluatedProperties: false + + properties: + data-lanes: + maxItems: 1 + + required: + - data-lanes + +required: + - compatible + - reg + - clocks + - clock-names + - dvdd-supply + - avdd-supply + - dovdd-supply + - port + +additionalProperties: false + +examples: + - | + #include <dt-bindings/clock/rk3399-cru.h> + #include <dt-bindings/gpio/gpio.h> + + i2c7 { + #address-cells = <1>; + #size-cells = <0>; + + ov2685: camera-sensor@3c { + compatible = "ovti,ov2685"; + reg = <0x3c>; + pinctrl-names = "default"; + pinctrl-0 = <&clk_24m_cam>; + + clocks = <&cru SCLK_TESTCLKOUT1>; + clock-names = "xvclk"; + + avdd-supply = <&pp2800_cam>; + dovdd-supply = <&pp1800>; + dvdd-supply = <&pp1800>; + reset-gpios = <&gpio2 3 GPIO_ACTIVE_LOW>; + + port { + ucam_out: endpoint { + remote-endpoint = <&mipi_in_ucam>; + data-lanes = <1>; + }; + }; + }; + }; + +... diff --git a/MAINTAINERS b/MAINTAINERS index f76ca2808474..e660a4e1f74c 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -15327,6 +15327,7 @@ M: Shunqian Zheng <zhengsq@rock-chips.com> L: linux-media@vger.kernel.org S: Maintained T: git git://linuxtv.org/media_tree.git +F: Documentation/devicetree/bindings/media/i2c/ovti,ov2685.yaml F: drivers/media/i2c/ov2685.c OMNIVISION OV2740 SENSOR DRIVER