devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Ben Hutchings <ben.hutchings@codethink.co.uk>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, devicetree@vger.kernel.org,
	galak@codeaurora.org, netdev@vger.kernel.org,
	linux-sh@vger.kernel.org
Subject: Re: [PATCH resend] Renesas Ethernet AVB driver
Date: Tue, 14 Apr 2015 00:13:48 +0200	[thread overview]
Message-ID: <552C3F9C.5070200@gmx.de> (raw)
In-Reply-To: <552C2849.2080503@cogentembedded.com>

Hi,

On 13.04.2015 22:34, Sergei Shtylyov wrote:
> Hello.
> 
> On 04/02/2015 04:56 PM, Ben Hutchings wrote:
> 
>> This driver looks somewhat similar to sh-eth, but lacks some of the
>> recent bug fixes made to that.  At least commit 283e38db65e7 ("sh_eth:
>> Fix serialisation of interrupt disable with interrupt & NAPI handler")
>> appears to be applicable, but there are probably others.
> 
>     I suspect this issue applies to many drivers...
>     I couldn't reproduce the bug that patch was fixing, so left this fix out 
> for the time being. Others cases were fixed (if applicable).

Maybe its just harder to trigger but it indeed looks similar to what Ben
has fixed for sh-eth. I wonder if that shutdown flag in the fix is
really needed though. IMHO it should be save if we simply call
napi_disable first, then disable irqs on hardware and finally
synchronize_irq...

Lino




  reply	other threads:[~2015-04-13 22:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27 23:13 [PATCH resend] Renesas Ethernet AVB driver Sergei Shtylyov
2015-03-28  5:17 ` Lino Sanfilippo
2015-03-28  8:36   ` Richard Cochran
2015-03-28 13:55   ` Sergei Shtylyov
2015-03-28  8:28 ` Richard Cochran
2015-03-28 18:26   ` David Miller
2015-03-30 22:51   ` Sergei Shtylyov
2015-03-31  6:43     ` Richard Cochran
2015-03-31  9:01       ` Richard Cochran
2015-03-31 15:38       ` David Miller
2015-03-31 17:40         ` Sergei Shtylyov
2015-03-31 17:48           ` David Miller
2015-04-03  6:27             ` masaru.nagai.vx
2015-04-12 22:03               ` Sergei Shtylyov
2015-04-09 13:11       ` Bjørn Mork
2015-04-09 17:57         ` David Miller
2015-04-13 20:23     ` Sergei Shtylyov
2015-04-14  5:27       ` Richard Cochran
2015-04-14 10:14         ` Sergei Shtylyov
2015-04-14 16:30           ` Richard Cochran
2015-04-14 16:58             ` Sergei Shtylyov
2015-04-14 18:30               ` Richard Cochran
2015-04-15  1:01                 ` masaru.nagai.vx
2015-04-15  5:31                   ` Richard Cochran
2015-04-02 13:56 ` Ben Hutchings
2015-04-13 20:34   ` Sergei Shtylyov
2015-04-13 22:13     ` Lino Sanfilippo [this message]
2015-04-13 22:31       ` Ben Hutchings
2015-04-13 22:53         ` Lino Sanfilippo
2015-04-13 23:08           ` Ben Hutchings

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=552C3F9C.5070200@gmx.de \
    --to=linosanfilippo@gmx.de \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-sh@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.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).