From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: netdev@vger.kernel.org
Cc: oss-drivers@netronome.com, Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net v2 0/3] nfp: wait more carefully for card init
Date: Wed, 13 Sep 2017 10:15:57 -0700 [thread overview]
Message-ID: <20170913171600.31049-1-jakub.kicinski@netronome.com> (raw)
Hi!
The first patch is a small fix for flower offload, we need a whitelist
of supported matches, otherwise the unsupported ones will be ignored.
The second and the third patch are adding wait/polling to the probe path.
We had reports of driver failing probe because it couldn't find the
control process (NSP) on the card. Turns out the NSP will only announce
its existence after it's fully initialized. Until now we assumed it
will be reachable, just not processing commands (hence we wait for
a NOOP command to execute successfully).
v2:
- fix a bad merge which resulted in a build warning and retest.
Jakub Kicinski (2):
nfp: wait for board state before talking to the NSP
nfp: wait for the NSP resource to appear on boot
Pieter Jansen van Vuuren (1):
nfp: add whitelist of supported flow dissector
.../net/ethernet/netronome/nfp/flower/offload.c | 13 ++++++
drivers/net/ethernet/netronome/nfp/nfp_main.c | 47 ++++++++++++++++++++++
drivers/net/ethernet/netronome/nfp/nfp_net_main.c | 23 -----------
drivers/net/ethernet/netronome/nfp/nfpcore/nfp.h | 2 +
.../ethernet/netronome/nfp/nfpcore/nfp_resource.c | 45 +++++++++++++++++++++
5 files changed, 107 insertions(+), 23 deletions(-)
--
2.14.1
next reply other threads:[~2017-09-13 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 17:15 Jakub Kicinski [this message]
2017-09-13 17:15 ` [PATCH net v2 1/3] nfp: add whitelist of supported flow dissector Jakub Kicinski
2017-09-13 17:15 ` [PATCH net v2 2/3] nfp: wait for board state before talking to the NSP Jakub Kicinski
2017-09-13 17:16 ` [PATCH net v2 3/3] nfp: wait for the NSP resource to appear on boot Jakub Kicinski
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=20170913171600.31049-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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