netdev - Re: [PATCH net-next v11 0/5] RGMII Internal delay common property

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20200625.160545.16023142112288844.davem@davemloft.net>
Date:   Thu, 25 Jun 2020 16:05:45 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dmurphy@...com
Cc:     andrew@...n.ch, f.fainelli@...il.com, hkallweit1@...il.com,
        robh@...nel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next v11 0/5] RGMII Internal delay common property

From: Dan Murphy <dmurphy@...com>
Date: Wed, 24 Jun 2020 07:16:00 -0500

> The RGMII internal delay is a common setting found in most RGMII capable PHY
> devices.  It was found that many vendor specific device tree properties exist
> to do the same function. This creates a common property to be used for PHY's
> that have internal delays for the Rx and Tx paths.
> 
> If the internal delay is tunable then the caller needs to pass the internal
> delay array and the return will be the index in the array that was found in
> the firmware node.
> 
> If the internal delay is fixed then the caller only needs to indicate which
> delay to return.  There is no need for a fixed delay to add device properties
> since the value is not configurable. Per the ethernet-controller.yaml the
> interface type indicates that the PHY should provide the delay.
> 
> This series contains examples of both a configurable delay and a fixed delay.

Series applied, thank you.