Re: [PATCH v3 1/3] dt-bindings: clock: qcom,camcc-sm8250: add interconnect provider

[Bryan O'Donoghue]

On 29/10/2026 01:50, Dmitry Baryshkov wrote:
>  From my PoV, CAMNOX_AXI, is just the same NoC clock, just not being
> wired through RPM/RPMh. From this point of view the clock can be
> described as as an interconnect, it gives correct abstraction: no matter
> how the camera blocks are connected or how the connection between them
> is managed in hardware / firmware / clock devices, there is a bus (aka
> interconnect) between those camera blocks. If at some point the clock
> becomes managed by RPMh, it won't (significantly) change the hardware
> description

yeah I think it should be an icc provider - perhaps interconnect nodes 
make sense, not for one clock but for a number of clocks and components 
in the system JPEG, ICP voting on the bandwidth/clocks.

TBH my point here is more we need to soak up the CPAs clock logic in an 
putative cpas_icc_set() routine since I'm... as sure as I can be that 
icc_set_bw() on its own and CCF can't really capture that logic.

---
bod