Re: [PATCH v3 5/6] clk: qcom: Add support for Global clock controller on Eliza
From: Abel Vesa
Date: Tue Feb 17 2026 - 02:58:23 EST
On 26-02-16 16:38:15, Konrad Dybcio wrote:
> On 2/16/26 2:43 PM, Abel Vesa wrote:
> > From: Taniya Das <taniya.das@xxxxxxxxxxxxxxxx>
> >
> > Add support for Global clock controller for Eliza Qualcomm SoC.
> >
> > Signed-off-by: Taniya Das <taniya.das@xxxxxxxxxxxxxxxx>
> > Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxxxxxxxx>
> > Signed-off-by: Abel Vesa <abel.vesa@xxxxxxxxxxxxxxxx>
> > ---
>
> [...]
>
>
> > +static struct clk_regmap_mux gcc_pcie_0_pipe_clk_src = {
>
> This and a number of others should be struct clk_regmap_phy_mux instead,
> cross-check with kaanapali and remember to drop the then-unused parentmaps
Oups, missed this in v4. Will fix in v5.
>
> [...]
>
> > + [GCC_CAMERA_HF_CLK_EN_SLP_STG] = { 0x26018, 1 },
> > + [GCC_CAMERA_SF_CLK_EN_SLP_STG] = { 0x26028, 1 },
> > + [GCC_CAMERA_HF_CLK_EN_SEL_SLP_STG] = { 0x26018, 2 },
> > + [GCC_CAMERA_SF_CLK_EN_SEL_SLP_STG] = { 0x26028, 2 },
>
> So SEL_SLP_STG=0x1 allows setting SLP_STG to =0x1 to assert the ARES,
> otherwise if SEL_SLP_STG=0x0, it's controlled by the HW state machine
>
> I don't think modelling the prior one as a reset is valid, but I don't
> know what considerations we need to take wrt dis/allowing hw control
> here and what the consumer expectations are.
>
> Taniya, would you know?
>
> Konrad