From: "Rob Herring (Arm)" <robh@kernel.org>
To: Cosmin Tanislav <demonsingur@gmail.com>
Cc: linux-gpio@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
linux-staging@lists.linux.dev, "Mark Brown" <broonie@kernel.org>,
"Bjorn Andersson" <quic_bjorande@quicinc.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Benjamin Mugnier" <benjamin.mugnier@foss.st.com>,
"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
"Taniya Das" <quic_tdas@quicinc.com>,
"Zhi Mao" <zhi.mao@mediatek.com>,
"Umang Jain" <umang.jain@ideasonboard.com>,
"Nícolas F . R . A . Prado" <nfraprado@collabora.com>,
"Heiko Stuebner" <heiko@sntech.de>,
linux-media@vger.kernel.org,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Biju Das" <biju.das.jz@bp.renesas.com>,
"Laurentiu Palcu" <laurentiu.palcu@oss.nxp.com>,
"Cosmin Tanislav" <cosmin.tanislav@analog.com>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
"Ross Burton" <ross.burton@arm.com>,
"Julien Massot" <julien.massot@collabora.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Ricardo Ribalda" <ribalda@chromium.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Ihor Matushchak" <ihor.matushchak@foobox.net>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Eric Biggers" <ebiggers@google.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Tommaso Merciai" <tomm.merciai@gmail.com>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Will Deacon" <will@kernel.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Dongcheng Yan" <dongcheng.yan@intel.com>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Javier Carrasco" <javier.carrasco@wolfvision.net>
Subject: Re: [RFC PATCH 18/24] dt-bindings: media: i2c: max96712: add support for I2C MUX
Date: Sat, 08 Mar 2025 13:44:30 -0600 [thread overview]
Message-ID: <174146307027.3480579.7919845264276459579.robh@kernel.org> (raw)
In-Reply-To: <20250308183410.3013996-19-demonsingur@gmail.com>
On Sat, 08 Mar 2025 20:33:47 +0200, Cosmin Tanislav wrote:
> MAX96712 and MAX96724 have more than one GMSL2 link, and each link is
> capable of connecting to a separate serializer. If these serializers
> have the same CFG pins configuration, they will also have the same I2C
> address, causing conflicts unless the deserializer muxes the I2C
> channels. Moreover, the serializers can have the same hardware attached
> to their respective I2C bus.
>
> The MAX96712 and MAX96724 suppot I2C channel muxing via the GMSL2 link
> to facilitate communication to each of the connected serializers.
>
> Document this capability.
>
> Signed-off-by: Cosmin Tanislav <demonsingur@gmail.com>
> ---
> .../devicetree/bindings/media/i2c/maxim,max96712.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg:items: 'oneOf' conditional failed, one must be fixed:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg:items: 'anyOf' conditional failed, one must be fixed:
'min' is not one of ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'dependentRequired', 'dependentSchemas', 'deprecated', 'description', 'else', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'required', 'then', 'typeSize', 'unevaluatedProperties', 'uniqueItems']
'type' was expected
from schema $id: http://devicetree.org/meta-schemas/keywords.yaml#
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg:items: 'anyOf' conditional failed, one must be fixed:
'max' is not one of ['$ref', 'additionalItems', 'additionalProperties', 'allOf', 'anyOf', 'const', 'contains', 'default', 'dependencies', 'dependentRequired', 'dependentSchemas', 'deprecated', 'description', 'else', 'enum', 'exclusiveMaximum', 'exclusiveMinimum', 'items', 'if', 'minItems', 'minimum', 'maxItems', 'maximum', 'multipleOf', 'not', 'oneOf', 'pattern', 'patternProperties', 'properties', 'required', 'then', 'typeSize', 'unevaluatedProperties', 'uniqueItems']
'type' was expected
from schema $id: http://devicetree.org/meta-schemas/keywords.yaml#
{'min': 0, 'max': 3} is not of type 'array'
from schema $id: http://devicetree.org/meta-schemas/keywords.yaml#
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg: 'anyOf' conditional failed, one must be fixed:
'maxItems' is a required property
hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
'items' is not one of ['maxItems', 'description', 'deprecated']
hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
'items' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg:items: 'oneOf' conditional failed, one must be fixed:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: properties:i2c-mux:patternProperties:^i2c@[0-3]$:properties:reg:items: 'anyOf' conditional failed, one must be fixed:
'maxItems' is a required property
hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
'min' is not one of ['maxItems', 'description', 'deprecated']
hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
'max' is not one of ['maxItems', 'description', 'deprecated']
hint: Only "maxItems" is required for a single entry if there are no constraints defined for the values.
Additional properties are not allowed ('max', 'min' were unexpected)
hint: Arrays must be described with a combination of minItems/maxItems/items
'min' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
hint: "items" can be a list defining each entry or a schema applying to all items. A list has an implicit size. A schema requires minItems/maxItems to define the size.
'max' is not one of ['description', 'deprecated', 'const', 'enum', 'minimum', 'maximum', 'multipleOf', 'default', '$ref', 'oneOf']
hint: "items" can be a list defining each entry or a schema applying to all items. A list has an implicit size. A schema requires minItems/maxItems to define the size.
hint: cell array properties must define how many entries and what the entries are when there is more than one entry.
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
{'min': 0, 'max': 3} is not of type 'array'
hint: "items" can be a list defining each entry or a schema applying to all items. A list has an implicit size. A schema requires minItems/maxItems to define the size.
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
hint: cell array properties must define how many entries and what the entries are when there is more than one entry.
from schema $id: http://devicetree.org/meta-schemas/core.yaml#
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: i2c-mux: Missing additionalProperties/unevaluatedProperties constraint
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/media/i2c/maxim,max96712.yaml: ^i2c@[0-3]$: Missing additionalProperties/unevaluatedProperties constraint
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250308183410.3013996-19-demonsingur@gmail.com
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.
next prev parent reply other threads:[~2025-03-08 19:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 18:33 [RFC PATCH 00/24] media: i2c: add Maxim GMSL2/3 serializer and deserializer drivers Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 01/24] dt-bindings: media: i2c: max96717: add myself as maintainer Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 02/24] dt-bindings: media: i2c: max96717: reflow text Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 03/24] dt-bindings: media: i2c: max96717: add support for I2C ATR Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 04/24] dt-bindings: media: i2c: max96717: add support for pinctrl/pinconf Cosmin Tanislav
2025-03-08 20:44 ` Rob Herring (Arm)
2025-03-08 18:33 ` [RFC PATCH 05/24] dt-bindings: media: i2c: max96717: add support for MAX9295A Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 06/24] dt-bindings: media: i2c: max96717: add support for MAX96793 Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 07/24] dt-bindings: media: i2c: max96714: add myself as maintainer Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 08/24] dt-bindings: media: i2c: max96714: reflow text Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 09/24] dt-bindings: media: i2c: max96714: make i2c-gate conditional on compatible Cosmin Tanislav
2025-03-08 20:44 ` Rob Herring (Arm)
2025-03-10 12:32 ` Rob Herring
2025-03-10 12:52 ` Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 10/24] dt-bindings: media: i2c: max96714: make ports " Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 11/24] dt-bindings: media: i2c: max96714: make supply " Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 12/24] dt-bindings: media: i2c: max96714: add support for MAX9296A Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 13/24] dt-bindings: media: i2c: max96714: add support for MAX96716A Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 14/24] dt-bindings: media: i2c: max96714: add support for MAX96792A Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 15/24] dt-bindings: media: i2c: max96712: add myself as maintainer Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 16/24] dt-bindings: media: i2c: max96712: use pattern properties for input ports Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 17/24] dt-bindings: media: i2c: max96712: increase number of output ports Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 18/24] dt-bindings: media: i2c: max96712: add support for I2C MUX Cosmin Tanislav
2025-03-08 19:44 ` Rob Herring (Arm) [this message]
2025-03-08 18:33 ` [RFC PATCH 19/24] dt-bindings: media: i2c: max96712: add support for POC supplies Cosmin Tanislav
2025-03-08 19:59 ` Rob Herring (Arm)
2025-03-08 18:33 ` [RFC PATCH 20/24] media: i2c: add Maxim GMSL2/3 serializer and deserializer drivers Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 21/24] arm64: defconfig: disable deprecated MAX96712 driver Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 22/24] staging: media: remove " Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 23/24] media: i2c: remove MAX96717 driver Cosmin Tanislav
2025-03-08 18:33 ` [RFC PATCH 24/24] media: i2c: remove MAX96714 driver Cosmin Tanislav
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=174146307027.3480579.7919845264276459579.robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=cosmin.tanislav@analog.com \
--cc=dan.carpenter@linaro.org \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dongcheng.yan@intel.com \
--cc=ebiggers@google.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=ihor.matushchak@foobox.net \
--cc=javier.carrasco@wolfvision.net \
--cc=julien.massot@collabora.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=nfraprado@collabora.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=quic_bjorande@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=ribalda@chromium.org \
--cc=ross.burton@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tomm.merciai@gmail.com \
--cc=umang.jain@ideasonboard.com \
--cc=will@kernel.org \
--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