[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf3d6690b9124ecf74df6c0f9f1c0f72ae1db9f7.camel@codeconstruct.com.au>
Date: Fri, 24 Oct 2025 15:56:03 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Krzysztof Kozlowski <krzk@...nel.org>, Ryan Chen
<ryan_chen@...eedtech.com>
Cc: benh@...nel.crashing.org, joel@....id.au, andi.shyti@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
andrew@...econstruct.com.au, p.zabel@...gutronix.de,
andriy.shevchenko@...ux.intel.com, naresh.solanki@...ements.com,
linux-i2c@...r.kernel.org, openbmc@...ts.ozlabs.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v20 1/4] dt-bindings: i2c: Split AST2600 binding into a
new YAML
Hi Krzysztof,
> Although now I saw next patch, so clearly this commit is incomplete.
The split that Ryan has done here - by shifting to an identical separate
binding, then making the changes explicit - allows us to review the
actual changes without losing them in the move. Sounds like a benefit to
me?
> You just need allOf:if:then: section to narrow the
> constraints/presence of properties.
That seems like a more complex approach. This is separate IP from the
2500 controllers, wouldn't that warrant a new binding spec?
Cheers,
Jeremy
Powered by blists - more mailing lists