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:   Tue, 23 Apr 2019 18:18:35 +0300
From:   Sergei Shtylyov <>
To:     Simon Horman <>,
        David Miller <>
Cc:     Magnus Damm <>,,, Andrew Lunn <>
Subject: Re: [PATCH net-next v3] ravb: Avoid unsupported internal delay mode
 for R-Car E3/D3

On 04/23/2019 04:01 PM, Simon Horman wrote:

> According to the R-Car Gen3 Hardware Manual Rev 1.50 of Nov 30, 2018, the
> TX clock internal delay mode isn't supported on R-Car E3 (r8a77990) or D3
> (r8a77995). And by extension it is also not supported by RZ/G2E (r9a774c0).
> This matches all ES versions of the affected SoCs as it is
> not clear if this problem will be resolved in newer chips.
> This can be revisited, as necessary.
> This patch does not error-out if PHY_INTERFACE_MODE_RGMII_ID or
> PHY_INTERFACE_MODE_RGMII_TXID are used on SoCs where TX clock delay
> mode is not supported as there is a risk of introducing a regression
> when used in conjunction with older DT blobs present in the field.
> Rather, a warning is logged in such cases.
> Based on work by Kazuya Mizuguchi.
> Signed-off-by: Simon Horman <>
> Reviewed-by: Andrew Lunn <>

Reviewed-by: Sergei Shtylyov <>


MBR, Seregi

Powered by blists - more mailing lists