Message-ID: <7666a6dad5c698483c30356d1278025a.sboyd@kernel.org>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20230217080720.5206-1-quic_kathirav@quicinc.com>
References: <20230217080720.5206-1-quic_kathirav@quicinc.com>
Subject: Re: [PATCH V3] clk: qcom: ipq5332: mark GPLL4 as critical temporarily
From:   Stephen Boyd <sboyd@kernel.org>
Cc:     quic_varada@quicinc.com, quic_srichara@quicinc.com,
        Kathiravan T <quic_kathirav@quicinc.com>
To:     Kathiravan T <quic_kathirav@quicinc.com>, agross@kernel.org,
        andersson@kernel.org, konrad.dybcio@linaro.org,
        linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
        linux-kernel@vger.kernel.org, mturquette@baylibre.com
Date:   Fri, 17 Feb 2023 14:36:27 -0800
User-Agent: alot/0.10
Precedence: bulk

Quoting Kathiravan T (2023-02-17 00:07:20)
> Clock framework disables the GPLL4 source since there are no active users
> for this source currently. Some of the clocks initialized by the
> bootloaders uses the GPLL4 as the source. Due to this, when the GPLL4 is
> disabled by the clock framework, system is going for the reboot.
>=20
> To avoid this, mark the GPLL4 as CRITICAL so that clock framework

s/CRITICAL/ignore unused/

> doesn't disable it. Once the users of this source is enabled, we can get
> rid of this flag.
>=20
> Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>