From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
James Hershaw <james.hershaw@corigine.com>,
Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/nfp: changes to link status reporting
Date: Wed, 21 Jun 2023 15:42:38 +0100 [thread overview]
Message-ID: <1c544eeb-5785-1619-3fa3-3ccc8cdfafac@amd.com> (raw)
In-Reply-To: <20230615032740.1247408-1-chaoyong.he@corigine.com>
On 6/15/2023 4:27 AM, Chaoyong He wrote:
> From: James Hershaw <james.hershaw@corigine.com>
>
> The NFP PMD driver retrieves the linkspeed by reading the
> NFP_NET_CFG_STS_LINK register. This register is not set by all versions
> of the firmware. Changes in this patch include:
>
> Addition of listener function to deal with control messages of type
> NFP_FLOWER_CMSG_TYPE_PORT_MOD being received by the PMD. This ensures
> that the up/down status of the port is updated when a version of
> firmware is being used that does not write the link status to the
> NFP_NET_CFG_STS register.
>
> Update the nfp_flower_repr_link_update() function to preferably read the
> linkspeed from the port table, while keeping the old lookup method as a
> fallback in case that is not supported.
>
> Signed-off-by: James Hershaw <james.hershaw@corigine.com>
> Reviewed-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-21 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 3:27 Chaoyong He
2023-06-21 14:42 ` Ferruh Yigit [this message]
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=1c544eeb-5785-1619-3fa3-3ccc8cdfafac@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=james.hershaw@corigine.com \
--cc=long.wu@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
/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;
as well as URLs for NNTP newsgroup(s).