linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Amit Pundir <amit.pundir@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Doug Anderson <dianders@chromium.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Caleb Connolly <caleb.connolly@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: regressions <regressions@lists.linux.dev>,
	linux-arm-msm <linux-arm-msm@vger.kernel.org>,
	dt <devicetree@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: qcom: sdm845-db845c: Move LVS regulator nodes up
Date: Wed, 7 Jun 2023 09:46:27 +0200	[thread overview]
Message-ID: <407ace5b-5c63-a6de-ff41-24d5cd1d4eb8@linaro.org> (raw)
In-Reply-To: <20230602161246.1855448-1-amit.pundir@linaro.org>

On 02/06/2023 18:12, Amit Pundir wrote:
> Move lvs1 and lvs2 regulator nodes up in the rpmh-regulators
> list to workaround a boot regression uncovered by the upstream
> commit ad44ac082fdf ("regulator: qcom-rpmh: Revert "regulator:
> qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS"").
> 
> Without this fix DB845c fail to boot at times because one of the
> lvs1 or lvs2 regulators fail to turn ON in time.

Why regulator would fail to turn on time? If it has ramp-up delay, add
it to DT. Otherwise how is it possible? You have a consumer, right?

This is not the correct solution and it is hiding real issue.

Best regards,
Krzysztof


  parent reply	other threads:[~2023-06-07  7:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 16:12 [PATCH] arm64: dts: qcom: sdm845-db845c: Move LVS regulator nodes up Amit Pundir
2023-06-06 23:34 ` Doug Anderson
2023-06-07  7:49   ` Krzysztof Kozlowski
2023-06-07  9:17     ` Amit Pundir
2023-06-07 10:16       ` Krzysztof Kozlowski
2023-06-08 17:26         ` Amit Pundir
2023-06-08 17:44           ` Doug Anderson
2023-06-07  7:46 ` Krzysztof Kozlowski [this message]
2023-06-14 18:18 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-14 18:47   ` Krzysztof Kozlowski
2023-06-14 19:08     ` Amit Pundir
2023-06-15 13:47       ` Amit Pundir
2023-06-15 15:03         ` Krzysztof Kozlowski
2023-06-15 16:09           ` Amit Pundir
2023-06-15 16:15             ` Amit Pundir
2023-06-16  8:27             ` Krzysztof Kozlowski
2023-06-16 17:09               ` Amit Pundir
2023-06-17  7:21                 ` Krzysztof Kozlowski
2023-06-19  7:06                   ` Amit Pundir
2023-06-14 19:44     ` Doug Anderson
2023-06-20 15:59       ` Bjorn Andersson
2023-06-22  7:47         ` Linux regression tracking (Thorsten Leemhuis)
2023-06-22 11:48           ` Amit Pundir
2023-07-07  5:08             ` Amit Pundir
2023-07-14 11:04               ` Linux regression tracking #update (Thorsten Leemhuis)

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=407ace5b-5c63-a6de-ff41-24d5cd1d4eb8@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=amit.pundir@linaro.org \
    --cc=andersson@kernel.org \
    --cc=broonie@kernel.org \
    --cc=caleb.connolly@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=robh+dt@kernel.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).