On Mon Jul 6, 2026 at 3:37 PM BST, Daniel Almeida wrote: > The clk API allows fine-grained control, but some drivers might be > more interested in a "set and forget" API. > > Expand the current API to support this. The clock will automatically be > disabled, unprepared and freed when the device is unbound from the bus > without further intervention by the driver.
Drivers could just put the enabled clock into their driver data. Given the general shift from devres to lifetime-scoped device resources, do we still have a need for this? Best, Gary > > Signed-off-by: Daniel Almeida <[email protected]>
