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:
 <CO1PR11MB4771BFEB270D7F3210744C21E2722@CO1PR11MB4771.namprd11.prod.outlook.com>
Date: Fri, 4 Oct 2024 10:33:36 +0000
From: <Divya.Koppera@...rochip.com>
To: <o.rempel@...gutronix.de>, <andrew@...n.ch>, <hkallweit1@...il.com>,
	<davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
	<pabeni@...hat.com>, <robh@...nel.org>, <krzk+dt@...nel.org>,
	<conor+dt@...nel.org>, <f.fainelli@...il.com>
CC: <florian.fainelli@...adcom.com>, <kernel@...gutronix.de>,
	<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>,
	<linux@...linux.org.uk>, <devicetree@...r.kernel.org>
Subject: RE: [PATCH net-next v5 1/2] dt-bindings: net: ethernet-phy: Add
 timing-role role property for ethernet PHYs

> This patch introduces a new `timing-role` property in the device tree bindings
> for configuring the master/slave role of PHYs. This is essential for scenarios
> where hardware strap pins are unavailable or incorrectly configured.
> 
> The `timing-role` property supports the following values:
> - `forced-master`: Forces the PHY to operate as a master (clock source).
> - `forced-slave`: Forces the PHY to operate as a slave (clock receiver).
> - `preferred-master`: Prefers the PHY to be master but allows negotiation.
> - `preferred-slave`: Prefers the PHY to be slave but allows negotiation.
> 
> The terms "master" and "slave" are retained in this context to align with the
> IEEE 802.3 standards, where they are used to describe the roles of PHY devices
> in managing clock signals for data transmission. In particular, the terms are
> used in specifications for 1000Base-T and MultiGBASE-T PHYs, among others.
> Although there is an effort to adopt more inclusive terminology, replacing
> these terms could create discrepancies between the Linux kernel and the
> established standards, documentation, and existing hardware interfaces.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
> Reviewed-by: Rob Herring (Arm) <robh@...nel.org>
> Reviewed-by: Florian Fainelli <florian.fainelli@...adcom.com>
> ---
> changes v5:
> - s/force-/forced-(/g
> - s/prefer-/preferred-/g
> changes v4:
> - add "Reviewed-by: Rob Herring (Arm) <robh@...nel.org>"
> changes v3:
> - rename "master-slave" to "timing-role"
> changes v2:
> - use string property instead of multiple flags
> 
> Signed-off-by: Oleksij Rempel <o.rempel@...gutronix.de>
> ---

Reviewed-by: Divya Koppera <divya.koppera@...rochip.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ