On Wed, Mar 15, 2017 at 03:51:27PM +0200, Roger Quadros wrote:
> Since commit 3c293f4e08b5 ("net: phy: Trigger state machine on state change
> and not polling.")
> phy_suspend() doesn't get called as part of phy_stop() for PHYs using
> interrupts because the phy state machine is never triggered after a
> phy_stop().
>
> Explicitly trigger the PHY state machine so that it can
> see the new PHY state (HALTED) and suspend the PHY.
>
> Signed-off-by: Roger Quadros <rog...@ti.com>
Hi Roger
This seems sensible. It mirrors what phy_start() does.
Reviewed-by: Andrew Lunn <and...@lunn.ch>
It does however lead to a follow up question. Are there other places
phydev->state is changed and it is missing a phy_trigger_machine()?
Andrew
