On 6/30/26 2:56 PM, Konrad Dybcio wrote: > On 5/8/26 12:49 AM, Loic Poulain wrote: >> On Agatti, the CAMSS AXI clock is not managed by the interconnect >> and defaults to its lowest rate (19.2 MHz), which is insufficient >> and leads to throttling of CAMSS-related traffic. >> >> Set the CAMSS AXI clock to a suitable operating point by assigning >> it to its nominal frequency (300 MHz) as defined by the specification. >> This ensures correct and stable operation while leaving room for >> future dynamic scaling support in the driver. > > Now that I think about it, since the clock is already consumed by > the driver, can we just put a set_rate in there? > > This will avoid introducing a point in time where the DT has a > suboptimal (power-wise) floor mandated regardless of what the driver > does
What I just said does not quite match reality The ultimate solution is going to involve some aggregation and then a set_rate. We can just hardcode the set_rate today instead, I think Konrad
