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 3/4] i2c: ast2600: Add controller driver for new register layout
Date: Mon, 27 Oct 2025 20:24:41 +0100 [thread overview]
Message-ID: <f08b1078-fc8c-4834-984c-813e01291033@kernel.org> (raw)
In-Reply-To: <20251027061240.3427875-4-ryan_chen@aspeedtech.com>
On 27/10/2025 07:12, Ryan Chen wrote:
> Add i2c-ast2600 new register mode driver to support AST2600
> i2c new register mode. This i2c-ast2600 new driver and the
> legacy i2c-aspeed driver both match the same compatible string
> "aspeed,ast2600-i2c-bus" because they target the same I2C
> controller IP on AST2600. However, AST2600 SoCs may configure
Where did you document ABI compatibility of new driver with old DTS,
which do not have required properties and uses old reg?
I don't see that. I actually clearly see:
> + i2c_bus = devm_kzalloc(dev, sizeof(*i2c_bus), GFP_KERNEL);
> + if (!i2c_bus)
> + return -ENOMEM;
> +
> + i2c_bus->reg_base = devm_platform_ioremap_resource(pdev, 0);
> + if (IS_ERR(i2c_bus->reg_base))
> + return PTR_ERR(i2c_bus->reg_base);
> +
> + rst = devm_reset_control_get_shared_deasserted(dev, NULL);
> + if (IS_ERR(rst))
> + return dev_err_probe(dev, PTR_ERR(rst), "Missing reset ctrl\n");
> +
> + i2c_bus->global_regs =
> + syscon_regmap_lookup_by_phandle(dev_of_node(dev), "aspeed,global-regs");
> + if (IS_ERR(i2c_bus->global_regs))
> + return PTR_ERR(i2c_bus->global_regs);
ABI break. No explanation of that ABI break, not even mentioning it.
There is no reason to break the ABI. Your new driver *must* support both
interfaces and both DTB. You *cannot* (please listen carefully, because
in the past we wasted a lot of time discussing simple statements) rely
on legacy driver binding to old DTB, because it is the same compatible.
You need to rewrite all this to handle both DTBs in backwards compatible
way.
NAK
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-10-27 19:24 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
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 [this message]
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=f08b1078-fc8c-4834-984c-813e01291033@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).