Thread (21 messages) 21 messages, 8 authors, 2026-01-30

Re: [PATCH v6 1/7] dt-bindings: i2c: xiic: make clocks optional

From: Michal Simek <michal.simek@amd.com>
Date: 2026-01-28 11:21:49
Also in: linux-devicetree, linux-i2c, lkml


On 1/28/26 11:37, Krzysztof Kozlowski wrote:
On Tue, Jan 27, 2026 at 09:03:55PM +0000, Abdurrahman Hussain wrote:
quoted
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?
Hardware obviously have clock input which needs to be connected. Without it it 
won't work.
And there are designs like Microblaze one where clock is shared with cpu itself 
and there is no way to adjust it. It is just working.

Then we have configurations where clock is coming from clock generator which 
needs to be enabled. That's case for SOCs with ARM cpus or with clock generators.

This series targets case around PCIe EP. Clock is likely derived from PCIe 
itself and there is no way how to change it, adjust it. It is just running on 
fixed value.

In DT this is design/described via fixed-clock but I expect this concept is not 
used on systems with ACPI.

Thanks,
Michal
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help