[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOX2RU7NaJL5dTrjz26oiz0psvXKV8C-7HGMmJ-rfNJ3r=y2qg@mail.gmail.com>
Date: Mon, 11 Jul 2022 23:14:38 +0200
From: Robert Marko <robimarko@...il.com>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Abhishek Sahu <absahu@...eaurora.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Devicetree List <devicetree@...r.kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
krzysztof.kozlowski+dt@...aro.org,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
linux-clk@...r.kernel.org,
open list <linux-kernel@...r.kernel.org>,
Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>, tdas@...eaurora.org
Subject: Re: [PATCH v4 10/11] clk: qcom: ipq8074: dont disable gcc_sleep_clk_src
On Mon, 11 Jul 2022 at 23:10, Stephen Boyd <sboyd@...nel.org> wrote:
>
> Quoting Robert Marko (2022-05-15 14:00:47)
> > diff --git a/drivers/clk/qcom/gcc-ipq8074.c b/drivers/clk/qcom/gcc-ipq8074.c
> > index 3204d550ff76..42d185fe19c8 100644
> > --- a/drivers/clk/qcom/gcc-ipq8074.c
> > +++ b/drivers/clk/qcom/gcc-ipq8074.c
> > @@ -663,6 +663,7 @@ static struct clk_branch gcc_sleep_clk_src = {
> > },
> > .num_parents = 1,
> > .ops = &clk_branch2_ops,
> > + .flags = CLK_IS_CRITICAL,
> > },
>
> Why not just remove the clk from the driver? Is anything using it?
Hi Stephen, USB sleep clocks are derived from it so it cant be dropped.
Regards,
Robert
Powered by blists - more mailing lists