netdev - Re: [PATCH v2 0/2] ARM: imx6ul-14x14-evk: Fix suspend over nfs by phy

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Thu, 01 Jun 2017 15:03:20 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     leonard.crestez@....com
Cc:     f.fainelli@...il.com, andrew@...n.ch, shawnguo@...nel.org,
        fugang.duan@....com, johan@...nel.org,
        alexandre.belloni@...e-electrons.com, p.zabel@...gutronix.de,
        fabio.estevam@....com, netdev@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] ARM: imx6ul-14x14-evk: Fix suspend over nfs by
 phy

From: Leonard Crestez <leonard.crestez@....com>
Date: Wed, 31 May 2017 13:29:28 +0300

> Right now attempting doing suspend/resume while root is mounted over NFS
> hangs on imx6ul-14x14-evk. This is happening because ksz8081 phy fixups are
> lost on resume.
> 
> Fix this by using equivalent devicetree properties instead of a phy fixup
> and handling those properties on resume in the micrel driver.
> 
> In theory it might now be possible to remove the phy fixup from mach-imx6ul
> entirely but it is possible that this would break other imx6ul boards which
> use the same phy. The solution would be to patch their dts but it's not
> clear how to identify affected boards.
> 
> This code is shared with imx6ull-14x14-evk but 6ull suspend needs an
> unrelated patch: https://lkml.org/lkml/2017/5/30/584
> 
> This is something of a corner case so there is no CC: stable.
> 
> Changes since v1: https://lkml.org/lkml/2017/5/30/672 
>  * Split a kszphy_config_reset function for stuff shared between
> config_init and resume. Calling config_init directly could be an option but
> on some HW variants it does extra stuff like parsing devicetree options.
> That would not be appropriate for resume code.

Series applied.