From: Rob Herring <robh@kernel.org>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: Ryan Chen <ryan_chen@aspeedtech.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andi.shyti@kernel.org" <andi.shyti@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"andrew@codeconstruct.com.au" <andrew@codeconstruct.com.au>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"naresh.solanki@9elements.com" <naresh.solanki@9elements.com>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v18 1/3] dt-bindings: i2c: aspeed,i2c.yaml: add transfer-mode and global-regs properties and update example
Date: Fri, 19 Sep 2025 15:53:29 -0500 [thread overview]
Message-ID: <20250919205329.GA2192084-robh@kernel.org> (raw)
In-Reply-To: <03abda47219b8b0b476a3740c7ed2acc4b2b16dc.camel@codeconstruct.com.au>
On Mon, Sep 15, 2025 at 11:41:31AM +0800, Jeremy Kerr wrote:
> Hi Ryan,
>
> > > OK, but the ast2400 and ast2500 I2C peripherals - which this binding also
> > > describes - do not have that facility. Given the 2600 is a distinct peripheral (as
> > > discussed on the v16 series), this would seem to warrant a distinct binding.
> > >
> > > Should this be split out into an ast2600-specific binding, to reflect that it is
> > > different hardware? The reference to the global registers and transfer modes
> > > would then be added only to the ast2600-i2c-bus binding.
> >
> > I agree it would be cleaner to split out a new binding file specifically for AST2600,
> > for example: `aspeed,ast2600-i2c.yaml`
> > But also I think `aspeed,i2cv2.yaml` more better name, that compatible will
> > support next generation such like AST2700 .....
>
> The ship may have already sailed on that one, as you already have the
> existing compatible string describing existing hardware.
>
> I would assume that the compatible string should be fixed for an
> instance of the specific hardware, but the DT maintainers may be able to
> provide some input/precedence on changing an existing binding, if
> necessary.
>
> If this does get changed, I would expect that you would need a
> corresponding update in the old driver too.
>
> Or, another option may be to keep the current generation ("v2 core with
> compat registers") as-is (ie., at ast2600-i2c-bus), and introduce a new
> string for the next - where the primary hardware change might be the
> removal of compat registers, but it's still new hardware
About the only place we use version numbers (without regret) is when the
version can be traced back to the actual verilog. This is typically only
IP targeted to FPGAs. The reality in SoCs is h/w designers can't help
themselves to not change things. In reality, there are almost always
some changes.
Rob
next prev parent reply other threads:[~2025-09-19 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 5:18 [PATCH v18 0/3] Add ASPEED AST2600 I2C controller driver Ryan Chen
2025-08-20 5:18 ` [PATCH v18 1/3] dt-bindings: i2c: aspeed,i2c.yaml: add transfer-mode and global-regs properties and update example Ryan Chen
2025-09-12 8:58 ` Jeremy Kerr
2025-09-12 9:27 ` Ryan Chen
2025-09-15 3:41 ` Jeremy Kerr
2025-09-19 20:53 ` Rob Herring [this message]
2025-09-24 5:31 ` Ryan Chen
2025-08-20 5:18 ` [PATCH v18 2/3] i2c: ast2600: Add controller driver for new register layout Ryan Chen
2025-08-20 5:18 ` [PATCH v18 3/3] i2c: ast2600: Add target mode support Ryan Chen
2025-09-01 1:06 ` 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=20250919205329.GA2192084-robh@kernel.org \
--to=robh@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@kernel.crashing.org \
--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=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).