Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v5] e1000e i219 fix unit hang on reset and runtime D3
Date: Tue, 14 Apr 2015 05:58:55 -0700	[thread overview]
Message-ID: <1429016335.2638.7.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1428967221-32195-1-git-send-email-yanirx.lubetkin@intel.com>

On Tue, 2015-04-14 at 02:20 +0300, Yanir Lubetkin wrote:
> unit hang may occur if multiple descriptors are available in the rings
> during
> reset or runtime suspend. This state can be detected by testing bit 8
> in the
> FEXTNVM7 register. if this bit is set and there are pending
> descriptors in one
> of the rings, we must flush them prior to reset. same applies entering
> runtime
> suspend.
> 
> Signed-off-by: Yanir Lubetkin <yanirx.lubetkin@intel.com>
> ---
>  drivers/net/ethernet/intel/e1000e/ich8lan.h |   5 ++
>  drivers/net/ethernet/intel/e1000e/netdev.c  | 102
> ++++++++++++++++++++++++++++
>  drivers/net/ethernet/intel/e1000e/regs.h    |   1 +
>  3 files changed, 108 insertions(+)

Thanks Yanir, I have applied your patch to my queue.
-- 
git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue.git
dev-queue
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20150414/e5c476fc/attachment.asc>

  parent reply	other threads:[~2015-04-14 12:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 23:20 [Intel-wired-lan] [PATCH v5] e1000e i219 fix unit hang on reset and runtime D3 Yanir Lubetkin
2015-04-14  0:05 ` Alexander Duyck
2015-04-14 12:58 ` Jeff Kirsher [this message]
2015-04-22 14:40 ` Alexander Duyck
2015-04-22 14:57   ` Lubetkin, YanirX

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=1429016335.2638.7.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=intel-wired-lan@osuosl.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