public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Nathan Sullivan <nathan.sullivan@ni.com>,
	David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: macb: Add better comment for RXUBR handling
Date: Fri, 15 May 2015 09:49:07 +0200	[thread overview]
Message-ID: <5555A4F3.40703@atmel.com> (raw)
In-Reply-To: <1431554496-11716-1-git-send-email-nathan.sullivan@ni.com>

Le 14/05/2015 00:01, Nathan Sullivan a écrit :
> Describe the handler for RXUBR better with a new comment.
> 
> Signed-off-by: Nathan Sullivan <nathan.sullivan@ni.com>
> Reviewied-by: Josh Cartwright <joshc@ni.com>
> Reviewied-by: Ben Shelton <ben.shelton@ni.com>

Thanks Nathan: good that you've added this comment!

Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>

> ---
>  drivers/net/ethernet/cadence/macb.c |    6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/drivers/net/ethernet/cadence/macb.c b/drivers/net/ethernet/cadence/macb.c
> index 61aa570..5f10dfc 100644
> --- a/drivers/net/ethernet/cadence/macb.c
> +++ b/drivers/net/ethernet/cadence/macb.c
> @@ -1037,6 +1037,12 @@ static irqreturn_t macb_interrupt(int irq, void *dev_id)
>  		 * add that if/when we get our hands on a full-blown MII PHY.
>  		 */
>  
> +		/* There is a hardware issue under heavy load where DMA can
> +		 * stop, this causes endless "used buffer descriptor read"
> +		 * interrupts but it can be cleared by re-enabling RX. See
> +		 * the at91 manual, section 41.3.1 or the Zynq manual
> +		 * section 16.7.4 for details.
> +		 */
>  		if (status & MACB_BIT(RXUBR)) {
>  			ctrl = macb_readl(bp, NCR);
>  			macb_writel(bp, NCR, ctrl & ~MACB_BIT(RE));
> 


-- 
Nicolas Ferre

  reply	other threads:[~2015-05-15  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 22:01 [PATCH] net: macb: Add better comment for RXUBR handling Nathan Sullivan
2015-05-15  7:49 ` Nicolas Ferre [this message]
2015-05-15 16:13 ` 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=5555A4F3.40703@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan.sullivan@ni.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox