[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ab29903-9861-4736-b827-5dd45b504baa@linaro.org>
Date: Wed, 30 Aug 2023 12:09:29 +0200
From: Konrad Dybcio <konrad.dybcio@...aro.org>
To: Luca Weiss <luca.weiss@...rphone.com>,
cros-qcom-dts-watchers@...omium.org,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Linus Walleij <linus.walleij@...aro.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>
Cc: ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [PATCH 03/11] arm64: dts: qcom: sc7280: Move qfprom clock to
chrome-common
On 30.08.2023 11:58, Luca Weiss wrote:
> On non-ChromeOS boards the clock cannot be touched, so move it in the
> chrome-common dtsi which is the only place where it's needed.
>
> Signed-off-by: Luca Weiss <luca.weiss@...rphone.com>
> ---
If that clock is not registered (e.g. it's in protected-clocks = <>,
would the _optional handler not handle it just fine?
Konrad
Powered by blists - more mailing lists