Re: [PATCH v7 1/6] i2c: xiic: skip input clock setup on non-OF systems
From: Abdurrahman Hussain <abdurrahman@nexthop.ai>
Date: 2026-01-29 23:29:56
Also in:
linux-devicetree, linux-i2c, lkml
From: Abdurrahman Hussain <abdurrahman@nexthop.ai>
Date: 2026-01-29 23:29:56
Also in:
linux-devicetree, linux-i2c, lkml
On Jan 29, 2026, at 2:43 PM, Andrew Lunn [off-list ref] wrote: On Thu, Jan 29, 2026 at 09:43:13PM +0000, Abdurrahman Hussain via B4 Relay wrote:quoted
From: Abdurrahman Hussain <abdurrahman@nexthop.ai> The xiic driver supports operation without explicit clock configuration when clocks cannot be specified via firmware, such as on ACPI-based systems.Are you saying it is technically impossible to specify a clock in ACPI? Maybe a more accurate would be: The xiic driver supports operation without explicit clock configuration when the clocks are not specified via firmware, such as when the ACPI tables are missing the description of the clocks. Andrew
Actually, ACPI (since 6.5) added a ClockInput() macro that can be added to _CRS of a device node. The ACPI subsystem in kernel could parse these and convert into proper clocks integrated with the CCF. But, AFAIK, this idea was rejected in the past. So, technically, it's the kernel that lacks support on ACPI systems. What about this wording then: The xiic driver supports operation without explicit clock configuration when the clocks specified via firmware are ignored, such as on ACPI systems. Abdurrahman