mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Lobakin <alobakin@marvell.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Alexander Lobakin <alobakin@marvell.com>,
	<anthony.wong@canonical.com>,
	Igor Russkikh <irusskikh@marvell.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Nikita Danilov <ndanilov@marvell.com>,
	Mark Starovoytov <mstarovoitov@marvell.com>,
	"Dmitry Bezrukov" <dmitry.bezrukov@marvell.com>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: atlantic: Add support for firmware v4
Date: Tue, 7 Jul 2020 11:46:57 +0300	[thread overview]
Message-ID: <20200707084657.205-1-alobakin@marvell.com> (raw)
In-Reply-To: <20200707063830.15645-1-kai.heng.feng@canonical.com>

From:   Kai-Heng Feng <kai.heng.feng@canonical.com>
Date:   Tue,  7 Jul 2020 14:38:28 +0800

> We have a new ethernet card that is supported by the atlantic driver:
> 01:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02)
> 
> But the driver failed to probe the device:
> kernel: atlantic: Bad FW version detected: 400001e
> kernel: atlantic: probe of 0000:01:00.0 failed with error -95
> 
> As a pure guesswork, simply adding the firmware version to the driver

Please don't send "pure guessworks" to net-fixes tree. You should have
reported this as a bug to LKML and/or atlantic team, so we could issue
it.

> can make it function. Doing iperf3 as a smoketest doesn't show any
> abnormality either.
> 
> Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
> ---
>  drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c b/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c
> index 73c0f41df8d8..0b4cd1c0e022 100644
> --- a/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c
> +++ b/drivers/net/ethernet/aquantia/atlantic/hw_atl/hw_atl_utils.c
> @@ -46,6 +46,7 @@
>  #define HW_ATL_FW_VER_1X 0x01050006U
>  #define HW_ATL_FW_VER_2X 0x02000000U
>  #define HW_ATL_FW_VER_3X 0x03000000U
> +#define HW_ATL_FW_VER_4X 0x0400001EU
>  
>  #define FORCE_FLASHLESS 0
>  
> @@ -81,6 +82,9 @@ int hw_atl_utils_initfw(struct aq_hw_s *self, const struct aq_fw_ops **fw_ops)
>  	} else if (hw_atl_utils_ver_match(HW_ATL_FW_VER_3X,
>  					  self->fw_ver_actual) == 0) {
>  		*fw_ops = &aq_fw_2x_ops;
> +	} else if (hw_atl_utils_ver_match(HW_ATL_FW_VER_4X,
> +					  self->fw_ver_actual) == 0) {
> +		*fw_ops = &aq_fw_2x_ops;
>  	} else {
>  		aq_pr_err("Bad FW version detected: %x\n",
>  			  self->fw_ver_actual);
> -- 
> 2.17.1

  reply	other threads:[~2020-07-07  8:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07  6:38 Kai-Heng Feng
2020-07-07  8:46 ` Alexander Lobakin [this message]
2020-07-07 10:02   ` Kai-Heng Feng
2020-07-07 19:56   ` David Miller
2020-07-15 15:34     ` [EXT] " Igor Russkikh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200707084657.205-1-alobakin@marvell.com \
    --to=alobakin@marvell.com \
    --cc=anthony.wong@canonical.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.bezrukov@marvell.com \
    --cc=irusskikh@marvell.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mstarovoitov@marvell.com \
    --cc=ndanilov@marvell.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®