Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Umang Chheda <umang.chheda@oss.qualcomm.com>,
	konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, richardcochran@gmail.com,
	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,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: monaco-evk: Add Interface Plus Mezzanine
Date: Tue, 24 Feb 2026 07:55:17 +0100	[thread overview]
Message-ID: <2b3dddba-f5d4-4eb5-b2b1-52df919e02f9@kernel.org> (raw)
In-Reply-To: <w6pfpkgu2xypyl3xw7upxo4gkbkagmmh4mr7ky2itdmusah5xt@gh44xrzgmrtg>

On 24/02/2026 05:29, Bjorn Andersson wrote:
>>
>>>
>>> The recommendation that has been communicated is to based label, name
>>> and regulator-name of the schematics, but prefix the node name with
>>> regulator- to achieve sensible sort order.
>>>
>>>
>>> In fact naming these regulator-0v9, regulator-1v8, and regulator-3v3
>>> make the name useless. We further have plenty of designs where there are
>>> multiple regulator-1v8 and regulator-3v3.
>>
>> The regulator-name is to match schematics. Node name should follow DT
>> spec expectations to show the purpose of the node.
>>
> 
> And "purpose" here means "it's a regulator providing 0.9V"?

The purpose is regulator, so I was in general in favor of
regulator-[0-9] with the number being index. The convention/schema asks
now for a more specific suffix, which still is just a suffix to
differentiate multiple nodes.

> 
>>>
>>> I guess the preferred name, per the binding, is to not have multiple
>>> 3.3V regulators in your design?
>>
>> I don't see what you are proving here. The "vreg" middle name addon is
>> not differentiating multiple 3.3V regulators.
>> It changes nothing in the problem of this duplication.
>>
> 
> I agree on the "vreg" part being redundant, but you're telling us that
> all fixed regulators should be named "regulator-[0-9]v[0-9]".

Yes, I am fine with some meaningful suffixes.

> 
> Are you saying that "regulator-edp-3p3", "regulator-misc-3p3", and
> "regulator-nvme" (examples from x1-crd.dtsi), should all be named

First, I would not change existing names just to match the convention.
Really not.

Second, this is not the case here. I talk about patch here. The patch
did not need additional suffixes but added the "vreg" useless
suffix/middlefix.

Third, if these are controllable regulators for a new source code, then
they should follow the convention with optional suffix. Whether the
suffix is numerical or name, I don't care.

> "regulator-3v3"? Or is your feedback limited to those regulators that
> are trivially named in the schematics?



Best regards,
Krzysztof

  reply	other threads:[~2026-02-24  6:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-22 17:35 [PATCH v2 0/1] Introduce Monaco EVK Interface Plus Mezzanine Umang Chheda
2026-02-22 17:35 ` [PATCH v2 1/1] arm64: dts: qcom: monaco-evk: Add " Umang Chheda
2026-02-22 18:27   ` Dmitry Baryshkov
2026-02-23  9:47     ` Umang Chheda
2026-02-23  9:59       ` Konrad Dybcio
2026-02-23 10:36         ` Umang Chheda
2026-02-23 12:48           ` Konrad Dybcio
2026-02-23 18:56       ` Dmitry Baryshkov
2026-02-27  7:23         ` Umang Chheda
2026-02-23 13:12   ` Krzysztof Kozlowski
2026-02-23 15:12     ` Bjorn Andersson
2026-02-23 15:36       ` Krzysztof Kozlowski
2026-02-23 19:02         ` Dmitry Baryshkov
2026-02-23 20:37           ` Krzysztof Kozlowski
2026-02-23 22:09             ` Dmitry Baryshkov
2026-02-27  9:50               ` Umang Chheda
2026-02-27 10:38                 ` Krzysztof Kozlowski
2026-02-24  4:29         ` Bjorn Andersson
2026-02-24  6:55           ` Krzysztof Kozlowski [this message]
2026-02-27  9:46             ` 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=2b3dddba-f5d4-4eb5-b2b1-52df919e02f9@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@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