From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Zhu Yanjun <zyjzyj2000@gmail.com>,
stable <stable@vger.kernel.org>, Willy Tarreau <w@1wt.eu>
Cc: netdev@vger.kernel.org, w@1wt.eu,
Zhu Yanjun <Yanjun.Zhu@windriver.com>,
Bruce Allan <bruce.w.allan@intel.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/5] e1000e: reset MAC-PHY interconnect on 82577/82578
Date: Tue, 16 Dec 2014 04:12:06 -0800 [thread overview]
Message-ID: <1418731926.2467.15.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1418725700-31465-2-git-send-email-Yanjun.Zhu@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1727 bytes --]
On Tue, 2014-12-16 at 18:28 +0800, Zhu Yanjun wrote:
> 2.6.x kernels require a similar logic change as commit 6dfaa76
> [e1000e: reset MAC-PHY interconnect on 82577/82578] introduces
> for newer kernels.
>
> During Sx->S0 transitions, the interconnect between the MAC and PHY on
> 82577/82578 can remain in SMBus mode instead of transitioning to the
> PCIe-like mode required during normal operation. Toggling the
> LANPHYPC
> Value bit essentially resets the interconnect forcing it to the
> correct
> mode.
>
> after review of all intel drivers, found several instances where
> drivers had the incorrect pattern of:
> memory mapped write();
> delay();
>
> which should always be:
> memory mapped write();
> write flush(); /* aka memory mapped read */
> delay();
>
> explanation:
> The reason for including the flush is that writes can be held
> (posted) in PCI/PCIe bridges, but the read always has to complete
> synchronously and therefore has to flush all pending writes to a
> device. If a write is held and followed by a delay, the delay
> means nothing because the write may not have reached hardware
> (maybe even not until the next read)
>
> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Zhu Yanjun <Yanjun.Zhu@windriver.com>
> ---
> drivers/net/e1000e/defines.h | 2 ++
> drivers/net/e1000e/ich8lan.c | 20 ++++++++++++++++++++
> 2 files changed, 22 insertions(+)
To be clear, Zhu is wanting this applied to stable trees (yet did not CC
stable@vger.kernel.org ).
Willy- I am fine with this series being applied to stable.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-16 12:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 10:28 [PATCH V2 0/5] e1000e: fix nic not boot after rebooting Zhu Yanjun
2014-12-16 10:28 ` [PATCH 1/5] e1000e: reset MAC-PHY interconnect on 82577/82578 Zhu Yanjun
2014-12-16 10:48 ` David Laight
2014-12-16 12:12 ` Jeff Kirsher [this message]
2014-12-16 12:17 ` Willy Tarreau
2014-12-16 10:28 ` [PATCH 2/5] e1000e: workaround EEPROM configuration change on 82579 on kernel 2.6.x Zhu Yanjun
2014-12-16 10:28 ` [PATCH 3/5] e1000e: do not toggle LANPHYPC value bit when PHY reset is blocked Zhu Yanjun
2014-12-16 10:28 ` [PATCH 4/5] e1000e: update workaround for 82579 intermittently disabled during S0->Sx Zhu Yanjun
2014-12-16 10:28 ` [PATCH 5/5] e1000e: cleanup use of check_reset_block function pointer Zhu Yanjun
2015-05-14 17:10 ` [PATCH V2 0/5] e1000e: fix nic not boot after rebooting Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2014-12-15 8:39 [PATCH " Zhu Yanjun
2014-12-15 8:39 ` [PATCH 1/5] e1000e: reset MAC-PHY interconnect on 82577/82578 Zhu Yanjun
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=1418731926.2467.15.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=Yanjun.Zhu@windriver.com \
--cc=bruce.w.allan@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
--cc=zyjzyj2000@gmail.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