All of lore.kernel.org
 help / color / mirror / Atom feed
From: mans@mansr.com (Måns Rullgård)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v1] net: ethernet: nb8800: Reset HW block in ndo_open
Date: Sat, 29 Jul 2017 13:05:28 +0100	[thread overview]
Message-ID: <yw1x379fla7r.fsf@mansr.com> (raw)
In-Reply-To: <f04a0cba-6c09-e9e4-f2d1-d8b2a7e276c9@free.fr> (Mason's message of "Sat, 29 Jul 2017 14:02:00 +0200")

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

> On 29/07/2017 13:24, M?ns Rullg?rd wrote:
>
>> Until you figure out why it's getting stuck, we can't be sure
>> it isn't caused by something that could trigger at any time.
> Would you take a look at it, if I can reproduce on tango4?
>
> I have identified a 100% reproducible flaw.
> I have proposed a work-around that brings this down to 0
> (tested 1000 cycles of link up / ping / link down).
>
> In my opinion, upstream should consider this work-around
> for inclusion. I'd like to hear David's and Florian's
> opinion on the topic. It's always a pain to maintain
> out-of-tree patches.

I'm not saying it shouldn't be fixed.  I am saying we should make sure
we make the right fix, not just paper over one instance of a wider issue.

>> Yes, but by then you've reset those parameters to the defaults.
>
> Good catch. There is some non HW-related init in
> nb8800_hw_init().
>
> I'll take this opportunity to change flow control to
> off by default (it breaks several 100 Mbps switches).

I was told to have it on by default.  This is what most other drivers do
too.  If you have faulty switches, that's your problem.

-- 
M?ns Rullg?rd

WARNING: multiple messages have this Message-ID (diff)
From: "Måns Rullgård" <mans@mansr.com>
To: Mason <slash.tmp@free.fr>
Cc: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev <netdev@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC PATCH v1] net: ethernet: nb8800: Reset HW block in ndo_open
Date: Sat, 29 Jul 2017 13:05:28 +0100	[thread overview]
Message-ID: <yw1x379fla7r.fsf@mansr.com> (raw)
In-Reply-To: <f04a0cba-6c09-e9e4-f2d1-d8b2a7e276c9@free.fr> (Mason's message of "Sat, 29 Jul 2017 14:02:00 +0200")

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

> On 29/07/2017 13:24, Måns Rullgård wrote:
>
>> Until you figure out why it's getting stuck, we can't be sure
>> it isn't caused by something that could trigger at any time.
> Would you take a look at it, if I can reproduce on tango4?
>
> I have identified a 100% reproducible flaw.
> I have proposed a work-around that brings this down to 0
> (tested 1000 cycles of link up / ping / link down).
>
> In my opinion, upstream should consider this work-around
> for inclusion. I'd like to hear David's and Florian's
> opinion on the topic. It's always a pain to maintain
> out-of-tree patches.

I'm not saying it shouldn't be fixed.  I am saying we should make sure
we make the right fix, not just paper over one instance of a wider issue.

>> Yes, but by then you've reset those parameters to the defaults.
>
> Good catch. There is some non HW-related init in
> nb8800_hw_init().
>
> I'll take this opportunity to change flow control to
> off by default (it breaks several 100 Mbps switches).

I was told to have it on by default.  This is what most other drivers do
too.  If you have faulty switches, that's your problem.

-- 
Måns Rullgård

  reply	other threads:[~2017-07-29 12:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 16:13 [RFC PATCH v1] net: ethernet: nb8800: Reset HW block in ndo_open Marc Gonzalez
2017-07-28 16:13 ` Marc Gonzalez
2017-07-28 16:17 ` Måns Rullgård
2017-07-28 16:17   ` Måns Rullgård
2017-07-28 16:43   ` Marc Gonzalez
2017-07-28 16:43     ` Marc Gonzalez
2017-07-28 18:56     ` Måns Rullgård
2017-07-28 18:56       ` Måns Rullgård
2017-07-28 21:53       ` Mason
2017-07-28 21:53         ` Mason
2017-07-29 11:24         ` Måns Rullgård
2017-07-29 11:24           ` Måns Rullgård
2017-07-29 12:02           ` Mason
2017-07-29 12:02             ` Mason
2017-07-29 12:05             ` Måns Rullgård [this message]
2017-07-29 12:05               ` Måns Rullgård
2017-07-29 12:44               ` Mason
2017-07-29 12:44                 ` Mason
2017-07-29 12:51                 ` Måns Rullgård
2017-07-29 12:51                   ` Måns Rullgård
2017-07-29 20:15                 ` Florian Fainelli
2017-07-29 20:15                   ` Florian Fainelli
2017-07-29 22:48                   ` Mason
2017-07-29 22:48                     ` Mason
2017-07-29 15:18             ` Florian Fainelli
2017-07-29 15:18               ` Florian Fainelli
2017-07-31 11:49               ` Mason
2017-07-31 11:49                 ` Mason
2017-07-31 11:59                 ` Måns Rullgård
2017-07-31 11:59                   ` Måns Rullgård
2017-07-31 14:08                   ` Mason
2017-07-31 14:08                     ` Mason
2017-07-31 15:18                     ` Mason
2017-07-31 15:18                       ` Mason
2017-07-31 15:28                       ` Måns Rullgård
2017-07-31 15:28                         ` Måns Rullgård
2017-07-31 15:18                     ` Måns Rullgård
2017-07-31 15:18                       ` Måns Rullgård

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=yw1x379fla7r.fsf@mansr.com \
    --to=mans@mansr.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.