From: Nathan Sullivan <nathan.sullivan@ni.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: macb: Do not enable RX buffer used interrupt
Date: Mon, 4 May 2015 17:18:04 -0500 [thread overview]
Message-ID: <20150504221804.GA24341@nathan3500-linux-VM> (raw)
In-Reply-To: <1430761396-4878-1-git-send-email-nathan.sullivan@ni.com>
On Mon, May 04, 2015 at 12:43:15PM -0500, Nathan Sullivan wrote:
> This driver does not handle the RX buffer used interrupt, nor does
> it need to due to handling the RX overflow interrupt already. Enabling
> the interrupt would lead to an infinite loop in the ISR.
>
Well, that may have been premature. We are seeing the RXUBR interrupt get
stuck asserted on Zynq hardware, and I failed to realize the driver clears
RXUBR already in macb_interrupt... Not enabling that interrupt keeps my
system responsive, but it's not the correct solution to this issue.
prev parent reply other threads:[~2015-05-04 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 17:43 [PATCH] net: macb: Do not enable RX buffer used interrupt Nathan Sullivan
2015-05-04 22:18 ` Nathan Sullivan [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=20150504221804.GA24341@nathan3500-linux-VM \
--to=nathan.sullivan@ni.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).