netdev - Re: dp83867: Why does ti,fifo-depth set only TX, and why is it mandatory?

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]

Date:   Sat, 23 Nov 2019 23:00:01 +0200
From:   Adrian Bunk <bunk@...nel.org>
To:     Dan Murphy <dmurphy@...com>
Cc:     Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        Heiner Kallweit <hkallweit1@...il.com>, netdev@...r.kernel.org
Subject: Re: dp83867: Why does ti,fifo-depth set only TX, and why is it
 mandatory?

On Thu, Nov 21, 2019 at 02:24:01PM -0600, Dan Murphy wrote:
> Adrian

Hi Dan,

>...
> OK the HW team said that FIFO depth is no longer a mandatory field to be
> written for either RGMII or SGMII.
> 
> So my suggestion here is that we deprecate, but support in the driver, the
> ti-fifo-depth, and add the already documented
> 
> rx-fifo-depth and tx-fifo-depth as optional DT entries.
> 
> So I can change the driver and DT docs and test the RGMII device as above as
> long as we are in agreement

sounds good to me.

> Dan

Thanks
Adrian