On Tue, Sep 17, 2024 at 10:11:03AM +0100, Russell King (Oracle) wrote: > On Fri, Sep 13, 2024 at 10:40:21AM +0200, Oleksij Rempel wrote: > > 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: > > - `force-master`: Forces the PHY to operate as a master (clock source). > > - `force-slave`: Forces the PHY to operate as a slave (clock receiver). > > - `prefer-master`: Prefers the PHY to be master but allows negotiation. > > - `prefer-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. > > Does this provide the boot-time default that userspace is subsequently > allowed to change through ethtool, or does it provide a fixed > configuration? It provides the boot-time default. -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
