Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Chukun Pan <amadeus@jmu.edu.cn>
To: dmitry.baryshkov@linaro.org
Cc: amadeus@jmu.edu.cn, andersson@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, konrad.dybcio@linaro.org,
	krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: ipq6018: move mp5496 regulator outside soc dtsi
Date: Sun, 10 Mar 2024 18:10:05 +0800	[thread overview]
Message-ID: <20240310101005.13541-1-amadeus@jmu.edu.cn> (raw)
In-Reply-To: <CAA8EJprc_xjejMANBjDkA2_FnRcYSJYsmM4VOvsKu1FkuMvGeg@mail.gmail.com>

Hi, Dmitry
> Please inline this dtsi file into the board file. While it might seem
> to make life easier, having such includes makes following regulator
> settings much harder. Especially once a board or two start overriding
> or expanding those settings.

Thanks for your suggestion. But unlike mobile phones or dev boards,
I don't think any manufacturer will change the voltage settings of
the mp5496 pmic on the ipq60xx router. The s2 part of mp5496 pmic
is used to supply the CPU, and its min/max voltage corresponds to
the CPU frequency of ipq60xx. Although the downstream qsdk kernel
uses the cpr regulator driver, its min/max voltage is still the
same as the current setting.

Thanks,
Chukun

-- 
2.25.1


  reply	other threads:[~2024-03-10 10:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06 14:03 [PATCH v2 0/4] arm64: dts: qcom: ipq6018: rework CPU Frequency Chukun Pan
2024-03-06 14:03 ` [PATCH v2 1/4] arm64: dts: qcom: ipq6018: add 1.2GHz " Chukun Pan
2024-03-06 14:33   ` Dmitry Baryshkov
2024-03-06 15:36     ` Chukun Pan
2024-03-06 19:34       ` Dmitry Baryshkov
2024-03-07  3:02         ` Chukun Pan
2024-03-07  7:29           ` Dmitry Baryshkov
2024-03-07 10:02             ` Chukun Pan
2024-03-07 10:13               ` Dmitry Baryshkov
2024-03-12 15:37           ` Kathiravan Thirumoorthy
2024-03-13  7:18             ` Chukun Pan
2024-03-13  9:32               ` Kathiravan Thirumoorthy
2024-03-06 16:20   ` Konrad Dybcio
2024-03-07  2:50     ` Chukun Pan
2024-03-06 20:38   ` Robert Marko
2024-03-07  3:26     ` Chukun Pan
2024-03-08  8:51       ` Robert Marko
2024-03-06 14:03 ` [PATCH v2 2/4] arm64: dts: qcom: ipq6018: add 1.5GHz " Chukun Pan
2024-03-06 14:36   ` Dmitry Baryshkov
2024-03-06 15:40     ` Chukun Pan
2024-03-06 19:36       ` Dmitry Baryshkov
2024-03-07  3:08         ` [PATCH v2 1/4] arm64: dts: qcom: ipq6018: add 1.2GHz " Chukun Pan
2024-03-06 16:20   ` [PATCH v2 2/4] arm64: dts: qcom: ipq6018: add 1.5GHz " Konrad Dybcio
2024-03-06 14:03 ` [PATCH v2 3/4] arm64: dts: qcom: ipq6018: move mp5496 regulator outside soc dtsi Chukun Pan
2024-03-06 14:38   ` Dmitry Baryshkov
2024-03-10 10:10     ` Chukun Pan [this message]
2024-03-06 14:03 ` [PATCH v2 4/4] arm64: dts: qcom: ipq6018-mp5496: add LDOA2 regulator Chukun Pan

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=20240310101005.13541-1-amadeus@jmu.edu.cn \
    --to=amadeus@jmu.edu.cn \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.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@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