netdev - Re: [PATCH 0/2] net: phy: dp83822: Add support for line class driver configuration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6cf76d72-4747-46d2-a1f7-d2f1131491f7@lunn.ch>
Date: Mon, 10 Jul 2023 21:38:51 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vesa Jääskeläinen <vesa.jaaskelainen@...sala.com>
Cc: "David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Rob Herring <robh+dt@...nel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Heiner Kallweit <hkallweit1@...il.com>,
	Russell King <linux@...linux.org.uk>, Andrew Davis <afd@...com>,
	netdev@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] net: phy: dp83822: Add support for line class driver
 configuration

> Hi Andrew,
> 
> This is needed for configuration in link between DP83822 and Ethernet Switch
> chip.

What switch chip is it?

Most boards just connect the MACs together and don't have PHYs in the
middle. There are some boards which do have PHYs, but they don't need
any special mode.

> In the connection there there is no Ethernet cable at all but routes
> within the circuit boards but instead has capacitive coupling on routes.

So you also left out the magnetics?

> So the setting itself is related to specific circuit board design.

Agreed. So it is then valid to put it into DT, if it is actually
needed.

> MLT-3 is related to encoding used in the signals -- I suppose wiki page is
> good introduction reference:
> 
> https://en.wikipedia.org/wiki/MLT-3_encoding

MLT-3 is well defined. What i could not find is any reference to what
reduced MLT-3 is. If it is not part of any standard, why don't you
just hard code the PHY to always use MTL-3 which is defined as part of
802.3?

I get the feeling reduced MLT-3 is TI proprietary. As such, it should
default to MLT-3 as defined in 802.3 and there could then be an option
to enable this proprietary mode for anybody we wants to use it.

So before accepting any patches, we need a better understanding of
that reduced MLT-3 is and why you would want to use it.

     Andrew