From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Marijn Suijten <marijn.suijten@somainline.org>
Cc: phone-devel@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
~postmarketos/upstreaming@lists.sr.ht,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Martin Botka <martin.botka@somainline.org>,
Jami Kettunen <jami.kettunen@somainline.org>,
Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] arm64: dts: qcom: sm6125-seine: Provide regulators to SDHCI 1
Date: Fri, 23 Dec 2022 14:20:42 +0100 [thread overview]
Message-ID: <40ce6134-e3e8-c3c7-8ba0-539b1ce3fc7c@linaro.org> (raw)
In-Reply-To: <20221223130813.qk7thawdueugb5z4@SoMainline.org>
On 23.12.2022 14:08, Marijn Suijten wrote:
> On 2022-12-23 13:00:18, Konrad Dybcio wrote:
>>
>>
>> On 22.12.2022 21:36, Marijn Suijten wrote:
>>> While SDHCI 1 appears to work out of the box, we cannot rely on the
>>> bootloader-enabled regulators nor expect them to remain enabled (e.g.
>>> when finally dropping pd_ignore_unused).
>>
>> Unrelated, unused-yet-enabled (as far as Linux is concerned, anyway,
>> it doesn't know the state of smd rpm regulators unless you add
>> regulator-boot-on) regulators get swept by "regulator cleanup".
>
> That's exactly the point made here: at least this way Linux knows that
> these regulators should remain enabled. Even if it doesn't know about
> many others and would fall flat on its face regardless when disabling
> others as part of regulator cleanup.
>
> Unless you meant something different?
I meant that regulators are not handled by pd_ignore_unused, but rather
by a similar mechanism.
Konrad
>
> - Marijn
next prev parent reply other threads:[~2022-12-23 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 20:36 [PATCH 0/5] arm64: dts: qcom: sm6125-seine: Configure regulators and enable SD Card Marijn Suijten
2022-12-22 20:36 ` [PATCH 1/5] arm64: dts: qcom: sm6125-seine: Configure PM6125 regulators Marijn Suijten
2022-12-23 11:57 ` Konrad Dybcio
2022-12-22 20:36 ` [PATCH 2/5] arm64: dts: qcom: sm6125-seine: Provide regulators to HS USB2 PHY Marijn Suijten
2022-12-23 11:58 ` Konrad Dybcio
2022-12-22 20:36 ` [PATCH 3/5] arm64: dts: qcom: sm6125-seine: Provide regulators to SDHCI 1 Marijn Suijten
2022-12-23 12:00 ` Konrad Dybcio
2022-12-23 13:08 ` Marijn Suijten
2022-12-23 13:20 ` Konrad Dybcio [this message]
2022-12-22 20:36 ` [PATCH 4/5] arm64: dts: qcom: sm6125-seine: Configure SD Card slot on SDHCI 2 Marijn Suijten
2022-12-23 12:00 ` Konrad Dybcio
2022-12-22 20:36 ` [PATCH 5/5] arm64: dts: qcom: sm6125-seine: Lock eMMC and SD Card IDs via aliases Marijn Suijten
2022-12-29 17:23 ` [PATCH 0/5] arm64: dts: qcom: sm6125-seine: Configure regulators and enable SD Card Bjorn Andersson
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=40ce6134-e3e8-c3c7-8ba0-539b1ce3fc7c@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=devicetree@vger.kernel.org \
--cc=jami.kettunen@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).