[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76a0b578efb62a6e6bd7dafd477fa15b1062a09c.camel@codeconstruct.com.au>
Date: Fri, 24 Oct 2025 16:41:53 +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 Kyzysztof,
> > Not much different than every other soc. All of them are separate
> > IPs.
> > Look at any Samsung, NXP or Qualcomm binding. Separate IPs.
>
>
> So let the move happen, but please explain in the commit msg that
> devices are completely different - nothing in common - and thus the
> binding will be different. We indeed do not keep completely different
> devices in one binding, but based on commit msg I had impression this
> was just major block upgrade.
OK, makes sense.
Ryan, let me know if you need a hand with the commit message changes.
Cheers,
Jeremy
Powered by blists - more mailing lists