[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260128-remarkable-airborne-chihuahua-a1a16c@quoll>
Date: Wed, 28 Jan 2026 11:37:23 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Abdurrahman Hussain <abdurrahman@...thop.ai>
Cc: Michal Simek <michal.simek@....com>,
Andi Shyti <andi.shyti@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, info@...ean-labs.com,
Andy Shevchenko <andriy.shevchenko@...el.com>, linux-arm-kernel@...ts.infradead.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v6 1/7] dt-bindings: i2c: xiic: make clocks optional
On Tue, Jan 27, 2026 at 09:03:55PM +0000, Abdurrahman Hussain wrote:
> The xiic driver is designed to operate without explicit clock configuration
And if you change this in the driver, then you change bindings?
You miss here explanation based on hardware - how does the hardware work
if nothing ticks it clocks?
Best regards,
Krzysztof
Powered by blists - more mailing lists