RE: [PATCH v4 3/5] net: asix: Fix AX88772x resume failures

[ASIX_Allan [Office]]

Dear Jon,

Thanks a lot for your reminding. I will submit a new driver patch soon.

---
Best regards,
Allan Chou


-Original Message-
From: Jon Hunter [mailto:jonath...@nvidia.com] 
Sent: Wednesday, November 30, 2016 4:08 PM
To: al...@asix.com.tw; fre...@asix.com.tw; dean_jenk...@mentor.com;
mark_cra...@mentor.com; da...@davemloft.net; robert.f...@collabora.com;
ivec...@redhat.com; john.stu...@linaro.org; vpala...@chromium.org;
step...@networkplumber.org; grund...@chromium.org; changch...@gmail.com;
and...@lunn.ch; trem...@gmail.com; colin.k...@canonical.com;
linux-...@vger.kernel.org; netdev@vger.kernel.org;
linux-ker...@vger.kernel.org; vpala...@google.com
Subject: Re: [PATCH v4 3/5] net: asix: Fix AX88772x resume failures

Hi Allan,

On 30/11/16 03:03, ASIX_Allan [Office] wrote:
> The change fixes AX88772x resume failure by
> - Restore incorrect AX88772A PHY registers when resetting
> - Need to stop MAC operation when suspending
> - Need to restart MII when restoring PHY
> 
> Signed-off-by: Allan Chou <al...@asix.com.tw>
> Signed-off-by: Robert Foss <robert.f...@collabora.com>
> Tested-by: Robert Foss <robert.f...@collabora.com>
> Tested-by: Jon Hunter <jonath...@nvidia.com>
> Tested-by: Allan Chou <al...@asix.com.tw>

V3 of this patch is already in the current mainline branch. So you need to
send a patch on top of V3 (or v4.9-rc7) to get this fixed. Also you should
highlight the fact that this is a fix needed for v4.9.

Cheers
Jon

--
nvpublic

Re: [PATCH v4 3/5] net: asix: Fix AX88772x resume failures

[Jon Hunter]

Hi Allan,

On 30/11/16 03:03, ASIX_Allan [Office] wrote:
> The change fixes AX88772x resume failure by
> - Restore incorrect AX88772A PHY registers when resetting
> - Need to stop MAC operation when suspending
> - Need to restart MII when restoring PHY
> 
> Signed-off-by: Allan Chou 
> Signed-off-by: Robert Foss 
> Tested-by: Robert Foss 
> Tested-by: Jon Hunter 
> Tested-by: Allan Chou 

V3 of this patch is already in the current mainline branch. So you need
to send a patch on top of V3 (or v4.9-rc7) to get this fixed. Also you
should highlight the fact that this is a fix needed for v4.9.

Cheers
Jon

-- 
nvpublic