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]
Date:   Wed, 13 Feb 2019 14:40:18 +0100
From:   Marc Gonzalez <>
To:     Andrew Lunn <>,
        Niklas Cassel <>,
        Florian Fainelli <>
Cc:     Vinod Koul <>,
        David S Miller <>,,
        Bjorn Andersson <>,, Florian Fainelli <>,
        "Nori, Sekhar" <>,
        Peter Ujfalusi <>
Subject: Re: [PATCH] net: phy: at803x: disable delay only for RGMII mode

On 13/02/2019 14:29, Andrew Lunn wrote:

>> So we have these modes:
>> PHY_INTERFACE_MODE_RGMII: TX and RX delays disabled
>> PHY_INTERFACE_MODE_RGMII_ID: TX and RX delays enabled
>> PHY_INTERFACE_MODE_RGMII_RXID: RX delay enabled, TX delay disabled
>> PHY_INTERFACE_MODE_RGMII_TXID: TX delay enabled, RX delay disabled
>> What I don't like with this patch, is that if we specify phy-mode
>> PHY_INTERFACE_MODE_RGMII_TXID, this patch will enable TX delay,
>> but RX delay will not be explicitly set.
> That is not the behaviour we want. It is best to assume the device is
> in a random state, and correctly enable/disable all delays as
> requested. Only leave the hardware alone if PHY_INTERFACE_MODE_NA is
> used.

That's what my patch did:

But see Florian's remarks:


Powered by blists - more mailing lists