netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net] nfp: always unmask aux interrupts at init
Date: Wed, 10 Jan 2018 15:51:22 -0500 (EST)	[thread overview]
Message-ID: <20180110.155122.188378601064685594.davem@davemloft.net> (raw)
In-Reply-To: <20180110021428.1706-1-jakub.kicinski@netronome.com>

From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue,  9 Jan 2018 18:14:28 -0800

> The link state and exception interrupts may be masked when we probe.
> The firmware should in theory prevent sending (and automasking) those
> interrupts if the device is disabled, but if my reading of the FW code
> is correct there are firmwares out there with race conditions in this
> area.  The interrupt may also be masked if previous driver which used
> the device was malfunctioning and we didn't load the FW (there is no
> other good way to comprehensively reset the PF).
> 
> Note that FW unmasks the data interrupts by itself when vNIC is
> enabled, such helpful operation is not performed for LSC/EXN interrupts.
> 
> Always unmask the auxiliary interrupts after request_irq().  On the
> remove path add missing PCI write flush before free_irq().
> 
> Fixes: 4c3523623dc0 ("net: add driver for Netronome NFP4000/NFP6000 NIC VFs")
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
> Reviewed-by: Dirk van der Merwe <dirk.vandermerwe@netronome.com>

Applied and queued up for -stable, thanks.

      reply	other threads:[~2018-01-10 20:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10  2:14 [PATCH net] nfp: always unmask aux interrupts at init Jakub Kicinski
2018-01-10 20:51 ` David Miller [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=20180110.155122.188378601064685594.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=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;
as well as URLs for NNTP newsgroup(s).