Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3920256pxj; Mon, 21 Jun 2021 09:23:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz3mh8C/aVEJPFg7NkVeS98/TeVLs+wYTyVeCkMHatUnHIDz9p077pbDO7+i+JLN6bA2u1z X-Received: by 2002:a05:6402:4301:: with SMTP id m1mr22854569edc.303.1624292602826; Mon, 21 Jun 2021 09:23:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624292602; cv=none; d=google.com; s=arc-20160816; b=qxAvT5cvXeVXHykV9AVnbCb1gE/q9Ij52tlmCBcbQeFMOtvNp8/FGka8ir10Ol5tiw 8uB3vt8KAqZOoib5Zqtugg5C7Yr1ilSL3y0d7xDixCuzkW76YIBw84YGwuz9UylLV07U wuxDXccUciPGb2fu3wdFvekLBJmWItEuIijdoeZnw1mvYkAubodpAZAayNXVXRGE+Z5a aEmlzn/RFxRB1RTIyq4KCloLLuFj0ULnyQOH+5ezhD1OeZGNENqmA2lYeSBdaG2w5PgQ QC6mpAlsBlAXh7DhP1gJNww4kMwSTtJpFPQJciagZV0sfpTUURaDZbmkqdFEpafvnfwq ezeg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=xAkW1KD3xrqa5lryLhnvT6fAQfvj7MAQnxZr3bnOyt0=; b=yPeBm0o6MGqD9tSlBBLwLUhkp1DPzfMZLQ2o9/BNddaVOkvfLPlFjrea8OvkJyZZc4 AW6r185RN8c/OPnMlic+huSlTj87UaLAVtGVivA52am26CCeXb+u1B//x4YoJ7KrmGvE 45iW36BAmsMbjlMRdIENEiwWmPl2G7crjhMHEAThQwFXAOUIU8NIobO7dkMoW5QDtA5L NSFgKGCE6fokAR7WEf7wQ9+ZWplsv/ROqtvJAF2KID20CQNAmPrZFAQ3GknIPRl6Vm3S LYnTHDcGQv2DGEbEKj8bddDEyLhvkS63CHefa8oL/H6FJgh31Im4HceSG68LEbncaGux IXDg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=rPa9cETW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i17si15551510edb.326.2021.06.21.09.23.00; Mon, 21 Jun 2021 09:23:22 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=rPa9cETW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230180AbhFUQXr (ORCPT + 99 others); Mon, 21 Jun 2021 12:23:47 -0400 Received: from mail.kernel.org ([198.145.29.99]:42284 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231873AbhFUQWR (ORCPT ); Mon, 21 Jun 2021 12:22:17 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 0EB596115B; Mon, 21 Jun 2021 16:19:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1624292390; bh=56PFYTutgjLtcWse1kCfWxGkP6kS+8Cdp0xr/smlXMY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=rPa9cETWeq8eg2KSKfHFD4JMn5SCJ+gFLCkQcKasLdUGJicjEGzWR/uxA8fH2qhix g3SIbdn1QW0Z2B/eAtHjURZF5Vy6WBh5igkqvLzH1Go4HWjWWe+TrX2zKOkaxaC0GN XvM8p9cawRkDf9pToLOsnAeMF9l0MpDYWW0vE8aY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Michael Chan , "David S. Miller" , Sasha Levin Subject: [PATCH 5.4 39/90] bnxt_en: Rediscover PHY capabilities after firmware reset Date: Mon, 21 Jun 2021 18:15:14 +0200 Message-Id: <20210621154905.445477126@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210621154904.159672728@linuxfoundation.org> References: <20210621154904.159672728@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Michael Chan [ Upstream commit 0afd6a4e8028cc487c240b6cfe04094e45a306e4 ] There is a missing bnxt_probe_phy() call in bnxt_fw_init_one() to rediscover the PHY capabilities after a firmware reset. This can cause some PHY related functionalities to fail after a firmware reset. For example, in multi-host, the ability for any host to configure the PHY settings may be lost after a firmware reset. Fixes: ec5d31e3c15d ("bnxt_en: Handle firmware reset status during IF_UP.") Signed-off-by: Michael Chan Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/broadcom/bnxt/bnxt.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c index 00ae7a9a42bf..f983d03da1e4 100644 --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c @@ -10610,6 +10610,8 @@ static void bnxt_fw_init_one_p3(struct bnxt *bp) bnxt_hwrm_coal_params_qcaps(bp); } +static int bnxt_probe_phy(struct bnxt *bp, bool fw_dflt); + static int bnxt_fw_init_one(struct bnxt *bp) { int rc; @@ -10624,6 +10626,9 @@ static int bnxt_fw_init_one(struct bnxt *bp) netdev_err(bp->dev, "Firmware init phase 2 failed\n"); return rc; } + rc = bnxt_probe_phy(bp, false); + if (rc) + return rc; rc = bnxt_approve_mac(bp, bp->dev->dev_addr, false); if (rc) return rc; -- 2.30.2