[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <acc9ca84eadb1f78308f0c3e2b527406@fw-web.de>
Date: Mon, 12 May 2025 18:54:13 +0200
From: "Frank Wunderlich (linux)" <linux@...web.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: Vladimir Oltean <olteanv@...il.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Frank
Wunderlich <frank-w@...lic-files.de>, Arınç ÜNAL <arinc.unal@...nc9.com>, Landen Chao
<Landen.Chao@...iatek.com>, DENG Qingfang <dqfext@...il.com>, Sean Wang
<sean.wang@...iatek.com>, Daniel Golle <daniel@...rotopia.org>, Lorenzo
Bianconi <lorenzo@...nel.org>, Felix Fietkau <nbd@....name>,
netdev@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v1 08/14] arm64: dts: mediatek: mt7988: add basic
ethernet-nodes
Am 2025-05-11 18:38, schrieb Andrew Lunn:
>> + gmac0: mac@0 {
>> + compatible = "mediatek,eth-mac";
>> + reg = <0>;
>> + phy-mode = "internal";
>> +
>> + fixed-link {
>> + speed = <10000>;
>> + full-duplex;
>> + pause;
>> + };
>
> Does phy-mode internal and fixed-link used together make any sense?
> Please could you explain this.
Hi,
the fixed link is used to bring up the mac and switch cpu port up with
the right settings.
Of course we can hardcode it in driver for mt7988, but driver already
supports the generic
definition via devicetree. So imho adding driver code for whats already
supported via devicetree
does not make sense for me and devicetree shows the right settings
(speed,duplex,flow control) without digging in the driver code.
e.g. we could disable flow-control there (but it causes retransmitts)
without changing driver.
Imho this is the cleanest way without adding unnecessary driver code and
SoC conditions and
devicetree describes hardware ;).
regards Frank
Powered by blists - more mailing lists