From: Stephen Boyd <sboyd@kernel.org>
To: Abhishek Sahu <absahu@codeaurora.org>,
Bjorn Andersson <andersson@kernel.org>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>,
Satya Priya Kakitapalli (Temp) <quic_skakitap@quicinc.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Ajit Pandey <quic_ajipan@quicinc.com>,
Imran Shaik <quic_imrashai@quicinc.com>,
Taniya Das <quic_tdas@quicinc.com>,
Jagadeesh Kona <quic_jkona@quicinc.com>
Subject: Re: [PATCH 4/5] clk: qcom: Add camera clock controller driver for SM8150
Date: Fri, 05 Apr 2024 14:32:10 -0700 [thread overview]
Message-ID: <5a6c424fafd7ca1281f4bd771b8c8219.sboyd@kernel.org> (raw)
In-Reply-To: <66968793-d0c9-9f31-6616-f67fdadcd6e5@quicinc.com>
Quoting Satya Priya Kakitapalli (Temp) (2024-04-04 23:27:29)
>
> On 3/2/2024 9:43 PM, Bryan O'Donoghue wrote:
> >
> > Alternatively switch on the always-on clocks before the really_probe()
> > but then roll back in a probe_err: goto
> >
> > probe_err:
> > remap_bits_update(regmap, 0xc1e4, BIT(0), 0);
> > pm_runtime_put_sync(&pdev->dev);
> >
> > There may be corner cases where always-on has to happen before
> > really_probe() I suppose but as a general pattern the above should be
> > how we go.
> >
>
> I have rechecked this and see that this clock is PoR ON (i.e BIT(0) is
> set upon power ON) and it should be kept always ON as per HW
> recommendation. So even if the probe fails we shouldn't be clearing it
> against the hw recommendation. We are setting the bit here again to make
> sure it is set when the driver probes.
>
Yes, always on clks should always be on. We don't turn them off if the
driver fails to probe. We should probably print a warning or something
if the register write fails, but since this is mmio it won't fail, so
just make sure they're on and move on.
next prev parent reply other threads:[~2024-04-05 21:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 5:38 [PATCH 0/5] clk: qcom: sm8150: Add camera clock controller support for SM8150 Satya Priya Kakitapalli
2024-02-29 5:38 ` [PATCH 1/5] clk: qcom: alpha-pll: Fix the pll post div mask Satya Priya Kakitapalli
2024-03-01 23:48 ` Konrad Dybcio
2024-02-29 5:38 ` [PATCH 2/5] clk: qcom: clk-alpha-pll: Add support for Regera PLL ops Satya Priya Kakitapalli
2024-03-01 23:56 ` Konrad Dybcio
2024-03-08 8:26 ` Satya Priya Kakitapalli (Temp)
2024-03-13 18:43 ` Konrad Dybcio
2024-02-29 5:38 ` [PATCH 3/5] dt-bindings: clock: qcom: Add SM8150 camera clock controller Satya Priya Kakitapalli
2024-02-29 8:00 ` Krzysztof Kozlowski
2024-02-29 5:38 ` [PATCH 4/5] clk: qcom: Add camera clock controller driver for SM8150 Satya Priya Kakitapalli
2024-03-02 16:13 ` Bryan O'Donoghue
2024-03-06 8:30 ` Satya Priya Kakitapalli (Temp)
2024-03-06 13:55 ` Bryan O'Donoghue
2024-03-08 10:46 ` Satya Priya Kakitapalli (Temp)
2024-03-08 10:58 ` Bryan O'Donoghue
2024-03-08 10:59 ` Bryan O'Donoghue
2024-03-08 12:40 ` Satya Priya Kakitapalli (Temp)
2024-03-08 13:04 ` Bryan O'Donoghue
2024-03-08 11:54 ` Dmitry Baryshkov
2024-03-28 9:42 ` Satya Priya Kakitapalli (Temp)
2024-04-05 6:27 ` Satya Priya Kakitapalli (Temp)
2024-04-05 21:32 ` Stephen Boyd [this message]
2024-02-29 5:38 ` [PATCH 5/5] arm64: dts: qcom: Add camera clock controller for sm8150 Satya Priya Kakitapalli
2024-03-02 16:15 ` Bryan O'Donoghue
2024-03-06 8:32 ` Satya Priya Kakitapalli (Temp)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5a6c424fafd7ca1281f4bd771b8c8219.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=absahu@codeaurora.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_skakitap@quicinc.com \
--cc=quic_tdas@quicinc.com \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).