public inbox for linux-arm-msm@vger.kernel.org
 help / color / mirror / Atom feed
From: Stanislav Zaikin <zstaseg@gmail.com>
To: Val Packett <val@packett.cool>, devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, andersson@kernel.org,
	konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS
Date: Mon, 16 Mar 2026 12:57:44 +0100	[thread overview]
Message-ID: <168615a6-615f-46cc-b126-4780fec34ecd@gmail.com> (raw)
In-Reply-To: <356110cc-699b-4a6d-973c-403d2e29630e@packett.cool>

On 3/16/26 5:05 AM, Val Packett wrote:
> On 3/5/26 6:39 AM, Stanislav Zaikin wrote:
>
>> Xiaomi 12 Lite 5G is a handset released in 2022
>>
>> This commit has the following features working:
>> - Display (with simple fb)
>> - Touchscreen
>> - UFS
>> - Power and volume buttons
>> - Pinctrl
>> - RPM Regulators
>> - Remoteprocs - wifi, bluetooth
>> - USB (Device Mode)
>> […]
>> +        vreg_l7b_2p96: ldo7 {
>> +            regulator-name = "vreg_l7b_2p96";
>> +            /* Constrained for UFS VCC, at least until UFS driver 
>> scales voltage */
>> +            regulator-min-microvolt = <2952000>;
>> +            regulator-max-microvolt = <2952000>;
>> +            regulator-initial-mode = <RPMH_REGULATOR_MODE_HPM>;
>> +        };
>> […]
>> +&ufs_mem_hc {
>> +    reset-gpios = <&tlmm 175 GPIO_ACTIVE_LOW>;
>> +
>> +    vcc-supply = <&vreg_l7b_2p96>;
>> +    vcc-max-microamp = <800000>;
>> +    /*
>> +     * Technically l9b enables an eLDO (supplied by s1b) which then 
>> powers
>> +     * VCCQ2 of the UFS.
>> +     */
>> +    vccq-supply = <&vreg_l9b_1p2>;
>> +    vccq-max-microamp = <900000>;
>
> If this device has UFS 3.x flash, which it most likely does, the 
> copy-pasted eLDO comment does not apply.. and VCC range is 2.4V-2.7V, 
> 2.95 is overvoltage! 

Hello Val,

Thank you for the review.

Though you're right that this comment is a copy-paste, taoyao has ufs2. 
This is the explaining comment from the downstream sources:

> /*
> * Yupik target supports both UFS2.2 & UFS3.1, here
> * vccq2 is supplied via eLDO, and that is controlled via
> * L9B which supports a max voltage of 1.2V, but eLDO would
> * supply 1.8V. and same L9B acts as vccq voltage for UFS3.1
> * devices.
> * Here L9B can max support for 1.2V but UFS GKI driver code
> * votes for 1.8V, which is leading to failure from pmic
> * regulator.
> *
> * Now since vccq and control of eLDO are common that is L9B
> * we can use vccq vote as control of eLDO for vccq2.
> * Hence vccq entries shall be used for both type of UFS
> * devices only. And vccq entries should not be changed/removed
> * for any design alteration.
> */

So I thought it's better to keep a small comment regarding eLDO.

> If it's actually UFS 2 after all, it would be better to rename the 
> property to vccq2-supply.
Could you elaborate please? Do you mean l9b?


  reply	other threads:[~2026-03-16 11:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-05  9:39 [PATCH v4 0/2] Add Xiaomi 12 Lite 5G (taoyao) device tree Stanislav Zaikin
2026-03-05  9:39 ` [PATCH v4 1/2] dt-bindings: arm: qcom: Add SM7325 Xiaomi 12 Lite 5G (taoyao) Stanislav Zaikin
2026-03-05  9:39 ` [PATCH v4 2/2] arm64: dts: qcom: Add Xiaomi 12 Lite 5G (taoyao) DTS Stanislav Zaikin
2026-03-05 10:27   ` Konrad Dybcio
2026-03-16  4:05   ` Val Packett
2026-03-16 11:57     ` Stanislav Zaikin [this message]
2026-03-16 20:47       ` Val Packett
2026-03-18  8:22         ` Stanislav Zaikin
2026-03-21  7:36   ` Val Packett
2026-03-23  8:04     ` Stanislav Zaikin
2026-03-23 20:49       ` Val Packett
2026-03-24  8:07         ` Stanislav Zaikin

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=168615a6-615f-46cc-b126-4780fec34ecd@gmail.com \
    --to=zstaseg@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=val@packett.cool \
    /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