From: Tengfei Fan <quic_tengfan@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <andersson@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<dmitry.baryshkov@linaro.org>
Cc: <linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel@quicinc.com>,
Fenglin Wu <quic_fenglinw@quicinc.com>
Subject: Re: [PATCH v10 3/4] arm64: dts: qcom: add base AIM300 dtsi
Date: Mon, 24 Jun 2024 10:22:21 +0800 [thread overview]
Message-ID: <af2a373d-9627-4067-80d7-3029e6f0fa34@quicinc.com> (raw)
In-Reply-To: <e344335f-be60-4568-97be-728257684310@linaro.org>
On 6/22/2024 7:09 PM, Konrad Dybcio wrote:
> On 20.06.2024 2:46 AM, Tengfei Fan wrote:
>>
>>
>> On 6/19/2024 3:06 AM, Konrad Dybcio wrote:
>>>
>>>
>>> On 6/18/24 09:22, Tengfei Fan wrote:
>>>> AIM300 Series is a highly optimized family of modules designed to
>>>> support AIoT applications. It integrates QCS8550 SoC, UFS and PMIC
>>>> chip etc.
>>>> Here is a diagram of AIM300 SoM:
>>>> +----------------------------------------+
>>>> |AIM300 SoM |
>>>> | |
>>>> | +-----+ |
>>>> | |--->| UFS | |
>>>> | | +-----+ |
>>>> | | |
>>>> | | |
>>>> 3.7v | +-----------------+ | +---------+ |
>>>> ---------->| PMIC |----->| QCS8550 | |
>>>> | +-----------------+ +---------+ |
>>>> | | |
>>>> | | |
>>>> | | +-----+ |
>>>> | |--->| ... | |
>>>> | +-----+ |
>>>> | |
>>>> +----------------------------------------+
>>>>
>>>> Co-developed-by: Fenglin Wu <quic_fenglinw@quicinc.com>
>>>> Signed-off-by: Fenglin Wu <quic_fenglinw@quicinc.com>
>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>>>> ---
>>>
>>> [...]
>>>
>>>> +&ufs_mem_hc {
>>>> + reset-gpios = <&tlmm 210 GPIO_ACTIVE_LOW>;
>>>> + vcc-supply = <&vreg_l17b_2p5>;
>>>> + vcc-max-microamp = <1300000>;
>>>> + vccq-supply = <&vreg_l1g_1p2>;
>>>> + vccq-max-microamp = <1200000>;
>>>> + vdd-hba-supply = <&vreg_l3g_1p2>;
>>>
>>> These regulators should generally have:
>>>
>>> regulator-allow-set-load;
>>> regulator-allowed-modes = <RPMH_REGULATOR_MODE_LPM
>>> RPMH_REGULATOR_MODE_HPM>;
>>>
>>> although the current setup you have never lets them exit HPM
>>>
>>> Konrad
>>
>> I understand your point is that these settings need to be added to allthe child regulator nodes of regulators-0, regulators-1, regulators-2, regulators-3, regulators-4 and regulators-5. Is that correct?
>
> No, I only meant the three references in the UFS node (l17b, l1g, l3g),
> although I suppose such properties should be there by default on all
> regulators in order to save power.. but most boards don't do that (yet),
> as nobody wants to waste their time with potentially one more thing to
> debug
Thank you for clarifying this. I will create a new patch to support
these since this patch series have already been applied.
>
> Konrad
--
Thx and BRs,
Tengfei Fan
next prev parent reply other threads:[~2024-06-24 2:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 7:21 [PATCH v10 0/4] arm64: dts: qcom: aim300: add AIM300 AIoT Tengfei Fan
2024-06-18 7:21 ` [PATCH v10 1/4] dt-bindings: arm: qcom: Document QCS8550 SoC and the AIM300 AIoT board Tengfei Fan
2024-06-18 7:22 ` [PATCH v10 2/4] arm64: dts: qcom: qcs8550: introduce qcs8550 dtsi Tengfei Fan
2024-06-18 10:06 ` Caleb Connolly
2024-06-20 13:40 ` Tengfei Fan
2024-06-20 13:49 ` Caleb Connolly
2024-06-21 1:12 ` Tengfei Fan
2024-06-18 7:22 ` [PATCH v10 3/4] arm64: dts: qcom: add base AIM300 dtsi Tengfei Fan
2024-06-18 19:06 ` Konrad Dybcio
2024-06-20 0:46 ` Tengfei Fan
2024-06-22 11:09 ` Konrad Dybcio
2024-06-24 2:22 ` Tengfei Fan [this message]
2024-06-18 7:22 ` [PATCH v10 4/4] arm64: dts: qcom: aim300: add AIM300 AIoT Tengfei Fan
2024-06-18 8:48 ` Dmitry Baryshkov
2024-06-18 8:57 ` Tengfei Fan
2024-06-21 6:11 ` [PATCH v10 0/4] " 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=af2a373d-9627-4067-80d7-3029e6f0fa34@quicinc.com \
--to=quic_tengfan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_fenglinw@quicinc.com \
--cc=robh@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).