public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Umang Chheda <umang.chheda@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	richardcochran@gmail.com
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Subject: Re: [PATCH v4 3/4] arm64: dts: qcom: monaco: Add monaco-ac EVK board
Date: Tue, 5 May 2026 00:46:58 +0530	[thread overview]
Message-ID: <b734a099-b5db-4ff9-8b75-265e7f8194a1@oss.qualcomm.com> (raw)
In-Reply-To: <0edacb23-a132-4f9c-be4f-ea3326c8d8a2@oss.qualcomm.com>



On 5/4/2026 6:23 PM, Konrad Dybcio wrote:
> On 4/27/26 7:05 PM, Umang Chheda wrote:
>> Add initial device tree support for monaco-ac EVK board, based
>> on Qualcomm's monaco-ac (QCS8300-AC) variant SoC.
> 
> [...]
> 
> 
>> +&apps_rsc {
>> +	regulators-0 {
>> +		vreg_s4a: smps4 {
>> +			regulator-name = "vreg_s4a";
>> +			regulator-min-microvolt = <1800000>;
>> +			regulator-max-microvolt = <1800000>;
>> +			regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
>> +		};
>> +
>> +		vreg_s9a: smps9 {
>> +			regulator-name = "vreg_s9a";
>> +			regulator-min-microvolt = <1352000>;
>> +			regulator-max-microvolt = <1352000>;
>> +			regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
>> +		};
> 
> Since these are on a PMIC that is present on both full and lite SKUs,
> are these rails also connected on the other one (perhaps with a
> different voltage setting)? Currently they're completely absent

on the other variant the power-grid is little different and these rails
are not used by any of the consumers on HLOS/APPS side - hence not added.


> 
> Konrad

Thanks,
Umang




  reply	other threads:[~2026-05-04 19:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 17:05 [PATCH v4 0/4] arm64: dts: qcom: Introduce support for monaco-ac-evk Umang Chheda
2026-04-27 17:05 ` [PATCH v4 1/4] arm64: dts: qcom: monaco-evk: Extract common EVK hardware into shared dtsi Umang Chheda
2026-05-04 12:57   ` Konrad Dybcio
2026-05-04 18:28     ` Umang Chheda
2026-05-04 20:19     ` Krzysztof Kozlowski
2026-05-05 13:53       ` Umang Chheda
2026-05-06  9:18         ` Konrad Dybcio
2026-05-04 18:44   ` Dmitry Baryshkov
2026-05-04 19:26     ` Umang Chheda
2026-05-04 23:28       ` Dmitry Baryshkov
2026-05-05 13:47         ` Umang Chheda
2026-04-27 17:05 ` [PATCH v4 2/4] dt-bindings: arm: qcom: Add monaco-ac-evk support Umang Chheda
2026-04-27 17:05 ` [PATCH v4 3/4] arm64: dts: qcom: monaco: Add monaco-ac EVK board Umang Chheda
2026-05-04 12:53   ` Konrad Dybcio
2026-05-04 19:16     ` Umang Chheda [this message]
2026-05-06  9:17       ` Konrad Dybcio
2026-04-27 17:05 ` [PATCH v4 4/4] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine Umang Chheda

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=b734a099-b5db-4ff9-8b75-265e7f8194a1@oss.qualcomm.com \
    --to=umang.chheda@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=faruque.ansari@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richardcochran@gmail.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