From: Logan Bristol <logan.bristol@utexas.edu>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: Josua Mayer <josua@solid-run.com>,
Wadim Egorov <w.egorov@phytec.de>,
linux@ew.tq-group.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH v2] arm64: dts: ti: k3-am64* Disable ethernet by default at SoC level
Date: Mon, 26 Aug 2024 16:17:07 -0500 [thread overview]
Message-ID: <6fa4f5e5-7f7b-495a-a95a-82d7b105d2d7@utexas.edu> (raw)
In-Reply-To: <4e884c6c-ec82-4229-a2a4-55da66cc284f@phytec.de>
Hi Daniel,
On 8/26/2024 12:29 AM, Daniel Schultz wrote:
> Hey Logan,
>
> my feedback is similar to Josua's.
>
> On 09.08.24 15:57, Logan Bristol wrote:
>> External interfaces should be disabled at the SoC DTSI level, since
>> the node is incomplete. Disable Ethernet switch and ports in SoC DTSI
>> and enable them in the board DTS. If the board DTS includes a SoM DTSI
>> that completes the node description, enable the Ethernet switch and ports
>> in SoM DTSI.
>>
>> Reflect this change in SoM DTSIs by removing ethernet port disable.
>>
>> Signed-off-by: Logan Bristol <logan.bristol@utexas.edu>
>> ---
>> Changes since v1:
>> - Enabled cpsw3g and cpsw_port1 in SoM DTSI instead of board DTS
>> if board DTS included SoM DTSI
>> ---
>> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 3 +++
>> arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi | 6 ++----
>> arch/arm64/boot/dts/ti/k3-am642-evm.dts | 3 +++
>> arch/arm64/boot/dts/ti/k3-am642-sk.dts | 3 +++
>> arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi | 6 ++----
>> arch/arm64/boot/dts/ti/k3-am642-tqma64xxl-mbax4xxl.dts | 6 ++----
>> 6 files changed, 15 insertions(+), 12 deletions(-)
>>
>> diff --git a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi b/arch/arm64/
>> boot/dts/ti/k3-am64-main.dtsi
>> index f8370dd03350..69c5af58b727 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am64-main.dtsi
>> @@ -677,6 +677,7 @@ cpsw3g: ethernet@8000000 {
>> assigned-clock-parents = <&k3_clks 13 9>;
>> clock-names = "fck";
>> power-domains = <&k3_pds 13 TI_SCI_PD_EXCLUSIVE>;
>> + status = "disabled";
>> dmas = <&main_pktdma 0xC500 15>,
>> <&main_pktdma 0xC501 15>,
>> @@ -701,6 +702,7 @@ cpsw_port1: port@1 {
>> phys = <&phy_gmii_sel 1>;
>> mac-address = [00 00 00 00 00 00];
>> ti,syscon-efuse = <&main_conf 0x200>;
>> + status = "disabled";
>> };
>> cpsw_port2: port@2 {
>> @@ -709,6 +711,7 @@ cpsw_port2: port@2 {
>> label = "port2";
>> phys = <&phy_gmii_sel 2>;
>> mac-address = [00 00 00 00 00 00];
>> + status = "disabled";
>> };
>> };
>> diff --git a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi b/arch/
>> arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> index ea7c58fb67e2..6bece2fb4e95 100644
>> --- a/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> +++ b/arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi
>> @@ -185,6 +185,7 @@ AM64X_IOPAD(0x0278, PIN_INPUT, 7) /* (C19)
>> EXTINTn.GPIO1_70 */
>> &cpsw3g {
>> pinctrl-names = "default";
>> pinctrl-0 = <&cpsw_rgmii1_pins_default>;
>> + status = "okay";
>> };
>> &cpsw3g_mdio {
>> @@ -208,10 +209,7 @@ cpsw3g_phy1: ethernet-phy@1 {
>> &cpsw_port1 {
>> phy-mode = "rgmii-rxid";
>> phy-handle = <&cpsw3g_phy1>;
> The connected phy is located on the SOM and should be enabled by default.
>> -};
>> -
>> -&cpsw_port2 {
>> - status = "disabled";
>> + status = "okay";
>> };
>
> This port is routed to the carrier-board. Please drop this node.
I replied similarly to Josua's comments, but if cpsw_port1 is to be
enabled and cpsw_port2 should be dropped from this DTSI, isn't that
shown in this diff?
Thank you,
Logan Bristol
next prev parent reply other threads:[~2024-08-26 21:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 13:57 Logan Bristol
2024-08-25 11:18 ` Josua Mayer
2024-08-26 21:12 ` Logan Bristol
2024-08-27 8:00 ` Josua Mayer
2024-08-26 5:29 ` Daniel Schultz
2024-08-26 21:17 ` Logan Bristol [this message]
2024-08-29 5:49 ` Daniel Schultz
2024-08-27 9:26 ` Matthias Schiffer
2024-08-28 18:41 ` Nishanth Menon
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=6fa4f5e5-7f7b-495a-a95a-82d7b105d2d7@utexas.edu \
--to=logan.bristol@utexas.edu \
--cc=conor+dt@kernel.org \
--cc=d.schultz@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=josua@solid-run.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@ew.tq-group.com \
--cc=nm@ti.com \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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
all inboxes | Powered by JetHome®