devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/4] dt-bindings: i2c: ast2600-i2c.yaml: Add global-regs and transfer-mode properties
Date: Mon, 27 Oct 2025 20:14:45 +0100	[thread overview]
Message-ID: <93a2ff5f-2f8e-494b-9652-b93bc243c229@kernel.org> (raw)
In-Reply-To: <20251027061240.3427875-3-ryan_chen@aspeedtech.com>

On 27/10/2025 07:12, Ryan Chen wrote:
> The AST2600 I2C controller supports three transfer modes: byte,
> buffer, and DMA. To allow board designers and firmware to
> explicitly select the preferred transfer mode for each controller
> instance. "aspeed,transfer-mode" to allow device tree to specify
> the desired transfer method used by each I2C controller instance.
> 
> And AST2600 i2c controller have two register mode, one is legacy
> register layout which is mix controller/target register control
> together, another is new mode which is separate controller/target
> register control.
> 

This implies your "reg" properties have now completely different meaning
and this would be quite an ABI break. We discussed this probably 15
revisions ago. Where did you document the resolution of that discussion?

>  
>  unevaluatedProperties: false
>  
> @@ -57,10 +85,12 @@ examples:
>        #address-cells = <1>;
>        #size-cells = <0>;
>        compatible = "aspeed,ast2600-i2c-bus";
> -      reg = <0x40 0x40>;
> +      reg = <0x80 0x80>, <0xc00 0x20>;

Not relevant to this patch. You just added this line in patch #1, so did
you add incorrect code just to fix it right away?

No, fix your example when creating it.


Best regards,
Krzysztof

  reply	other threads:[~2025-10-27 19:14 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
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 [this message]
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=93a2ff5f-2f8e-494b-9652-b93bc243c229@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).