[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e0d2c55-fb2f-4903-a555-f51019942c6e@linaro.org>
Date: Sat, 18 Nov 2023 01:06:06 +0100
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>,
Sibi Sankar <quic_sibis@...cinc.com>, andersson@...nel.org,
mturquette@...libre.com, sboyd@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Cc: agross@...nel.org, conor+dt@...nel.org, quic_tdas@...cinc.com,
quic_rjendra@...cinc.com, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, neil.armstrong@...aro.org,
abel.vesa@...aro.org, quic_tsoni@...cinc.com
Subject: Re: [PATCH V2 2/4] clk: qcom: Add Global Clock controller (GCC)
driver for X1E80100
On 17.11.2023 21:50, Bryan O'Donoghue wrote:
> On 17/11/2023 09:27, Sibi Sankar wrote:
>> * Use shared ops in the x1e80100 gcc driver [Bryan].
>
> This looks better to me now / more consistent with what we have in sc8280xp - where we do try to hit suspend and => retention/parking matters.
Parking the clock is separate from putting the system to sleep.
IIUC we usually use shared ops on clocks that may have different users
(e.g. not only controlled by Linux) and/or that are crucial to the
functioning of hardware (like AXI clocks, which if gated would make
the system crash on any access attempt, from any subsystem, unless
turned on beforehand)
Perhaps Dmitry can use some clearer wording than me..
Konrad
Powered by blists - more mailing lists