[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76f3bc23-8677-42bd-a3a5-43b17cbe552e@linaro.org>
Date: Fri, 15 Sep 2023 14:19:56 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Michael Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...nel.org>,
Sricharan Ramabadhran <quic_srichara@...cinc.com>,
Gokul Sriram Palanisamy <quic_gokulsri@...cinc.com>,
Varadarajan Narayanan <quic_varada@...cinc.com>,
Anusha Rao <quic_anusha@...cinc.com>,
Devi Priya <quic_devipriy@...cinc.com>,
Jassi Brar <jassisinghbrar@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2 01/11] clk: qcom: ipq8074: drop the CLK_SET_RATE_PARENT
flag from PLL clocks
On 14.09.2023 08:59, Kathiravan Thirumoorthy wrote:
> GPLL, NSS crypto PLL clock rates are fixed and shouldn't be scaled based
> on the request from dependent clocks. Doing so will result in the
> unexpected behaviour. So drop the CLK_SET_RATE_PARENT flag from the PLL
> clocks.
>
> Cc: stable@...r.kernel.org
> Fixes: b8e7e519625f ("clk: qcom: ipq8074: add remaining PLL’s")
> Signed-off-by: Kathiravan Thirumoorthy <quic_kathirav@...cinc.com>
> ---
Stephen, do you think there should be some sort of error
or at least warning thrown when SET_RATE_PARENT is used with
RO ops?
Konrad
Powered by blists - more mailing lists