public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Måns Rullgård" <mans@mansr•com>
To: Mason <slash.tmp@free•fr>
Cc: Florian Fainelli <f.fainelli@gmail•com>,
	Andrew Lunn <andrew@lunn•ch>, netdev <netdev@vger•kernel.org>,
	David Miller <davem@davemloft•net>
Subject: Re: Waiting for the PHY to complete auto-negotiation
Date: Mon, 11 Dec 2017 16:32:53 +0000	[thread overview]
Message-ID: <yw1xtvwxtebu.fsf@mansr.com> (raw)
In-Reply-To: <e968c0cf-f69f-7f1d-a0db-b856f4c50755@free.fr> (Mason's message of "Mon, 11 Dec 2017 15:47:54 +0100")

Mason <slash.tmp@free•fr> writes:

> On 11/12/2017 15:36, Måns Rullgård wrote:
>
>> Mason writes:
>> 
>>> I suppose I should test forcefully setting the enable bit to 0 in
>>> the driver, and see if hell breaks loose.
>> 
>> You can't.  When the enable bit is 1, writes to that register are
>> ignored.  It goes back to 0 automatically when the hw runs out of
>> descriptors.
>
> I don't think they are ignored, because toggling the control flow
> bit actually breaks RX.

Oh, then it's even worse than the docs suggest.

-- 
Måns Rullgård

      reply	other threads:[~2017-12-11 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 16:39 Waiting for the PHY to complete auto-negotiation Mason
2017-12-06 16:59 ` Andrew Lunn
2017-12-06 18:03   ` Mason
2017-12-06 18:26     ` Andrew Lunn
2017-12-06 19:00       ` Mason
2017-12-06 19:07         ` Andrew Lunn
2017-12-06 19:25           ` Mason
2017-12-06 23:00             ` Florian Fainelli
2017-12-07 16:17               ` Mason
2017-12-09 18:49                 ` Florian Fainelli
2017-12-11 14:29                   ` Mason
2017-12-11 14:36                     ` Måns Rullgård
2017-12-11 14:47                       ` Mason
2017-12-11 16:32                         ` Måns Rullgård [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=yw1xtvwxtebu.fsf@mansr.com \
    --to=mans@mansr$(echo .)com \
    --cc=andrew@lunn$(echo .)ch \
    --cc=davem@davemloft$(echo .)net \
    --cc=f.fainelli@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=slash.tmp@free$(echo .)fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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