From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] arm64: dts: qcom: sm8550-mtp: use correct UFS supply
Date: Wed, 6 Sep 2023 13:39:46 +0200 [thread overview]
Message-ID: <fe346849-cd0f-aee5-9ab9-ea581025329b@linaro.org> (raw)
In-Reply-To: <9c7fae56-85a2-4691-8192-24237761d25c@linaro.org>
On 06/09/2023 13:28, Konrad Dybcio wrote:
> On 6.09.2023 12:47, Krzysztof Kozlowski wrote:
>> According to schematics the VCCQ2 supply is not connected and the L3G
>> regulator instead powers up the controller pads (VDD_PX10). Use correct
>> supply vdd-hba and drop unsupported current limit for the vdd-hba.
> Why is it unsupported?
Maybe I was here not precise. I move the regulator from vccq2 to
vdd-hba. vccq2 has control of current in UFS core driver. Bindings also
allow it.
vdd-hba does not have current control in UFS (ignored) and bindings do
not allow such max-microamp property. Why? I don't know. That's how it
is done.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-09-06 11:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 10:47 [PATCH 1/6] arm64: dts: qcom: sm8550-mtp: use correct UFS supply Krzysztof Kozlowski
2023-09-06 10:47 ` [PATCH 2/6] arm64: dts: qcom: sm8550-qrd: " Krzysztof Kozlowski
2023-09-06 12:07 ` Konrad Dybcio
2023-09-06 10:47 ` [PATCH 3/6] arm64: dts: qcom: sm8450-hdk: add UFS host controller supply Krzysztof Kozlowski
2023-09-06 11:29 ` Konrad Dybcio
2023-09-06 10:47 ` [PATCH 4/6] arm64: dts: qcom: sm8450-qrd: " Krzysztof Kozlowski
2023-09-06 11:28 ` Konrad Dybcio
2023-09-06 10:47 ` [PATCH 5/6] arm64: dts: qcom: sm8350-hdk: " Krzysztof Kozlowski
2023-09-06 11:29 ` Konrad Dybcio
2023-09-06 10:47 ` [PATCH 6/6] arm64: dts: qcom: sm8350-mtp: " Krzysztof Kozlowski
2023-09-06 11:29 ` Konrad Dybcio
2023-09-06 11:28 ` [PATCH 1/6] arm64: dts: qcom: sm8550-mtp: use correct UFS supply Konrad Dybcio
2023-09-06 11:39 ` Krzysztof Kozlowski [this message]
2023-09-06 11:50 ` Konrad Dybcio
2023-09-06 12:05 ` Krzysztof Kozlowski
2023-09-06 12:07 ` Konrad Dybcio
2023-09-14 16:04 ` (subset) " 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=fe346849-cd0f-aee5-9ab9-ea581025329b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.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-kernel@vger.kernel.org \
--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).