From: Krzysztof Kozlowski <krzk@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>,
bmc-sw@aspeedtech.com, benh@kernel.crashing.org, joel@jms.id.au,
andi.shyti@kernel.org, jk@codeconstruct.com.au, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
andrew@codeconstruct.com.au, p.zabel@pengutronix.de,
andriy.shevchenko@linux.intel.com, naresh.solanki@9elements.com,
linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v21 1/4] dt-bindings: i2c: Split AST2600 binding into a new YAML
Date: Mon, 27 Oct 2025 20:11:32 +0100 [thread overview]
Message-ID: <59d4d107-4f35-4906-8524-f45b9b85f0ff@kernel.org> (raw)
In-Reply-To: <20251027061240.3427875-2-ryan_chen@aspeedtech.com>
On 27/10/2025 07:12, Ryan Chen wrote:
> The AST2600 I2C controller introduces a completely new register
> map and Separate control/target register sets, unlike the mixed
> layout used in AST2400/AST2500.
>
> In addition, at new AST2600 configuration registers and transfer
> modes require new DT properties, which are incompatible with
> existing bindings. Therefore, this patch creates a dedicated
> binding file for AST2600 to properly describe these new
> hardware capabilities.
>
> A subsequent change will modify this new binding to properly
> describe the AST2600 hardware.
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> .../devicetree/bindings/i2c/aspeed,i2c.yaml | 3 +-
> .../devicetree/bindings/i2c/ast2600-i2c.yaml | 66 +++++++++++++++++++
> 2 files changed, 67 insertions(+), 2 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml
>
> diff --git a/Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml b/Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml
> index 5b9bd2feda3b..d4e4f412feba 100644
> --- a/Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml
> +++ b/Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml
> @@ -4,7 +4,7 @@
> $id: http://devicetree.org/schemas/i2c/aspeed,i2c.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> -title: ASPEED I2C on the AST24XX, AST25XX, and AST26XX SoCs
> +title: ASPEED I2C on the AST24XX, AST25XX SoCs
>
> maintainers:
> - Rayn Chen <rayn_chen@aspeedtech.com>
> @@ -17,7 +17,6 @@ properties:
> enum:
> - aspeed,ast2400-i2c-bus
> - aspeed,ast2500-i2c-bus
> - - aspeed,ast2600-i2c-bus
>
> reg:
> minItems: 1
> diff --git a/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml b/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml
> new file mode 100644
> index 000000000000..6ddcec5decdc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/i2c/ast2600-i2c.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/i2c/ast2600-i2c.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ASPEED I2C on the AST26XX SoCs
> +
> +maintainers:
> + - Ryan Chen <ryan_chen@aspeedtech.com>
> +
> +allOf:
> + - $ref: /schemas/i2c/i2c-controller.yaml#
> +
> +properties:
> + compatible:
> + enum:
> + - aspeed,ast2600-i2c-bus
> +
> + reg:
> + minItems: 1
<form letter>
This is a friendly reminder during the review process.
It seems my or other reviewer's previous comments were not fully
addressed. Maybe the feedback got lost between the quotes, maybe you
just forgot to apply it. Please go back to the previous discussion and
either implement all requested changes or keep discussing them.
Thank you.
</form letter>
> + items:
> + - description: address offset and range of bus
> + - description: address offset and range of bus buffer
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
Nothing improved
> + description:
> + root clock of bus, should reference the APB
> + clock in the second cell
Really, you just ignored all the comments.
No wonder this is v21 and there will be more. Please re-think what is
going wrong in this process that you need 22 or more revisions.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-27 19:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 6:12 [PATCH v21 0/4] Add ASPEED AST2600 I2C controller driver Ryan Chen
2025-10-27 6:12 ` [PATCH v21 1/4] dt-bindings: i2c: Split AST2600 binding into a new YAML Ryan Chen
2025-10-27 19:11 ` Krzysztof Kozlowski [this message]
2025-10-30 6:04 ` Jeremy Kerr
2025-11-05 7:04 ` Krzysztof Kozlowski
2025-10-27 6:12 ` [PATCH v21 2/4] dt-bindings: i2c: ast2600-i2c.yaml: Add global-regs and transfer-mode properties Ryan Chen
2025-10-27 19:14 ` Krzysztof Kozlowski
2025-10-28 7:47 ` Krzysztof Kozlowski
2025-10-29 9:25 ` Ryan Chen
2025-10-29 11:19 ` Krzysztof Kozlowski
2025-10-30 1:48 ` Ryan Chen
2025-11-05 7:05 ` Krzysztof Kozlowski
2025-11-07 6:35 ` Ryan Chen
2025-10-27 6:12 ` [PATCH v21 3/4] i2c: ast2600: Add controller driver for new register layout Ryan Chen
2025-10-27 19:24 ` Krzysztof Kozlowski
2025-11-07 6:26 ` Ryan Chen
2025-11-07 9:42 ` andriy.shevchenko
2025-11-08 3:47 ` Ryan Chen
2025-10-27 6:12 ` [PATCH v21 4/4] i2c: ast2600: Add target mode support Ryan Chen
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=59d4d107-4f35-4906-8524-f45b9b85f0ff@kernel.org \
--to=krzk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@kernel.crashing.org \
--cc=bmc-sw@aspeedtech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naresh.solanki@9elements.com \
--cc=openbmc@lists.ozlabs.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=ryan_chen@aspeedtech.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;
as well as URLs for NNTP newsgroup(s).