From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chintan Vankar <c-vankar@ti.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
s-vadapalli@ti.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am625-sk: Add bootph-all property in phy_gmii_sel node
Date: Mon, 29 Apr 2024 09:26:16 +0200 [thread overview]
Message-ID: <44e430f6-1bad-4d0c-a908-823b83625db5@kernel.org> (raw)
In-Reply-To: <f400160f-1caf-44f6-a1b2-3a538eebd63c@ti.com>
On 29/04/2024 08:58, Chintan Vankar wrote:
>
>
> On 29/04/24 12:12, Chintan Vankar wrote:
>>
>>
>> On 29/04/24 12:08, Krzysztof Kozlowski wrote:
>>> Are you sure you kept proper ordering of nodes or just stuffed this to
>>> the end?
>>
>> Yes, I added this node at the end.
>
> Is it okay to add it at the end or it should be defined after "cpsw3g"
> node ?
What is the ordering for this subarch? What does the DTS coding style say?
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Chintan Vankar <c-vankar@ti.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, Tero Kristo <kristo@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>,
s-vadapalli@ti.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am625-sk: Add bootph-all property in phy_gmii_sel node
Date: Mon, 29 Apr 2024 09:26:16 +0200 [thread overview]
Message-ID: <44e430f6-1bad-4d0c-a908-823b83625db5@kernel.org> (raw)
In-Reply-To: <f400160f-1caf-44f6-a1b2-3a538eebd63c@ti.com>
On 29/04/2024 08:58, Chintan Vankar wrote:
>
>
> On 29/04/24 12:12, Chintan Vankar wrote:
>>
>>
>> On 29/04/24 12:08, Krzysztof Kozlowski wrote:
>>> Are you sure you kept proper ordering of nodes or just stuffed this to
>>> the end?
>>
>> Yes, I added this node at the end.
>
> Is it okay to add it at the end or it should be defined after "cpsw3g"
> node ?
What is the ordering for this subarch? What does the DTS coding style say?
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-04-29 7:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 6:16 [PATCH v2] arm64: dts: ti: k3-am625-sk: Add bootph-all property in phy_gmii_sel node Chintan Vankar
2024-04-29 6:16 ` Chintan Vankar
2024-04-29 6:38 ` Krzysztof Kozlowski
2024-04-29 6:38 ` Krzysztof Kozlowski
2024-04-29 6:42 ` Chintan Vankar
2024-04-29 6:42 ` Chintan Vankar
2024-04-29 6:58 ` Chintan Vankar
2024-04-29 6:58 ` Chintan Vankar
2024-04-29 7:26 ` Krzysztof Kozlowski [this message]
2024-04-29 7:26 ` Krzysztof Kozlowski
2024-04-29 9:38 ` Chintan Vankar
2024-04-29 9:38 ` Chintan Vankar
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=44e430f6-1bad-4d0c-a908-823b83625db5@kernel.org \
--to=krzk@kernel.org \
--cc=c-vankar@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.