From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Umang Chheda <umang.chheda@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, mohd.anwar@oss.qualcomm.com,
krishna.chundru@oss.qualcomm.com,
monish.chunara@oss.qualcomm.com,
Faruque Ansari <faruque.ansari@oss.qualcomm.com>
Subject: Re: [PATCH v5 2/3] arm64: dts: qcom: monaco: Add monaco-ac EVK board
Date: Fri, 10 Jul 2026 14:49:44 +0200 [thread overview]
Message-ID: <c8d7b622-b36b-4ae9-b3ab-461ce87ac727@oss.qualcomm.com> (raw)
In-Reply-To: <20260626111301.3479559-3-umang.chheda@oss.qualcomm.com>
On 6/26/26 1:13 PM, Umang Chheda wrote:
> Add initial device tree support for monaco-ac EVK board,
> based on Qualcomm's monaco-ac (QCS8300-AC) variant SoC.
[...]
> + regulator-allowed-modes = <RPMH_REGULATOR_MODE_HPM>;
> + };
> + vreg_s4a: smps4 {
nit: Ideally there would be a \n above here, but otherwise this
is identical to the existing evk dt.. I would prefer if that was
a common file but if others prefer not to..
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-07-10 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 11:12 [PATCH v5 0/2] arm64: dts: qcom: Introduce support for Monaco-ac-sku Evaluation Kit Umang Chheda
2026-06-26 11:12 ` [PATCH v5 1/3] dt-bindings: arm: qcom: Add monaco-ac-evk support Umang Chheda
2026-06-26 11:13 ` [PATCH v5 2/3] arm64: dts: qcom: monaco: Add monaco-ac EVK board Umang Chheda
2026-06-26 11:42 ` sashiko-bot
2026-07-10 12:49 ` Konrad Dybcio [this message]
2026-06-26 11:13 ` [PATCH v5 3/3] arm64: dts: qcom: monaco-ac-evk: Add IFP mezzanine Umang Chheda
2026-07-10 12:50 ` Konrad Dybcio
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=c8d7b622-b36b-4ae9-b3ab-461ce87ac727@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=faruque.ansari@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mohd.anwar@oss.qualcomm.com \
--cc=monish.chunara@oss.qualcomm.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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