All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: johan@kernel.org,
	"open list:TI NETCP ETHERNET DRIVER" <netdev@vger.kernel.org>,
	"Kwok, WingMan" <w-kwok2@ti.com>
Subject: Re: Micrel Phy - Is there a way to configure the Phy not to do 802.3x flow control?
Date: Thu, 3 Mar 2016 23:26:54 +0100	[thread overview]
Message-ID: <20160303222654.GS15541@lunn.ch> (raw)
In-Reply-To: <56D8B83E.7000303@ti.com>

On Thu, Mar 03, 2016 at 05:18:38PM -0500, Murali Karicheri wrote:
> Hi,
> 
> We are using Micrel Phy in one of our board and wondering if we can force the
> Phy to disable flow control at start. I have a 1G ethernet switch connected
> to Phy and the phy always enable flow control. I would like to configure the
> phy not to flow control. Is that possible and if yes, what should I do in the
> my Ethernet driver to tell the Phy not to enable flow control?

Hi Murali

Have you played with:

       ethtool -a|--show-pause devname

       ethtool -A|--pause devname [autoneg on|off] [rx on|off] [tx on|off]

Andrew

  reply	other threads:[~2016-03-03 22:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 22:18 Micrel Phy - Is there a way to configure the Phy not to do 802.3x flow control? Murali Karicheri
2016-03-03 22:26 ` Andrew Lunn [this message]
2016-03-10 15:07   ` Murali Karicheri
2016-03-04  0:16 ` Florian Fainelli
2016-03-10 16:48   ` Murali Karicheri
2016-03-10 18:05     ` Florian Fainelli
2016-03-10 19:38       ` Murali Karicheri
2016-03-10 22:51         ` Murali Karicheri
2016-03-11 18:31         ` Murali Karicheri
2016-03-11 19:51           ` Florian Fainelli
2016-03-16 15:08             ` Murali Karicheri
2016-03-16 15:16               ` Murali Karicheri
2016-03-18  0:10               ` Florian Fainelli

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=20160303222654.GS15541@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=johan@kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=w-kwok2@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.