Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Umang Chheda <umang.chheda@oss.qualcomm.com>,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	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
Subject: Re: [PATCH v2 1/1] arm64: dts: qcom: monaco-evk: Add Interface Plus Mezzanine
Date: Fri, 27 Feb 2026 11:38:02 +0100	[thread overview]
Message-ID: <58e3bc9c-28d3-41be-8c7a-4b858ab44e2b@kernel.org> (raw)
In-Reply-To: <1b34bdcf-79fa-45c1-8ca8-8610c15741af@oss.qualcomm.com>

On 27/02/2026 10:50, Umang Chheda wrote:
> Hello Krzysztof,
> 
> On 2/24/2026 3:39 AM, Dmitry Baryshkov wrote:
>> On Mon, Feb 23, 2026 at 09:37:53PM +0100, Krzysztof Kozlowski wrote:
>>> On 23/02/2026 20:02, Dmitry Baryshkov wrote:
>>>>>> So I presume what you're saying is that we should at most declare one
>>>>>> level of non-controlled fixed regulators?
>>>>> In general, non-controller fixed regulators should not be there at all,
>>>>> except when they serve certain purpose, like fulfill the binding
>>>>> requirement. It's their only point.
>>>>>
>>>>> And a chain of:
>>>>>
>>>>> A -> B -> C -> device
>>>>>
>>>>> is completely redundant if all A+B+C are non-controlled.
>>>> I think that came from me. I don't consider that to be completely
>>>> redundant. It helps in reviews and in some understanding of the board
>>>> logic. I'm not asking to implement all the intermediate regulators, but
>>>> to implement the meaningful relationship between end-user regulators.
>>> These are not end-user regulators. These are fixed things which no one
>>> touches and no one needs. There is no single purpose for user-space to
>>> see them.
>>>
>>> Why do you not insist on defining all of such external oscilators, rest
>>> of regulators, all possible little ICs?
>> So, where is the boundary from you point of view? Do we define fixed
>> regulators powering DRM bridges / USB hubs and other similar devices?
>> Or do we do it only if the bindings require us to do it?
> 
> Can you help share your point of view on the above query from Dmitry ? In this case to adhere to  bindings requirements

I already replied in this thread. No point to repeat in multiple places.

Best regards,
Krzysztof

  reply	other threads:[~2026-02-27 10:38 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 [this message]
2026-02-24  4:29         ` Bjorn Andersson
2026-02-24  6:55           ` Krzysztof Kozlowski
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=58e3bc9c-28d3-41be-8c7a-4b858ab44e2b@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