From: Ajit Singh <blfizzyy@gmail.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.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 v4 3/3] arm64: dts: qcom: Add Vicharak Axon Mini
Date: Thu, 11 Jun 2026 15:05:41 +0530 [thread overview]
Message-ID: <aip7U3GXEjDEQLq0@page.local> (raw)
In-Reply-To: <cc48189f-421c-4d04-945a-5905fa52357c@oss.qualcomm.com>
On Wed, Jun 10, 2026 at 03:01:48PM +0530, Konrad Dybcio wrote:
> On 6/7/26 1:36 PM, Ajit Singh wrote:
Thanks for review, Konrad!
> > Add DTS for the Vicharak Axon Mini board based on the Qualcomm
> > QCS6490 SoC.
> >
> > This adds debug UART, eMMC, UFS, SDIO WLAN, USB 2.0 host, PCIe
> > support along with regulators.
> >
> > The UFS ICE block is kept disabled because enabling it currently causes
> > an SError during qcom_ice_create() on this board. UFS works without ICE.
> >
> > Signed-off-by: Ajit Singh <blfizzyy@gmail.com>
> > ---
>
> [...]
>
> > + vreg_l16b_1p1: ldo16 {
> > + regulator-name = "vreg_l16b_1p1";
> > + regulator-min-microvolt = <1100000>;
> > + regulator-max-microvolt = <1300000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > +
> > + regulator-always-on;
> > + regulator-boot-on;
> > + };
> > +
> > + vreg_l17b_1p7: ldo17 {
> > + regulator-name = "vreg_l17b_1p7";
> > + regulator-min-microvolt = <1700000>;
> > + regulator-max-microvolt = <1900000>;
> > + regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
> > +
> > + regulator-always-on;
> > + regulator-boot-on;
> > + };
>
> Any reason for these two to be always-on?
vreg_l17b_1p7 supplies VDDD of the ES8388 audio codec, and vreg_l16b_1p1
supplies the CH7218A eDP-to-HDMI bridge. Both consumers are not described in
this initial DTS and will be added in follow-up patches.
So yes, these do not need to be always-on in this patch. I will drop
regulator-always-on and regulator-boot-on for both.
>
> [...]
>
> > +&usb_2 {
> > + /* Routed to an onboard USB hub for two USB-A host ports. */
> > + dr_mode = "host";
>
> Do they need to be powered/power sequenced in any way?
> see drivers/usb/misc/onboard_usb_dev.c and e.g. qcs6490-rb3gen2.dts
> -> usb5e3,610
Thanks, I checked it. For Axon-mini USB hub is powered from the shared
VCC_3V3 rail, which is enabled by board hardware. There is no hub-specific
reset so I think no power sequencing is required here.
>
> Konrad
Ajit
prev parent reply other threads:[~2026-06-11 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 11:36 [PATCH v4 0/3] arm64: dts: qcom: Add Vicharak Axon Mini Ajit Singh
2026-06-07 11:36 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add prefix for Vicharak Ajit Singh
2026-06-07 11:36 ` [PATCH v4 2/3] dt-bindings: arm: qcom: Add Vicharak Axon Mini Ajit Singh
2026-06-07 11:36 ` [PATCH v4 3/3] arm64: dts: " Ajit Singh
2026-06-07 18:56 ` Dmitry Baryshkov
2026-06-10 12:58 ` Konrad Dybcio
2026-06-10 13:01 ` Konrad Dybcio
2026-06-11 9:35 ` Ajit Singh [this message]
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=aip7U3GXEjDEQLq0@page.local \
--to=blfizzyy@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.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