diff options
| author | hayeswang <hayeswang@realtek.com> | 2012-10-05 23:29:13 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-10-13 05:28:12 +0900 |
| commit | c43209e91508d1dbfa21203dc491ba67e0d30579 (patch) | |
| tree | ee509502c6f83094aef46426e7f9ebd65eacff08 /drivers/net/r8169.c | |
| parent | 11bd9becc350ab8adbb7f749c10536741d617d8a (diff) | |
| download | kernel_samsung_smdk4412-c43209e91508d1dbfa21203dc491ba67e0d30579.zip kernel_samsung_smdk4412-c43209e91508d1dbfa21203dc491ba67e0d30579.tar.gz kernel_samsung_smdk4412-c43209e91508d1dbfa21203dc491ba67e0d30579.tar.bz2 | |
r8169: increase the delay parameter of pm_schedule_suspend
commit 10953db8e1a278742ef7e64a3d1491802bcfa98b upstream
The link down would occur when reseting PHY. And it would take about 2 ~ 5
seconds from link down to link up. If the delay of pm_schedule_suspend is
not long enough, the device would enter runtime_suspend before link up.
After link up, the device would wake up and reset PHY again. Then, you
would find the driver keep in a loop of runtime_suspend and rumtime_resume.
Signed-off-by: Hayes Wang <hayeswang@realtek.com>
Acked-by: Francois Romieu <romieu@fr.zoreil.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/net/r8169.c')
| -rw-r--r-- | drivers/net/r8169.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/r8169.c b/drivers/net/r8169.c index 3fe4fd3..95305d3 100644 --- a/drivers/net/r8169.c +++ b/drivers/net/r8169.c @@ -1157,7 +1157,7 @@ static void __rtl8169_check_link_status(struct net_device *dev, netif_carrier_off(dev); netif_info(tp, ifdown, dev, "link down\n"); if (pm) - pm_schedule_suspend(&tp->pci_dev->dev, 100); + pm_schedule_suspend(&tp->pci_dev->dev, 5000); } spin_unlock_irqrestore(&tp->lock, flags); } |