Re: [PATCH 00/48] clk: qcom: Use common probe data for always-on clocks

[Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>]

On 9/16/26 12:28 PM, Abel Vesa wrote:
> Many Qualcomm clock controller drivers still enable always-on branches
> with individual qcom_branch_set_clk_en() calls in their probe functions.
> The common probe code already supports describing these register offsets
> through the clk_cbcrs and num_clk_cbcrs fields of qcom_cc_driver_data.
> 
> Convert the remaining users of these direct calls to per-controller
> critical_cbcrs arrays. This centralizes branch enable handling in the
> common probe path and makes the always-on register lists easier to review
> alongside the other controller data.
> 
> For GCC drivers, also describe DFS RCGs through the common driver data and
> move auxiliary register programming into clk_regs_configure callbacks
> where appropriate. Drivers whose initialization is fully covered by the
> common path can then use qcom_cc_probe() directly. Keep device-specific
> setup in the remaining probe functions, including the separate CBCR lists
> needed by the SA8775P/QCS8300 camera and SM8350/SC8280XP video variants.
> 
> Signed-off-by: Abel Vesa <abel.vesa@oss.qualcomm.com>
> ---

I left a couple comments as replies, but let's have them be additive
touch-ups on top of this so as not to resend 48 patches

for this series:

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad