Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Anusha Ajithkumar <tessolveupstream@gmail.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board
Date: Fri, 5 Dec 2025 10:58:56 +0530	[thread overview]
Message-ID: <9b0c7cac-3577-4190-883b-7de26790b8bc@gmail.com> (raw)
In-Reply-To: <CAO9ioeUVx_qf3no9aLgZ3OQQPQ7nG-2aTx8SHaEN5DUf02USWA@mail.gmail.com>



On 03-12-2025 02:36, Dmitry Baryshkov wrote:
> On Tue, 18 Nov 2025 at 12:16, <tessolveupstream@gmail.com> wrote:
>>
>>
>>
>> On 14-11-2025 01:38, Dmitry Baryshkov wrote:
>>> On Fri, Nov 07, 2025 at 04:27:35PM +0530, Sudarshan Shetty wrote:
> 
>>>> +
>>>> +&uart0 {
>>>> +    status = "okay";
>>>> +};
>>>> +
>>>> +&usb_1_hsphy {
>>>> +    vdd-supply = <&vreg_l5a>;
>>>> +    vdda-pll-supply = <&vreg_l12a>;
>>>> +    vdda-phy-dpdm-supply = <&vreg_l13a>;
>>>> +
>>>> +    status = "okay";
>>>> +};
>>>> +
>>>> +&usb_qmpphy {
>>>> +    vdda-phy-supply = <&vreg_l5a>;
>>>> +    vdda-pll-supply = <&vreg_l12a>;
>>>> +
>>>> +    status = "okay";
>>>> +};
>>>> +
>>>> +&usb_1 {
>>>> +    status = "okay";
>>>> +};
>>>> +
>>>> +&usb_1_dwc3 {
>>>> +    dr_mode = "host";
>>>> +};
>>>> +
>>>> +&usb_hsphy_2 {
>>>
>>> So, the labels are usb_1_hsphy, but usb_hsphy_2? That's not logical,
>>> please fix one of them. Then please fix the order of nodes here.
>>
>> The node names come directly from the included talos.dtsi, where they
>> are defined as usb_1_hsphy & usb_hsphy_2.
>> To avoid breaking inherited definitions, we kept the same labels
>> in our board DTS.
> 
> Please fix them in the base DT.
>

The inconsistent naming originates from talos.dtsi, which is 
outside the scope of this patch series. Modifying these labels 
in our board DTS would break the inherited node references 
from talos.dtsi. >> However, I will reorder the nodes so they appear in a logical and
>> consistent sequence.
> 
> This is a prerequisite, no questions.
> 


  reply	other threads:[~2025-12-05  5:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 10:57 [PATCH v6 0/2] Add Qualcomm Technologies, Inc. Talos EVK SMARC support Sudarshan Shetty
2025-11-07 10:57 ` [PATCH v6 1/2] dt-bindings: arm: qcom: talos-evk: Add QCS615 Talos EVK SMARC platform Sudarshan Shetty
2025-11-07 10:57 ` [PATCH v6 2/2] arm64: dts: qcom: talos-evk: Add support for QCS615 talos evk board Sudarshan Shetty
2025-11-13 20:08   ` Dmitry Baryshkov
2025-11-14  4:40     ` Bjorn Andersson
2025-11-18 10:16     ` tessolveupstream
2025-12-02 21:06       ` Dmitry Baryshkov
2025-12-05  5:28         ` Anusha Ajithkumar [this message]
2025-12-06  2:43           ` Dmitry Baryshkov
2025-12-15 13:22             ` tessolveupstream

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=9b0c7cac-3577-4190-883b-7de26790b8bc@gmail.com \
    --to=tessolveupstream@gmail.com \
    --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=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