From: Kalesh AP <kalesh.purayil@emulex.com>
Date: Tue, 20 Jan 2015 08:51:47 +0000 (-0500)
Subject: be2net: issue function reset cmd in resume path
X-Git-Tag: v4.0-rc1~133^2~157^2~2
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=9a6d73d9f297fd1bf7514bf2b1dc2f4b48c638b9;p=platform%2Fkernel%2Flinux-exynos.git

be2net: issue function reset cmd in resume path

The Lancer FW is picky about requiring a function reset FW cmd as a part
of the initialization sequence.

Signed-off-by: Kalesh AP <kalesh.purayil@emulex.com>
Signed-off-by: Sathya Perla <sathya.perla@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
---

diff --git a/drivers/net/ethernet/emulex/benet/be_main.c b/drivers/net/ethernet/emulex/benet/be_main.c
index f5ac35c..0b0482b 100644
--- a/drivers/net/ethernet/emulex/benet/be_main.c
+++ b/drivers/net/ethernet/emulex/benet/be_main.c
@@ -5071,6 +5071,10 @@ static int be_resume(struct pci_dev *pdev)
 	if (status)
 		return status;
 
+	status = be_cmd_reset_function(adapter);
+	if (status)
+		return status;
+
 	be_intr_set(adapter, true);
 	/* tell fw we're ready to fire cmds */
 	status = be_cmd_fw_init(adapter);