netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vince Bridgers <vbridger@opensource.altera.com>
To: <peppe.cavallaro@st.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: <vbridger@opensource.altera.com>, <vbridger@altera.com>
Subject: [PATCH net 0/5] stmmac: Correct flow control configuration
Date: Wed, 15 Apr 2015 11:17:37 -0500	[thread overview]
Message-ID: <1429114662-1528-1-git-send-email-vbridger@opensource.altera.com> (raw)

This series of patches corrects flow control configuration for the Synopsys
GMAC driver.

Flow control is configured based on a configurable receive fifo size. If
less than 4Kbytes flow control is left disabled and a warning is presented. If
a receive fifo size is not specified, flow control is left disabled to
maintain current behavior. Unicast pause detection was disabled, but is now 
enabled. The pause time was modified to be maximum time per a XON/XOFF
flow control mode of operation.

This patch was tested on an Altera Cyclone 5 and an Altera Arria 10 devkit,
and verified that flow control operates as expected when enabled.

Please consider this series for inclusion so that flow control will
function as expected for the Synopsys GMAC controller. 

Vince Bridgers (5):
  stmmac: Add properties for transmit and receive fifo sizes
  stmmac: Add defines and documentation for enabling flow control
  stmmac: Read tx-fifo-depth and rx-fifo-depth from the devicetree
  stmmac: Enable unicast pause frame detect in GMAC Register 6
  stmmac: Configure Flow Control to work correctly based on rxfifo size

 Documentation/devicetree/bindings/net/ethernet.txt |  6 +++
 Documentation/devicetree/bindings/net/stmmac.txt   |  4 ++
 drivers/net/ethernet/stmicro/stmmac/common.h       |  5 ++-
 drivers/net/ethernet/stmicro/stmmac/dwmac1000.h    | 51 ++++++++++++++++++++++
 .../net/ethernet/stmicro/stmmac/dwmac1000_core.c   |  5 ++-
 .../net/ethernet/stmicro/stmmac/dwmac1000_dma.c    | 26 ++++++++++-
 drivers/net/ethernet/stmicro/stmmac/dwmac100_dma.c |  2 +-
 drivers/net/ethernet/stmicro/stmmac/stmmac_main.c  | 16 ++++---
 .../net/ethernet/stmicro/stmmac/stmmac_platform.c  |  4 ++
 include/linux/stmmac.h                             |  2 +
 10 files changed, 111 insertions(+), 10 deletions(-)

-- 
1.9.1

             reply	other threads:[~2015-04-15 20:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-15 16:17 Vince Bridgers [this message]
2015-04-15 16:17 ` [PATCH net 1/5] stmmac: Add properties for transmit and receive fifo sizes Vince Bridgers
2015-04-15 16:17 ` [PATCH net 2/5] stmmac: Add defines and documentation for enabling flow control Vince Bridgers
2015-04-15 16:17 ` [PATCH net 3/5] stmmac: Read tx-fifo-depth and rx-fifo-depth from the devicetree Vince Bridgers
2015-04-15 16:17 ` [PATCH net 4/5] stmmac: Enable unicast pause frame detect in GMAC Register 6 Vince Bridgers
2015-04-15 16:17 ` [PATCH net 5/5] stmmac: Configure Flow Control to work correctly based on rxfifo size Vince Bridgers
2015-04-16  7:22 ` [PATCH net 0/5] stmmac: Correct flow control configuration Giuseppe CAVALLARO
2015-04-16 18:09 ` David Miller

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=1429114662-1528-1-git-send-email-vbridger@opensource.altera.com \
    --to=vbridger@opensource.altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peppe.cavallaro@st.com \
    --cc=vbridger@altera.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).