[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <176096011475.23064.13799548826512417145.robh@kernel.org>
Date: Mon, 20 Oct 2025 06:35:18 -0500
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Ryan Chen <ryan_chen@...eedtech.com>
Cc: andi.shyti@...nel.org, linux-i2c@...r.kernel.org,
andriy.shevchenko@...ux.intel.com, naresh.solanki@...ements.com,
p.zabel@...gutronix.de, linux-arm-kernel@...ts.infradead.org,
openbmc@...ts.ozlabs.org, conor+dt@...nel.org,
linux-aspeed@...ts.ozlabs.org, joel@....id.au, krzk+dt@...nel.org,
andrew@...econstruct.com.au, linux-kernel@...r.kernel.org,
benh@...nel.crashing.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v19 1/4] dt-bindings: i2c: Split AST2600 binding into a
new YAML
On Mon, 20 Oct 2025 09:31:57 +0800, Ryan Chen wrote:
> The AST2600 I2C controller is a new hardware design compared to the
> I2C controllers in previous ASPEED SoCs (e.g., AST2400, AST2500).
>
> It introduces new features such as:
> - A redesigned register layout
> - Separation between controller and target mode registers
> - Transfer mode selection (byte, buffer, DMA)
> - Support for a shared global register block for configuration
>
> Due to these fundamental differences, maintaining a separate
> devicetree binding file for AST2600 helps to clearly distinguish
> the hardware capabilities and configuration options from the older
> controllers.
>
> Signed-off-by: Ryan Chen <ryan_chen@...eedtech.com>
> ---
> .../devicetree/bindings/i2c/aspeed,i2c.yaml | 3 +-
> .../devicetree/bindings/i2c/ast2600-i2c.yaml | 67 +++++++++++++++++++
> 2 files changed, 68 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml
>
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/i2c/ast2600-i2c.yaml: warning: ignoring duplicate '$id' value 'http://devicetree.org/schemas/i2c/aspeed,i2c.yaml#'
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml: properties:reg: {'minItems': 1, 'maxItems': 2, 'items': [{'description': 'address offset and range of bus'}, {'description': 'address offset and range of bus buffer'}]} should not be valid under {'required': ['maxItems']}
hint: "maxItems" is not needed with an "items" list
from schema $id: http://devicetree.org/meta-schemas/items.yaml#
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename
$id: http://devicetree.org/schemas/i2c/aspeed,i2c.yaml
file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml
Documentation/devicetree/bindings/i2c/ast2600-i2c.example.dtb: /example-0/i2c@40: failed to match any schema with compatible: ['aspeed,ast2600-i2c-bus']
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20251020013200.1858325-2-ryan_chen@aspeedtech.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.
Powered by blists - more mailing lists